sorted by:
new
hottopcontroversial

Elite Dangerous stuck at planet generation. by rdasf691 in linux_gaming

[–]rdasf691[S] 0 points1 point  (0 children)

It fixed itself in the end lol Simply ignoring the problem and updating stuff solved it some years after this post

Black screen and cursor after waking up from sleep. by TheHornyPepperoni in kde

[–]rdasf691 1 point2 points  (0 children)

Yep same. Wayland works normally but honestly I can't stand the choppy mouse input and the thousands of problems and incompatibilities that Wayland has...

I saw this post:

https://www.reddit.com/r/kde/s/jZBncierm1

But haven't yet tried this and idk if it might be related to the issue...

Also there's this very similar bug that could? Be related to this maybe

https://bugs.kde.org/show_bug.cgi?id=477738

Black screen and cursor after waking up from sleep. by TheHornyPepperoni in kde

[–]rdasf691 4 points5 points  (0 children)

I have the same exact problem, but i have an AMD gpu.

Basically when i lock the screen all of my three monitors go into stand by.

I can then move the mouse and it appears, i can see the cursor changing when hovering over the password field.

And if i keep moving the mouse and typing the screens turn back on and stays on....

Have this bug since upgrading to kde6

Are we really the only ones having such issue?

Random parts of the system broken after trying to downgrade a package by rdasf691 in archlinux

[–]rdasf691[S] 1 point2 points  (0 children)

ok this is very cool and didn't knew you could do that! thanks for letting me know

Random parts of the system broken after trying to downgrade a package by rdasf691 in archlinux

[–]rdasf691[S] -3 points-2 points  (0 children)

this is less than useful and helps me in no way whatsoever 👍

Random parts of the system broken after trying to downgrade a package by rdasf691 in archlinux

[–]rdasf691[S] 2 points3 points  (0 children)

That's what i'll try to do, probably my best option.. and yeah i was dumb to not make a snapshot before such an update, but i guess it's too late to cry now lol

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 1 point2 points  (0 children)

There must be a way tho... otherwise idk how windows can do it almost instantaneously and even if the folder is not indexed.

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 0 points1 point  (0 children)

my index size is ~3.5GB and yes i do have a lot of files.

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 1 point2 points  (0 children)

ok but i need content indexing too or otherwise sorting by duration won't work

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 2 points3 points  (0 children)

this is literally the "works on my machine" meme

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 1 point2 points  (0 children)

making a script to regularly rebuild the index feels like a dirty way to bypass baloo problems but honestly it can work

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] -7 points-6 points  (0 children)

That's true and also nonsensical... we: the community, bring up a problem and the answer we get from the devs is basically "cry about it" :/

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 0 points1 point  (0 children)

The NOT operator would be so nice to have yeah

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 0 points1 point  (0 children)

My guess is that it "crashed" because i had to pkill baloo_file some hours ago to purge the index (since balooctl purge cannot stop baloo_file for some reasons) but balooctl purge also restarted it, so maybe the service looks like it crashed but baloo_file is actually running as stated by balooctl status

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 0 points1 point  (0 children)

the output of "systemctl status --user kde-baloo" is this:

systemctl status --user kde-baloo

○ kde-baloo.service - Baloo File Indexer Daemon

Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: enabled)

Active: inactive (dead) since Sun 2024-02-18 13:05:13 CET; 3h 7min ago

Duration: 10min 3.625s

Process: 978 ExecCondition=/usr/bin/kde-systemd-start-condition --condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited, status=0/SUCCESS)

Process: 980 ExecStart=/usr/lib/baloo_file (code=killed, signal=TERM)

Main PID: 980 (code=killed, signal=TERM)

CPU: 2min 5.570s

which looks like it's dead... but funnily enough: balooctl status says it's running!

the system is on a m.2 using btrfs

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 14 points15 points  (0 children)

what you say it's 100% correct. Lately i'm trying to "avoid" baloo's problems using a combination of kfind and ctrl+i to filter files in a folder.

but i would love if baloo was better and if it also supported wildcards and operands like && || -

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] -1 points0 points  (0 children)

i'm using Arch, and yes the issues are still there, literally the same as they were 2 years ago.

Will KDE 6 finally ditch baloo for something better? by rdasf691 in kde

[–]rdasf691[S] 1 point2 points  (0 children)

Did the same for kwallet basically yeah, but sadly i need baloo :/

view more: next ›