[plasmashell] [Bug 489003] Cant change power profiles with widget despite power-profiles-daemon being enabled and working
https://bugs.kde.org/show_bug.cgi?id=489003 César Augusto Montoya Ocampo changed: What|Removed |Added CC||sprit152...@gmail.com --- Comment #5 from César Augusto Montoya Ocampo --- Can confirm same behavior, from a fresh install of KDE Plasma on Fedora 40, I added the "Power and Battery" widget to the panel, and it displays no batteries, as well as the power-profiles not supported message, relevant terminal outputs (https://pastebin.com/t75TdtHc). Additional information: Removing the widget and adding it again fixes the issue, but it will appear again on next boot. SPECS Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.9.5-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: HP Product Name: HP Pavilion Laptop 15-eg0xxx System Version: Type1ProductConfigId -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 425912] Send video stream from phone to computer with kdeconnect (phone as webcam/security camera)
https://bugs.kde.org/show_bug.cgi?id=425912 César Augusto Montoya Ocampo changed: What|Removed |Added CC||sprit152...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472543] Crash when closing a window
https://bugs.kde.org/show_bug.cgi?id=472543 César changed: What|Removed |Added CC||elorm...@gmail.com --- Comment #3 from César --- Plasma crashed when I closed a python3 app created by myself -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467588] Battery indicator displays connected and not charging but it is not really connected
https://bugs.kde.org/show_bug.cgi?id=467588 César Augusto Montoya Ocampo changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #8 from César Augusto Montoya Ocampo --- Hello, suddenly this issue is no longer happening, I'll close the issue, I have no idea what I did to fix it, or if some package update fixed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467588] Battery indicator displays connected and not charging but it is not really connected
https://bugs.kde.org/show_bug.cgi?id=467588 --- Comment #7 from César Augusto Montoya Ocampo --- (In reply to Fushan Wen from comment #6) > So upower/powerdevil correctly reports the battery status, but the widget > shows wrong information, which is weird. That seems to be it, how do we proceed? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 467588] Battery indicator displays connected and not charging but it is not really connected
https://bugs.kde.org/show_bug.cgi?id=467588 --- Comment #5 from César Augusto Montoya Ocampo --- What a long command to get such tiny output. (true,) -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 467588] Battery indicator displays connected and not charging but it is not really connected
https://bugs.kde.org/show_bug.cgi?id=467588 --- Comment #3 from César Augusto Montoya Ocampo --- Created attachment 157446 --> https://bugs.kde.org/attachment.cgi?id=157446=edit upower -d output Added to attachments -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 467588] Battery indicator displays connected and not charging but it is not really connected
https://bugs.kde.org/show_bug.cgi?id=467588 César Augusto Montoya Ocampo changed: What|Removed |Added Attachment #157430|0 |1 is obsolete|| --- Comment #1 from César Augusto Montoya Ocampo --- Created attachment 157432 --> https://bugs.kde.org/attachment.cgi?id=157432=edit Image showing battery status, laptop is disconnected -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 467588] New: Battery indicator displays connected and not charging but it is not really connected
https://bugs.kde.org/show_bug.cgi?id=467588 Bug ID: 467588 Summary: Battery indicator displays connected and not charging but it is not really connected Classification: Plasma Product: Powerdevil Version: 5.27.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sprit152...@gmail.com CC: m...@ratijas.tk Target Milestone: --- Created attachment 157430 --> https://bugs.kde.org/attachment.cgi?id=157430=edit Video demostrating laptop unplugged but Plasma thinking is not SUMMARY *** When starting up, battery status indicator on system tray will display connected but not charging, though it is not really connected, this is fixed by connecting and disconnecting the laptop *** STEPS TO REPRODUCE 1. Login into Plasma with a laptop while on battery 2. Check battery status OBSERVED RESULT Battery indicator shows "plugged in but not charging" EXPECTED RESULT Battery indicator should show not connected (discharging) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux 37 (Kernel 6.1.18-200.fc37.x86_64 (64-bit)) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Not happening on Gnome, not duplicate of https://bugs.kde.org/show_bug.cgi?id=423556, mine gets fixed by plugging and unplugging the laptop. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454490] [Plasma workspace] Spectacle hotkeys hardcoded (?) in Wayland
https://bugs.kde.org/show_bug.cgi?id=454490 César Augusto Montoya Ocampo changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED --- Comment #4 from César Augusto Montoya Ocampo --- (In reply to Justin Zobel from comment #3) > César can you please confirm if you are able to reproduce this issue on a > current version of Plasma? It seems the two other users who replied here are > unable to reproduce it. Right now I don't have how test this out, sorry, I guess I'll close the bug. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 455056] New: Kate crash when going to Settings Menu -> 'Configure Kate' option
https://bugs.kde.org/show_bug.cgi?id=455056 Bug ID: 455056 Summary: Kate crash when going to Settings Menu -> 'Configure Kate' option Product: kate Version: 22.04.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: cesar.pastor...@sidia.com Target Milestone: --- Application: kate (22.04.1) Qt Version: 5.15.4 Frameworks Version: 5.94.0 Operating System: Linux 5.13.0-44-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.24 DrKonqi: 5.24.5 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: I just opened the Settings menu and selected the 'Configure Kate' option. The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [New LWP 313232] [New LWP 313233] [New LWP 313234] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f20e1c4f99f in __GI___poll (fds=0x7fff7cd880b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f20ddc749c0 (LWP 313231))] Thread 4 (Thread 0x7f20ca6bc700 (LWP 313234)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55b590d512a8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55b590d51258, cond=0x55b590d51280) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55b590d51280, mutex=0x55b590d51258) at pthread_cond_wait.c:647 #3 0x7f20d42af5eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f20d42af1eb in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f20e0b59609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f20e1c5c133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f20d7a8a700 (LWP 313233)): #0 0x7f20e1c4f99f in __GI___poll (fds=0x7f20d0012e10, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f20e014836e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f20e01484a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f20e2220c8b in QEventDispatcherGlib::processEvents (this=0x7f20db60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f20e21c4eab in QEventLoop::exec (this=this@entry=0x7f20d7a89bb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f20e1fde462 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f20e3284f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f20e1fdf643 in QThreadPrivate::start (arg=0x7f20e3308d80) at thread/qthread_unix.cpp:331 #8 0x7f20e0b59609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f20e1c5c133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f20dd101700 (LWP 313232)): #0 0x7f20e1c4f99f in __GI___poll (fds=0x7f20dd100ae8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f20e0b96c1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f20e0b9890a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f20dd84b228 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f20e1fdf643 in QThreadPrivate::start (arg=0x55b590844df0) at thread/qthread_unix.cpp:331 #5 0x7f20e0b59609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f20e1c5c133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f20ddc749c0 (LWP 313231)): [KCrash Handler] #4 0x7f20e36e2cd8 in QFlags::operator|= (other=, this=) at ./src/core/kconfig.cpp:1045 #5 KConfigPrivate::lookupData (this=this@entry=0x26b, group=..., key=key@entry=0x7f20dc834b26 "View Style", flags=flags@entry=..., expand=expand@entry=0x7fff7cd88e47) at ./src/core/kconfig.cpp:1046 #6 0x7f20e36f58d4 in KConfigGroup::readEntry (this=this@entry=0x55b5910b3a40, key=key@entry=0x7f20dc834b26 "View Style", aDefault=...) at /usr/include/c++/9/bits/atomic_base.h:326 #7 0x7f20e36f5b10 in KConfigGroup::readEntry (this=0x55b5910b3a40, key=0x7f20dc834b26 "View Style", aDefault=0x7f20dc834b1b "DetailTree") at /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:706 #8 0x7f20dc7be301 in KDirOperator::readConfig(KConfigGroup const&) () from /lib/x86_64-linux-gnu/libKF5KIOFileWidgets.so.5 #9 0x7f20d6eefc24 in KateFileBrowser::readSessionConfig (this=0x55b5920b0320, cg=...) at ./addons/filebrowser/katefilebrowser.cpp:160 #10 0x7f20d6eed08f in KateFileBrowserPluginView::createFileBrowser (this=0x55b59108e9c0, visible=true) at /usr/include/c++/9/bits/unique_ptr.h:360 #11 0x7f20d6eed8d4 in
[Spectacle] [Bug 454490] [Plasma workspace] Spectacle hotkeys hardcoded (?) in Wayland
https://bugs.kde.org/show_bug.cgi?id=454490 César Augusto Montoya Ocampo changed: What|Removed |Added Version|unspecified |22.04.1 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 454490] New: [Plasma workspace] Spectacle hotkeys hardcoded (?) in Wayland
https://bugs.kde.org/show_bug.cgi?id=454490 Bug ID: 454490 Summary: [Plasma workspace] Spectacle hotkeys hardcoded (?) in Wayland Product: Spectacle Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: sprit152...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 149266 --> https://bugs.kde.org/attachment.cgi?id=149266=edit Absolutely unbinded shortcuts for spectacle and the notification about the screenshot can be seen SUMMARY When using Plasma (Wayland) the shortcuts for spectacle are hardcoded and cannot be unbinded STEPS TO REPRODUCE 1. Log in a Plasma (Wayland) session 2. Press Ctrl + PrntScrn or PrtnScrn OBSERVED RESULT Plasma workspace tries to take a screenshot using spectacle EXPECTED RESULT No action should be performed as the shortcuts are not binded in the System Settings → Shortcuts section SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 Kernel Version: 5.17.9-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Issue is not present in Plasma (Xorg) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 424090] Add emoji font selection
https://bugs.kde.org/show_bug.cgi?id=424090 César Augusto Montoya Ocampo changed: What|Removed |Added CC||sprit152...@gmail.com --- Comment #2 from César Augusto Montoya Ocampo --- I want this feature too. Up -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 440163] New: Hotkeys using shift + numbers inconsistent between keyboard layouts
https://bugs.kde.org/show_bug.cgi?id=440163 Bug ID: 440163 Summary: Hotkeys using shift + numbers inconsistent between keyboard layouts Product: systemsettings Version: 5.22.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: sprit152...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 140262 --> https://bugs.kde.org/attachment.cgi?id=140262=edit The shortcut is mapped as Meta + $, instead of Meta + Shift + 4 SUMMARY If you add a custom shortcut using Shift + [0..9] it will save the character formed using Shift + that number, e.g. "Meta + Shift + 1" produces "!", "Meta + Shift + 4" produces "$", this is a problem when you have various keyboard layouts that assign different characters to it. STEPS TO REPRODUCE 1. Assign any shortcut to Shift + [0..9] 2. Change to another layout that changes the character in that number OBSERVED RESULT The shortcut is not valid anymore EXPECTED RESULT The shortcut should work anyways. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.13.4-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The expected result would be for the shortcut to work anyways, I guess it can be solved changing how the mapping works, instead of saving "$" when I press Shift + 4, save Shift + 4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421749] Plasma desktop crashes when choosing to configure the thermal monitor widget
https://bugs.kde.org/show_bug.cgi?id=421749 César Augusto Montoya Ocampo changed: What|Removed |Added CC||sprit152...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 402916] New: Calligra words crash on save, while creating thumbnail
https://bugs.kde.org/show_bug.cgi?id=402916 Bug ID: 402916 Summary: Calligra words crash on save, while creating thumbnail Product: calligrawords Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: cochisece...@zoho.com Target Milestone: --- Created attachment 117305 --> https://bugs.kde.org/attachment.cgi?id=117305=edit Full backtrace SUMMARY On my system, Calligra words from Manjaro packages and compiled from source crashes when saving (manual or autosave). The backtrace tells the crash happens when creating the thumbnail of the odf file, or in a posterior step, probably while interacting with libfreeimage. Backtrace (full backtrace attached): Thread 1 (Thread 0x7f2ada90 (LWP 11133)): [KCrash Handler] #6 0x7f2ae0ba0bd8 in KoStore::pos() const () at /usr/lib/libkostore.so.16 #7 0x7f2ac88ff549 in FreeImage_ValidateFIF () at /usr/lib/libfreeimage.so.3 #8 0x7f2ac88fa3c6 in FreeImage_GetFileTypeFromHandle () at /usr/lib/libfreeimage.so.3 #9 0x7f2ac9362580 in FreeImageHandler::GetFIF(QIODevice*, QByteArray const&) () at /usr/lib/qt/plugins/imageformats/libxfreeimage.so #10 0x7f2ac9363c65 in FreeimageQt5Plugin::capabilities(QIODevice*, QByteArray const&) const () at /usr/lib/qt/plugins/imageformats/libxfreeimage.so #11 0x7f2adfe5880a in () at /usr/lib/libQt5Gui.so.5 #12 0x7f2adfe58fac in () at /usr/lib/libQt5Gui.so.5 #13 0x7f2adfe5917c in QImageWriter::write(QImage const&) () at /usr/lib/libQt5Gui.so.5 #14 0x7f2adfe29a0e in QImageData::doImageIO(QImage const*, QImageWriter*, int) const () at /usr/lib/libQt5Gui.so.5 #15 0x7f2adfe29bd8 in QImage::save(QIODevice*, char const*, int) const () at /usr/lib/libQt5Gui.so.5 #16 0x7f2ae21c654d in KoDocument::saveOasisPreview(KoStore*, KoXmlWriter*) () at /usr/lib/libkomain.so.16 #17 0x7f2ae21c69c9 in KoDocument::saveNativeFormatODF(KoStore*, QByteArray const&) () at /usr/lib/libkomain.so.16 #18 0x7f2ae21c7af4 in KoDocument::saveNativeFormat(QString const&) () at /usr/lib/libkomain.so.16 #19 0x7f2ae21c2aee in KoDocument::saveFile() () at /usr/lib/libkomain.so.16 #20 0x7f2ae21cb0e9 in KoDocument::save() () at /usr/lib/libkomain.so.16 #21 0x7f2ae21cc660 in KoDocument::saveAs(QUrl const&) () at /usr/lib/libkomain.so.16 #22 0x7f2ae21db6db in KoMainWindow::saveDocument(bool, bool, int) () at /usr/lib/libkomain.so.16 #23 0x7f2ae21dc8e0 in KoMainWindow::slotFileSave() () at /usr/lib/libkomain.so.16 STEPS TO REPRODUCE 1. Open a document, wait for autosave or try to save manually. OBSERVED RESULT Crash EXPECTED RESULT File saved SOFTWARE/OS VERSIONS freeimage 3.18 KDE Frameworks 5.53.0 Qt Version: 5.12 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 116617] Please add Extended Attribute support (setxattr, getxattr)
https://bugs.kde.org/show_bug.cgi?id=116617 Cochise César changed: What|Removed |Added CC||cochisece...@zoho.com --- Comment #16 from Cochise César --- I'm working on a solution for this. Comments are welcome. https://phabricator.kde.org/D17816 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 316965] Unify Default Applications and File Associations items
https://bugs.kde.org/show_bug.cgi?id=316965 Cochise César changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WORKSFORME |FIXED --- Comment #2 from Cochise César --- Thanks by the heads up. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399883] In new review form, content box have no hint of focus
https://bugs.kde.org/show_bug.cgi?id=399883 --- Comment #5 from Cochise César --- Downstream bug report. https://github.com/lxqt/lxqt/issues/1585 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399883] In new review form, content box have no hint of focus
https://bugs.kde.org/show_bug.cgi?id=399883 --- Comment #3 from Cochise César --- I'm using Fusion, but this was not the significant part. Running Discover in a Plasma session there is no bug with all widget styles I tested (even some very uncommon). The screenshots where taken in a LXQt session. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399883] In new review form, content box have no hint of focus
https://bugs.kde.org/show_bug.cgi?id=399883 --- Comment #1 from Cochise César --- Created attachment 115680 --> https://bugs.kde.org/attachment.cgi?id=115680=edit Revieu content with text, but no boders. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399883] New: In new review form, content box have no hint of focus
https://bugs.kde.org/show_bug.cgi?id=399883 Bug ID: 399883 Summary: In new review form, content box have no hint of focus Product: Discover Version: 5.14.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: cochisece...@zoho.com Target Milestone: --- Created attachment 115679 --> https://bugs.kde.org/attachment.cgi?id=115679=edit Review contento with focus, SUMMARY In the the new review form, the review content box have no borders and show no hint of focus. The review title box have borders and show a blue border and a blinking cursor when have focus. STEPS TO REPRODUCE 1. Open the dialog to add a new review to an application. 2. 3. OBSERVED RESULT The review content input box shows no hint of activation. EXPECTED RESULT Every focusable widget should show if it has focus. SOFTWARE VERSIONS (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.
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 --- Comment #25 from Cochise César <cochisece...@zoho.com> --- (In reply to ocumo from comment #24) > "What are the sidebar advantages?" > Again. Just to repeat one of them: tree view. > And again: not just the sidebar, but also this: Multiple splitting. Then, let me be more clear: "What are the advantages of *bookmarks/history* in sidebar over the other views?" Tree view is for file system hierarchy, so your answer is out of the scope of my question. I can think in some: - consistency with other browsers - easy of access > For the record, neither History dialog, Bookmarks bar, and so on have > anything to do with side tree view. The bug is about the sidebar, not only about the tree view plugin. The sidebar have also plugins for History and Bookmarks. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 --- Comment #23 from Cochise César <cochisece...@zoho.com> --- Alex6: WebDAV is implemented in KIO level, not in Dolphin or Konqueror, so, any KDE application have WebDAV support. You can use multiple tabs and split each tab in dolphin. The only resource not supported is rendering HTML interfaces. Everyone complaining about Dolphin: Dolphin is light, just as a file manager needs to be. (https://my.mixtape.moe/prebrn.png) It not aims to replace Konqueror for power users, but to be usable for "average users". The focus is not web, but file search integration. It was born in KDE 4.0 days and when "semantik desktop" was the aim. As KHTML and QtWebKit started to lack behind other browser engines Konqueror lost traction, not only as a web browser, but as file manager. As free software, is up to users to fix it. = As a little contribution to the discussion: There is a History dialog and Bookmarks bar, menu and dialog. What are the sidebar advantages? There are KIOs for file creation history (recentdocuments://) and access history (timeline://). Maybe the best way to solve this is create a KIO for web bookmarks and other for web history and make a sidebar capable of interacting with any KIO, so this data wold be system accessible and the KIOs used in Dolphin would be available em Konqueror took. -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 374673] No acquiring icons
https://bugs.kde.org/show_bug.cgi?id=374673 --- Comment #2 from Cochise César <cochisece...@zoho.com> --- Listing the files in other icon themes, they go in "status" folder. $ yaourt -Ql faenza-icon-theme |grep acquiring faenza-icon-theme /usr/share/icons/Faenza-Dark/status/scalable/network-cellular-signal-acquiring-symbolic.svg faenza-icon-theme /usr/share/icons/Faenza-Dark/status/scalable/network-vpn-acquiring-symbolic.svg faenza-icon-theme /usr/share/icons/Faenza-Dark/status/scalable/network-wired-acquiring-symbolic.svg faenza-icon-theme /usr/share/icons/Faenza-Dark/status/scalable/network-wireless-acquiring-symbolic.svg faenza-icon-theme /usr/share/icons/Faenza/status/scalable/network-cellular-signal-acquiring-symbolic.svg faenza-icon-theme /usr/share/icons/Faenza/status/scalable/network-vpn-acquiring-symbolic.svg faenza-icon-theme /usr/share/icons/Faenza/status/scalable/network-wired-acquiring-symbolic.svg faenza-icon-theme /usr/share/icons/Faenza/status/scalable/network-wireless-acquiring-symbolic.svg -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 374673] New: No acquiring icons
https://bugs.kde.org/show_bug.cgi?id=374673 Bug ID: 374673 Summary: No acquiring icons Product: Oxygen Version: 5.8.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: icons Assignee: n...@oxygen-icons.org Reporter: cochisece...@zoho.com Target Milestone: --- The icon theme don't have the network-wireless-acquiring or any other icon that means the connection is being configured. In Plasma NM Applet this is not a problem, as the plasmoid have a visual feedback, but when using the theme with another nm manager, like nm-tray, the acquiring state have no visual feedback. Reference: https://github.com/palinek/nm-tray/issues/4 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 374672] No acquiring icons
https://bugs.kde.org/show_bug.cgi?id=374672 Cochise César <cochisece...@zoho.com> changed: What|Removed |Added Severity|normal |minor -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 374672] New: No acquiring icons
https://bugs.kde.org/show_bug.cgi?id=374672 Bug ID: 374672 Summary: No acquiring icons Product: Breeze Version: 5.8.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: cochisece...@zoho.com CC: kain...@gmail.com Target Milestone: --- The icon theme don't have the network-wireless-acquiring or any other icon that means the connection is being configured. In Plasma NM Applet this is not a problem, as the plasmoid have a visual feedback, but when using the theme with another nm manager, like nm-tray, the acquiring state have no visual feedback. Reference: https://github.com/palinek/nm-tray/issues/4 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 --- Comment #9 from Cochise César <cochisece...@zoho.com> --- After seeing the actual code, it is a relatively small codebase (5,1 kloc) and is highly modular, so porting it to frameworks five is a activity I can pick. Maybe I can fix the base and the history plugin for the next release. But I not able to discuss what would be he best solution in long term. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar
https://bugs.kde.org/show_bug.cgi?id=373824 Cochise César <cochisece...@gmail.com> changed: What|Removed |Added CC||cochisece...@gmail.com --- Comment #7 from Cochise César <cochisece...@gmail.com> --- Ths sidebar itself is a feature, I think is important. And inside the sidebar we can have extensions/plugins/watheraver, and it is up to community making tis extensions. Can you point where are the sidebar code right now? I wanto to see if it is hard to port to kf5. Thanks. -- You are receiving this mail because: You are watching all bug changes.
