[kile] [Bug 485951] New: The window allowing selection of clipboard history items is unusable
https://bugs.kde.org/show_bug.cgi?id=485951 Bug ID: 485951 Summary: The window allowing selection of clipboard history items is unusable Classification: Applications Product: kile Version: 2.9.93 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: user interface Assignee: michel.lud...@gmail.com Reporter: listes.rusc...@laposte.net Target Milestone: --- Created attachment 168790 --> https://bugs.kde.org/attachment.cgi?id=168790=edit Example of too small a window to see and use its contents Greetings, the picture attached says it all: the window allowing selection of clipboard history items is small and unresizable. The example provided is for a window that is 2-3 cm wide. Thank you for developing this awesome piece of software! Sincerely, Filippo -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 476207] Kile crashes when clicking the browse button of the viewer
https://bugs.kde.org/show_bug.cgi?id=476207 rusconi changed: What|Removed |Added CC||listes.rusc...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 476207] Kile crashes when clicking the browse button of the viewer
https://bugs.kde.org/show_bug.cgi?id=476207 --- Comment #9 from rusconi --- Created attachment 168142 --> https://bugs.kde.org/attachment.cgi?id=168142=edit New crash information added by DrKonqi kile (2.9.93) using Qt 5.15.10 Confirm the previously reported bug -- Backtrace (Reduced): #6 0x7f5e1ad5c506 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f5e1ad5f271 in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 [...] #9 0x7f5e1ae58ddb in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f5e1af55b3e in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f5e1ada5dc8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 481419] New: Failure to build kcalc right after successfull kdesrc-build --pretend
https://bugs.kde.org/show_bug.cgi?id=481419 Bug ID: 481419 Summary: Failure to build kcalc right after successfull kdesrc-build --pretend Classification: Developer tools Product: kdesrc-build Version: Git Platform: Debian testing OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: mp...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- Greetings, >From the git https://invent.kde.org/sdk/kdesrc-build page, I followed all the steps up to: $ kdesrc-build --pretend The output is very reassuring: ``` Holding performance profile Building extra-cmake-modules from frameworks (1/375) Cloning extra-cmake-modules Source update complete for extra-cmake-modules: 1 file affected. Preparing build system for extra-cmake-modules. Running cmake targeting Kate - Ninja... Compiling... succeeded (after 0 seconds) Installing extra-cmake-modules succeeded (after 0 seconds) [... lots of similar output with only succeeded outcome] Building xwaylandvideobridge from xwaylandvideobridge (374/375) Cloning xwaylandvideobridge Source update complete for xwaylandvideobridge: 1 file affected. Preparing build system for xwaylandvideobridge. Running cmake targeting Kate - Ninja... Compiling... succeeded (after 0 seconds) Installing xwaylandvideobridge succeeded (after 0 seconds) Building qrca from qrca (375/375) Cloning qrca Source update complete for qrca: 1 file affected. Preparing build system for qrca. Running cmake targeting Kate - Ninja... Compiling... succeeded (after 0 seconds) Installing qrca succeeded (after 0 seconds) <<< PACKAGES SUCCESSFULLY BUILT >>> Built 375 modules ``` I thus go on with the build of kcalc (small program to start with) and at that point that fails like this: ``` % kdesrc-build kcalc git:(master|) Fetching remote changes to sysadmin-repo-metadata Merging sysadmin-repo-metadata changes from branch master Holding performance profile Building extra-cmake-modules from frameworks (1/22) Cloning extra-cmake-modules Source update complete for extra-cmake-modules: 579 files affected. Preparing build system for extra-cmake-modules. Running cmake targeting Kate - Ninja... Compiling... succeeded (after 2 seconds) Installing extra-cmake-modules succeeded (after 1 second) Building kconfig from frameworks (2/22) Cloning kconfig Source update complete for kconfig: 395 files affected. Preparing build system for kconfig. Running cmake targeting Kate - Ninja... Unable to configure kconfig with KDE CMake kconfig didn't build, stopping here. <<< PACKAGES FAILED TO BUILD >>> kconfig - /home/rusconi/kde/src/log/2024-02-16-01/kconfig/cmake.log Possible solution: Install the build dependencies for the modules: kconfig You can use 'sudo apt build-dep ', 'sudo dnf builddep ', 'sudo zypper --plus-content repo-source source-install --build-deps-only ' or a similar command for your distro of choice. See https://community.kde.org/Get_Involved/development/Install_the_dependencies Important notification for kconfig: kconfig has failed to build 7 times. :-( Your logs are saved in /home/rusconi/kde/src/log/2024-02-16-01 (additional logs are saved in /home/rusconi/.local/state/log/2024-02-16-03) ``` At that point, I look into /home/rusconi/kde/src/log/2024-02-16-01/kconfig/cmake.log ``` 1 # kdesrc-build running: 'cmake' '-B' '.' '-S' '/home/rusconi/kde/src/kconfig' '-G' 'Kate - Ninja' '-DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=ON' '-DCMAKE_BUILD_TYPE=RelWithDebInfo' '-DBUILD_WITH_QT6=ON' '-DCMAKE_CXX_FLAGS:STRING=-pip 1 e' '-DCMAKE_INSTALL_PREFIX=/home/rusconi/kde/usr' 2 # from directory: /home/rusconi/kde/build/kconfig 3 CMake Deprecation Warning: 4 Support for "Extra Generators" like 5 6 Kate 7 8 is deprecated and will be removed from a future version of CMake. IDEs may 9 use the cmake-file-api(7) to view CMake-generated project build trees. 10 11 12 -- The C compiler identification is GNU 13.2.0 13 -- The CXX compiler identification is GNU 13.2.0 14 -- Detecting C compiler ABI info 15 -- Detecting C compiler ABI info - done 16 -- Check for working C compiler: /usr/lib/ccache/cc - skipped 17 -- Detecting C compile features 18 -- Detecting C compile features - done 19 -- Detecting CXX compiler ABI info 20 -- Detect
[kdevelop] [Bug 477759] After formatting, the code position is reset to top of file
https://bugs.kde.org/show_bug.cgi?id=477759 --- Comment #4 from rusconi --- Greetings, I have made a pull request at https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/530 that apparently sets the formatted file's views' cursor positions correctly right after the formatting of the file. I have left comments using cout(), of course remove them freely. In the hope this very first contribution is a good starting point to have code in the upstream source tree. Sincerely, Filippo -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 477759] After formatting, the code position is reset to top of file
https://bugs.kde.org/show_bug.cgi?id=477759 --- Comment #2 from rusconi --- (In reply to Igor Kushnir from comment #1) > The relevant code appears to be in > SourceFormatterController::FileFormatter::formatDocument() at > https://invent.kde.org/kdevelop/kdevelop/-/blob/ > 8f23c66e87587db3116d81f14e7d7ea3caf03150/kdevplatform/shell/ > sourceformattercontroller.cpp#L729-735 > > I think the bug can be fixed by introducing new API > QVector IDocument::allCursorPositions() and void > IDocument::setAllCursorPositions(const QVector &); and > using the new API in formatDocument() to save and restore the cursor > positions of all views, not just the active one. Since this API does not > exist yet, similar bugs are possible elsewhere. > > A merge request is welcome. I would be eager to help. Please, give me some directions as to where I find the different views of a given opened file, to start with. Then, I'll try to find my way. Thank you, Filippo -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 477759] New: After formatting, the code position is reset to top of file
https://bugs.kde.org/show_bug.cgi?id=477759 Bug ID: 477759 Summary: After formatting, the code position is reset to top of file Classification: Applications Product: kdevelop Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- Greetings, I use the clang formatter in KDevelop. I also open many editing views with the split feature. Oftentimes I view multiple times the same file at different locations in these views. When I run the code reformatting feature, the view that is active stays at the right location while the other views change the position of the text to the top of that file's text. This is problematic because it obliges me to look back for the right position each time (or setting / unsetting continuously bookmarks). I run the code formatter very very often because the view of properly formatted code helps me understanding the code I am working on. But if that formatting comes at the price of having to always search back the original position in the file, that's a huge toll. Would it be possible to fix this issue ? Thank you for listening and congrats on this wonderful development enviroment! Filippo -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 477663] New: Direct file to be opened to a given editor view (left or right | top or bottom)
https://bugs.kde.org/show_bug.cgi?id=477663 Bug ID: 477663 Summary: Direct file to be opened to a given editor view (left or right | top or bottom) Classification: Applications Product: kdevelop Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- Greetings, I love using KDevelop by setting the header files in the left editor pane (after having made a vertical split) and the code files in the right editor pane. It would very helpful to be able to drag and drop a given file (either .hpp or .cpp) from the file list available in the "Projects" or the "Documents" to the editor's left or right pane. Thank you for developing KDevelop! Sincerely, Filippo -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 475918] New: Focus follows mouse inside the editor when there is an active split
https://bugs.kde.org/show_bug.cgi?id=475918 Bug ID: 475918 Summary: Focus follows mouse inside the editor when there is an active split Classification: Applications Product: kdevelop Version: 5.10.221202 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: All editors Assignee: kdevelop-bugs-n...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- Greetings, how such a wonderful development environment! One wish: I am deeply accustomed to the fact that the focus follows mouse in KDE and I get always caught writing text in the bad editor window of the KDevelop IDE when the editor window is split. Would it be possible to implement that as an option? It certainly would make life easier for focus-follows-mouse-people-like-me :-) Most sincerely, lopi...@debian.org -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 471560] New: KDevelop crashes when eliciting a file reformatting operation
https://bugs.kde.org/show_bug.cgi?id=471560 Bug ID: 471560 Summary: KDevelop crashes when eliciting a file reformatting operation Classification: Applications Product: kdevelop Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- Application: kdevelop (5.10.221202 (22.12.2)) Qt Version: 5.15.8 Frameworks Version: 5.107.0 Operating System: Linux 6.1.0-9-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux trixie/sid DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I started a clang-format-based reformatting of the file using the Alt+C,F keyboard shortcut and the program crashed. This already happened sometimes. The crash can be reproduced sometimes. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f655650d1dc in QAccessibleObject::object() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7f6556fb618a in QAccessibleWidget::isValid() const () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f6556506848 in QAccessibleEvent::accessibleInterface() const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7f6556506d6d in QAccessible::updateAccessibility(QAccessibleEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7f65539f7934 in KateViewInternal::documentTextInserted(KTextEditor::Document*, KTextEditor::Range) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #9 0x7f65560e8f4f in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f65538b4417 in KTextEditor::DocumentPrivate::textInsertedRange(KTextEditor::Document*, KTextEditor::Range const&) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #11 0x7f655393748f in KTextEditor::DocumentPrivate::editWrapLine(int, int, bool, bool*) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #12 0x7f6553938cc3 in KTextEditor::DocumentPrivate::insertText(KTextEditor::Cursor const&, QString const&, bool) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #13 0x7f655393b92b in KTextEditor::DocumentPrivate::setText(QString const&) () at /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #14 0x7f6553db5eda in () at /lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.510 #15 0x7f6557b025cd in KDevelop::SourceFormatterController::FileFormatter::formatDocument(KDevelop::IDocument&) const () at /lib/x86_64-linux-gnu/libKDevPlatformShell.so.510 #16 0x7f6557b02ea3 in KDevelop::SourceFormatterController::beautifySource() () at /lib/x86_64-linux-gnu/libKDevPlatformShell.so.510 #17 0x7f65560e8f4f in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f6556d5c782 in QAction::triggered(bool) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f6556d5f3ab in QAction::activate(QAction::ActionEvent) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f6556d5ff7d in QAction::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f6556d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f65560b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f655656c76b in QShortcutMap::dispatchEvent(QKeyEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #24 0x7f655656d0bb in QShortcutMap::tryShortcut(QKeyEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7f6556515376 in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #26 0x7f65565390cd in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #27 0x7f654ab03063 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so #28 0x7f65560e8f4f in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f6556bde03f in QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #30 0x7f65560dd6f0 in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #31 0x7f6556d62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7f65560b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f65560b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7f655610a153 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f6551c627a9 in g_main_context_dispatch () at
[Active Window Control] [Bug 466341] New: When only one window opened on virtual desktop and switching back to that desktop from another one, give it the focus
https://bugs.kde.org/show_bug.cgi?id=466341 Bug ID: 466341 Summary: When only one window opened on virtual desktop and switching back to that desktop from another one, give it the focus Classification: Plasma Product: Active Window Control Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: listes.rusc...@laposte.net CC: plasma-b...@kde.org Target Milestone: --- Greetings, I have multiple virtual desktops. I continuously switch from one to another back and forth (everything keyboard-based with tons of shortcuts). Most often some of these desktops contain a single window spanning all my monitors (huge Konsole with many tabs, each containing a vim session with many vim tabs). What I would like: when I switch back to the desktops that contain a single window, I would like it to be automagically focused. At present time, I have to use the Alt+TAB to activate it each time with is an uncomfortable key shortcut and breaks the fluidity of the workflow. Rationale: since there is only one window open in that desktop (and that it covers all the estate), that makes sense for it to gain focus by default when switching to the desktop containing it, no ? Thank you for the wonderful software that you develop and make it available to all of us! I use KDE since decades. Most sincerely, Filippo -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 463915] Custom shortcuts do not work
https://bugs.kde.org/show_bug.cgi?id=463915 --- Comment #6 from rusconi --- Greetings, having followed your suggestion that Custom shortcuts should now be moved to the Shortcuts section, I have not observed the reported failures anymore. Maybe we could close the issue since people experiencing the same issues will know here how to proceed to fix them ? Anyways, most sincerely, Filippo PS Keep up with the wonderful work you do in KDE/Plasma :-) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 463915] Custom shortcuts do not work
https://bugs.kde.org/show_bug.cgi?id=463915 --- Comment #4 from rusconi --- (In reply to Nate Graham from comment #3) > But were these custom shortcuts set using the "Custom Shortcuts" page in > system settings, or the "Shortcuts" page? Yes, they were set there in the "Custom Shortcuts" (that was years ago :-) Sincerely Filippo -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 463915] Custom shortcuts do not work
https://bugs.kde.org/show_bug.cgi?id=463915 --- Comment #2 from rusconi --- (In reply to Nate Graham from comment #1) > Are you using X11 or Wayland? > > Were these custom shortcuts using the "Custom Shortcuts" page in system > settings, or the "Shortcuts" page? Greetings, thank you for your response. First of all, after a second upgrade, the situation is more erratic: some times the shortcuts do not work and then other times they do. It seems like there might be a timer that waits for them to be configured and set. Anyhow, I am using Xorg. Sincerely, Filippo PS One thing I am starting to see as I go: if I start firefox with my custom shortcut Win+F, after some time it crashes (or closes, I cannot tell). At that point, I try to use the custom shortcut again, and that time it would not work (Firefox does not start). I start it using KRunner and then it never crashes (or closes). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 463915] New: Custom shortcuts do not work
https://bugs.kde.org/show_bug.cgi?id=463915 Bug ID: 463915 Summary: Custom shortcuts do not work Classification: Frameworks and Libraries Product: frameworks-kglobalaccel Version: 5.26.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- Greetings, since the last two updates of plasma on my debian testing machine (quite recently), I noticed that my custom shortcuts do not work right after login. Interestingly, I also noticed that at some point they would work, according to the following sequence: - open the System Settings window: not yet - select Shortcuts: not yet - select Custom shortcuts: not yet - select my own group of shortcuts without modifying anything: yes! the shortcuts work. I hope this is enough to trace back the problem. Thank you for such an amazing desktop ! Filippo -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 445098] New: Wish: add [date/time] as target to suspend reminder
https://bugs.kde.org/show_bug.cgi?id=445098 Bug ID: 445098 Summary: Wish: add [date/time] as target to suspend reminder Product: korganizer Version: 5.13.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: reminder daemon (korgac) Assignee: kdepim-b...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- SUMMARY When a reminder is triggered, the dialog box that is provided to the user lists the task at hand and provides a way to suspend the reminder to retrigger in weeks, days, hours, minutes. I would find it highly useful if the user could enter via a calendar widget the date and time at which the reminder should be triggered once more. For example: it's saturday at night and I have a reminder for an event that will occur on monday at 14:00. I would like to be able to quickly set the reminder to trigger again on monday at 08:00 (because I know I'll be on my computer at that time). Doing the calculations in days/hours/minutes is complicated (and I do not want to risk an error). Doing a simple calendar search/click and then tell an hour would be highly useful. I know of this because KAlarm (which I used to use) allows this very useful and flexible reminder time setting. Thank you s much for developing KDE! Sincerely, Filippo SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Debian GNU/Linux box, here. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 351057] custom shortcuts disappear
https://bugs.kde.org/show_bug.cgi?id=351057 rusconi changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #11 from rusconi --- For me the new KDE version works fine: KDE Plasma Version: 5.19.5 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 415975] New: Make available to dbus the function that saves the organizer calendar to ics file
https://bugs.kde.org/show_bug.cgi?id=415975 Bug ID: 415975 Summary: Make available to dbus the function that saves the organizer calendar to ics file Product: korganizer Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: import/export Assignee: kdepim-b...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- SUMMARY I would like to automagically (via qdbus bash scripting) save the korganizer calendar (with two folders) to file. KOrganizer receives data from a nextcloud web calendar with two folders. I would like to store "on demand" the calendars to a file (as a backup if the web calendar fails, as it sometimes does). Thank you for the collective work on KDE, my desktop environment since years and years... Filippo @debian.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391633] Screen brightness cannot be adjusted from keyboard or UI
https://bugs.kde.org/show_bug.cgi?id=391633 rusconi <listes.rusc...@laposte.net> changed: What|Removed |Added CC||listes.rusc...@laposte.net --- Comment #3 from rusconi <listes.rusc...@laposte.net> --- I discovered that clicking the Apply button is required when changing the screen brightness setting from the "Energy saving" menu of the system settings panel. That is not intuitive, one would expect the luminosity of the screen to change along with the sliding of the control. For a ZBook (Xeon) HP laptop workstation, the settings cannot be modified using the fn/f5 fn/f6 keyboard combinations. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389434] New: .xsession-errors reported an error
https://bugs.kde.org/show_bug.cgi?id=389434
Bug ID: 389434
Summary: .xsession-errors reported an error
Product: kwin
Version: unspecified
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: core
Assignee: kwin-bugs-n...@kde.org
Reporter: listes.rusc...@laposte.net
Target Milestone: ---
5307529 kf5.kcoreaddons.desktopparser: Could not locate service type file
kservicetypes5/kwin-script.desktop, tried ("/home//.local/share",
"/usr/share", "/usr/local/share")
That error is in .xsession-errors. When I try to locate the file, I discover
that it actually is :
/usr/share/kservicetypes5/kwinscript.desktop
Note the missing dash.
Hope this helps.
Filippo
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 356466] okular print graphing paper smaller than it should be
https://bugs.kde.org/show_bug.cgi?id=356466 --- Comment #3 from rusconi <listes.rusc...@laposte.net> --- When I try to print according to your suggestion the svg Inkscape file, I get the following error: lpr: Unsupported document-format "image/svg+xml" However, this is what I tried: Print the graph paper directly from Inkscape : perfect Print using inkscape --without-gui --export-pdf=/dev/stdout /tmp/file.svg | lpr -P HP_PRINTER -o fit-to-page : erroneous size Print using inkscape --without-gui --export-pdf=/dev/stdout /tmp/file.svg | lpr -P HP_PRINTER : perfect Print the pdf file from Inkscape using Okular : seems like printing with -o fit-to-page, although the ouput is not sub-millimetrically identical. So, yeah, the hypothesis you provide seems correct. Thank you for your handling of this bug. Cheers, Filippo So, yeah, apparently you are right, -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374337] Alarm export / import doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=374337 --- Comment #4 from rusconi <listes.rusc...@laposte.net> --- Greetings, is this bugs's status still unconfirmed ? How is it going to be dealt with ? Thank you. Filippo -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 374337] Alarm export / import doesn't work properly
https://bugs.kde.org/show_bug.cgi?id=374337 rusconi <listes.rusc...@laposte.net> changed: What|Removed |Added CC||listes.rusc...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 351242] cannot type accented characters like é à è
https://bugs.kde.org/show_bug.cgi?id=351242 --- Comment #1 from rusconi <listes.rusc...@laposte.net> --- Version 16.12.0 For me this bug seems to have gone away. You can close it. Thank you for this useful program. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 351253] KAlarm does not go to system tray and closing the window ends its process.
https://bugs.kde.org/show_bug.cgi?id=351253 --- Comment #7 from rusconi <listes.rusc...@laposte.net> --- Version 2.11.7-5ak This bug seems to not show up anymore. For me, you can close it. Thank you for this useful program. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 378945] Export of selected alarms fails
https://bugs.kde.org/show_bug.cgi?id=378945 --- Comment #2 from rusconi <listes.rusc...@laposte.net> --- Greetings Jarvie, thank you for your reply. In fact, after thinking a bit about it, I reasoned that the most simple thing to backup is simply the calendar.ics file that contains all the active alarms. So, forget about my enquiry/suggestion. Filippo -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 378945] New: Export of selected alarams fails
https://bugs.kde.org/show_bug.cgi?id=378945 Bug ID: 378945 Summary: Export of selected alarams fails Product: kalarm Version: 2.11.4 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: listes.rusc...@laposte.net Target Milestone: --- Version: 2.11.7-5ak (Debian GNU/Linux, KDE desktop) When I select alarms, right-click onto them and then select export to a file, the export fails with the following message: Failed to save new calendar to: May I take advantage to suggest that such an export feature might be implemented such that it is accessible from dbus. That would be awesome to be able to automatically export the alarms to a file from the command line this way. Thank you for this excellent piece of software ! Filippo -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 356466] New: okular print graphing paper smaller than it should be
https://bugs.kde.org/show_bug.cgi?id=356466 Bug ID: 356466 Summary: okular print graphing paper smaller than it should be Product: okular Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: printing Assignee: okular-de...@kde.org Reporter: listes.rusc...@laposte.net I prepare my graphing paper (5x5 mm squares) with Inkscape. When I print the graph paper directly from Inkscape the 5x5 square size is correct over a 20 cm length. If I first export that Inkscape document to a pdf file and then use Okular to print it, the squares are smaller (I can fit one square more in a 30 cm length). I know this is Okular's fact because if I print that same pdf file with lpr , the result is perfect, like when I print directly from Inkscape. I could provide the Inkscape file, if necessary. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
