[ghostwriter] [Bug 479049] New: feature request: more shortcuts
https://bugs.kde.org/show_bug.cgi?id=479049 Bug ID: 479049 Summary: feature request: more shortcuts Classification: Applications Product: ghostwriter Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: i...@vivaldi.net Target Milestone: --- Though I've generally had a positive experience by switching from VSCode & document editors to Ghostwriter, the absence of some gestures is inconvenient. Notably, what I would be happy to see: - up arrow key could function like the Home button when the cursor is at the first line of a file. - down arrow key could function like the End button when the cursor is at the last line of a file. - `ctrl+[` & `ctrl+]` for indenting selected line(s). This differs from using tab to indent the current line, as when nothing is selected, a tab inserts spaces/tabs at the current cursor position; `ctrl+[` would instead indent from the beginning of the line. - Though you can technically get Tab to work this way mid-line via shift-select shenanigans, it is a needlessly hackier solution. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 473025] New: Crashing a lot now.
https://bugs.kde.org/show_bug.cgi?id=473025 Bug ID: 473025 Summary: Crashing a lot now. Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: ernie...@hotmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.22.3 (22.12.3)) Qt Version: 5.15.9 Frameworks Version: 5.105.0 Operating System: Linux 6.4.7-100.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.27.4 [KCrashBackend] -- Information about the crash: Normal usage, i have been flipping between terminal and browser as part of normal dev. as part of a game dev ive been using the mouse wheel a lot with the dragging action of the mouse on the browser. however flipping back to the terminal (using emacs -nw), it crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x7ff7c54cd965 in QObject::~QObject() () from /lib64/libQt5Core.so.5 #5 0x7ff7c551a2a2 in QTextStream::~QTextStream() () from /lib64/libQt5Core.so.5 #6 0x7ff7c53d65f4 in QDebug::~QDebug() () from /lib64/libQt5Core.so.5 #7 0x563ab65fb5aa in Akonadi::Server::NotificationSubscriber::socketDisconnected() () #8 0x7ff7c54d0fc6 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7ff7c54d114f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7ff7c5a8459c in QAbstractSocket::disconnectFromHost() () from /lib64/libQt5Network.so.5 #11 0x7ff7c5a84ddd in QAbstractSocketPrivate::canReadNotification() () from /lib64/libQt5Network.so.5 #12 0x7ff7c5a9acd9 in QReadNotifier::event(QEvent*) () from /lib64/libQt5Network.so.5 #13 0x7ff7c549d5fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7ff7c54ef15f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #15 0x7ff7c3718c7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #16 0x7ff7c376f118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #17 0x7ff7c3715f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #18 0x7ff7c54ee71a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7ff7c549c06a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7ff7c52e71ba in QThread::exec() () from /lib64/libQt5Core.so.5 #21 0x7ff7c52e855b in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #22 0x7ff7c4cae12d in start_thread () from /lib64/libc.so.6 #23 0x7ff7c4d2fbc0 in clone3 () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff7b3dff6c0 (LWP 2480) "QDBusConnection"): #1 0x7ff7c4cf4efd in clock_gettime@GLIBC_2.2.5 () from /lib64/libc.so.6 #2 0x7ff7c54ee025 in qt_gettime() () from /lib64/libQt5Core.so.5 #3 0x7ff7c54ec9dd in QTimerInfoList::updateCurrentTime() () from /lib64/libQt5Core.so.5 #4 0x7ff7c54ece19 in QTimerInfoList::timerWait(timespec&) () from /lib64/libQt5Core.so.5 #5 0x7ff7c54ee98e in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #6 0x7ff7c3718829 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #7 0x7ff7c376ef03 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #8 0x7ff7c3715f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #9 0x7ff7c54ee736 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #10 0x7ff7c549c06a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #11 0x7ff7c52e71ba in QThread::exec() () from /lib64/libQt5Core.so.5 #12 0x7ff7c58c1b1b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #13 0x7ff7c52e855b in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #14 0x7ff7c4cae12d in start_thread () from /lib64/libc.so.6 #15 0x7ff7c4d2fbc0 in clone3 () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff7c3d31940 (LWP 2476) "akonadiserver"): #1 0x7ff7c376f08d in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7ff7c3715f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7ff7c54ee71a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7ff7c549c06a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff7c54a4132 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #6 0x563ab6531058 in main () [Inferior 1 (process 2476) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472915] Drag drop moving email in Thunderbird and desktop environment crashed
https://bugs.kde.org/show_bug.cgi?id=472915 --- Comment #1 from Ernie --- Created attachment 160698 --> https://bugs.kde.org/attachment.cgi?id=160698&action=edit New crash information added by DrKonqi akonadiserver (5.22.3 (22.12.3)) using Qt 5.15.9 I was developing an angular app, 1. running ng serve 2. running ng test 3. editing in emacs (-nw) 4. running podman 5. using firefox. It always occurd when i was scrolling around on the web page (i was developing), particularaly using the mouse wheel... -- Backtrace (Reduced): #4 0x55ff2bfb129b in Akonadi::Server::AkonadiServer::connectionDisconnected() () #5 0x7f393d6c8264 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #6 0x7f393d69d5fb in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #7 0x7f393d6a0984 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #8 0x7f393d6eec27 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 472915] Drag drop moving email in Thunderbird and desktop environment crashed
https://bugs.kde.org/show_bug.cgi?id=472915 Ernie changed: What|Removed |Added CC||ernie...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 452403] Okular needs ability to sanitize and redact PDF (and possibly other types of) documents.
https://bugs.kde.org/show_bug.cgi?id=452403 Ernie changed: What|Removed |Added CC||gother@gmail.com --- Comment #1 from Ernie --- This is seriously an important feature and it's almost always premium, it would make a lot of people switch from Adobe Acrobat Pro probably -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #377 from Ernie --- It's worth every bit of $25 to me if I had assurance that it would get done. It's worth nothing to me without a commitment after what? 6 years? I've lost pretty much all faith in KDE developers. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Sep 10, 2020 at 4:14 PM Donald Krebs wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > --- Comment #376 from Donald Krebs --- > I just added $25 to the bounty program. > I'm not a developer, just an old guy that enjoys building and maintaining > sites for friends and groups I want to support. > Way back when... I settled on a work flow that was easy and... fun. With > WordPress open on a Virtual Desktop (with a blue background), Chrome open > on another, (with a yellow background), and a Google Doc on another (with a > black background). The work flow was comfortable and intuitive. > Since losing the unique backgrounds, I find myself thinking "this used to > be easier." > I tried using "activities" but I abandoned it. It seems like adding > complexity to something that was valuable because of its simplicity. > Ditto using an app. Learning how to use the app took time and > concentration... once again, adding complexity to achieve simplicity. > My little arrangement is so simple that I get by without the feature I once > made use of. > I must admit that whenever I read through this thread, I'm a bit resentful > and more than a little perplexed. What developer thinks it's a good idea to > REMOVE features? Isn't it your job to improve and simplify your product? > Adding features and capabilities? > I changed the default $15 bounty to $25 because, in my mind, that's about > what I would be willing to pay for an app that would do nothing more than > allow unique backgrounds on Virtual Desktops. > For an eighty year old hobbyist living on Social Security, that $25 is > precious. > Forgive my rambling but one last thing... consider this a challenge. What > is it worth to YOU to get this done and put behind us? > > Donald Krebs - mobile > > On Thu, Sep 10, 2020, 1:47 PM wrote: > > > https://bugs.kde.org/show_bug.cgi?id=341143 > > > > --- Comment #374 from abrah...@acm.org --- > > I'm one of the early complainers about the loss of different wallpapers > on > > different desktops. I'd be quite happy if different activities could > have > > different wallpapers and I could just think of activities as being > desktops > > with some additional properties I'd never use. If I could just think of > > activities as desktops called something else, I and presumably most of > the > > other unhappy users would be satisfied. > > > > -- > > You are receiving this mail because: > > You are on the CC list for the bug. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #373 from Ernie --- I'd be happy to kick in $15 if I had a commitment from KDE to fix this within 6 months. After 6 years, I have little faith that they will follow through. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Sep 10, 2020 at 11:42 AM edpil02 wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > --- Comment #372 from edpil02 --- > Just add a $15 bounty too. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #365 from Ernie --- I disagree with point B. If you are right, there is no point in continuing this argument OR to offer a bounty. The mysterious "powers that be" at KDE will do nothing. Conversely, is there are any developers left that actually care what the community thinks, I believe we should continue to ask questions and voice displeasure with the lack of action. Call it a peaceful protest.If there are a couple dozen comments on this bug every day, maybe we will get action. On Wed, Sep 9, 2020 at 3:44 PM Filip Fila wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > --- Comment #364 from Filip Fila --- > Guys it's been a long time and you can clearly see that: a) this isn't a > priority for developers; b) complaining has an adverse effect on their > interest > > I sympathize with all of you since I used to fervently lobby for my > issues. I > couldn't understand why developers didn't view some of them as important. > Eventually I switched my approach to trying to change as much as I could > myself, although that wasn't much. After some time, that evolved into > seeing > that, in the greater scheme of things and life, the desire to have my > computer > environment be exactly how I want it to be really isn't too important. > > Maybe my experience can resonate with some of you. Besides, ancient wisdom > says > we should try to cease worrying over all the things we have no influence > over. > > But if you still feel strongly about this, the only thing I see as a way > out is > to create a bounty of sorts that someone would then be more likely to take > you > up on instead of working pro bono. But as most main KDE developers are > already > paid to work on KDE, it would most likely have to be someone else doing the > work... which given that they would not be a maintainer makes it > impossible to > guarantee that their patches would get accepted. So it seems to me that a > reasonable path forward is to first communicate with developers if they > would > be open to a patch from a third-party via a bounty. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #351 from Ernie --- Nate Graham, I read the comments at the link you provided. I was particularly astounded by: "*other things were deemed either more important or more feasible to fix by the people doing the work*". My question is deemed by WHO? Certainly in the YEARS since developers removed a useful and sorely missed feature, someone has had time to address the issue. I realize that developers have decided that the wishes of the community are less important than Anthropological Global Warming, but like AGW, the fact that different wall papers on virtual desktops are unimportant to users is a myth. Yeah. I know that users sending bitches about a feature they want returned to KDE is unproductive as far as fixing the situation, but it does surely indicate the importance in the work flow of users. I recommend users who are still interested in seeing the issue resolved keep asking for progress reports and confirming that for the average user, this is not a trivial matter. " On Mon, Sep 7, 2020 at 9:18 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > --- Comment #350 from Nate Graham --- > We've still done nothing. :) > > This blog post I wrote is pretty relevant: > https://pointieststick.com/2020/05/18/why-dont-you-just-fix-thing-already/ > > TL;DR: people capable of doing this are all working on other things which > can > also only be done by them which are more important and impactful, such as > making the Wayland session usable. Ultimately we need more developers to > keep > doing stuff like that and also this. > > I know that's not what people want to hear, but it's what I've got for you, > sorry. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #348 from Ernie --- Christoph Feck! So all you can add is don't leave comments? A status update from time to time would be appreciated. The only thing tat gets a response is a few days of bitching by dozens of people who have been kept in the dark for years. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Bring back per-virtual-desktop wallpapers
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #342 from Ernie --- I've seen over the past few years several comments by the Gods at KDE either telling us that it couldn't be done, it wouldn't be done, or it is in the works. Which is it? Are the developers so committed to a colossal mirtake that they would "lose face" if they reverted or is it that they think the noise will just go away? I've seen fixes by users that kind of work but never a KDE update that includes a fix. I'd really like to know what the developers think and if there's any possibility of getting back one of the features that made me a KDE user nearly 25 years ago. On Thu, Sep 3, 2020 at 1:58 PM lp wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > lp changed: > >What|Removed |Added > > > CC||paul...@gmail.com > > --- Comment #341 from lp --- > I would also like this feature back. Or alternatively, to have an activity > switcher which is comparable in features with the "desktop grid" effect. > > During work, when my desktop becomes overcrowded, I summon the desktop > grid and > quickly drag some windows to another desktop. This cannot be easily done > with > activities. Although the activity pager allows dragging, it has no preview > which makes it very unpractical, also it is small. > > The different background are just a clue to distinguish one desktop from > the > other when flipping through. Also note that Vallpaper is not compatible > with > desktop grid: because it changes the wallpaper for all virtual desktops > depending on which is active, hence they all look have the wallpaper of the > last active one in grid view. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #242 from Ernie --- Well said On Mar 6, 2017 3:37 PM, "Jay" wrote: > https://bugs.kde.org/show_bug.cgi?id=341143 > > Jay changed: > >What|Removed |Added > > > CC||atlp...@excite.com > > --- Comment #241 from Jay --- > For all the good things in Plasma 5, they are worthless owing to the loss > of > ability to set different wallpaper for each virtual desktop. That's how I > keep > track of which desktop I'm working in. It greatly aided efficiency. > > Without this vital feature, I'm better off using XFCE because it boots two > seconds faster and has fewer parts that kill the DE when things get messed > up. > I've always used XFCE to recover from fatal KDE errors. Might as well use > it > for my DE. > > Thanks to the KDE team for the many years of wonderful Plasma pre-5. I > look > forward to your new programs and features. There are better DE's than > Plasma > when there's no wallpaper difference, especially when KDE's other great > features are loaded into XFCE. > > -- > You are receiving this mail because: > You are on the CC list for the bug. -- You are receiving this mail because: You are watching all bug changes.
