https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #58 from Joachim Wagner ---
For those of us who cannot install a patch, what version of KDE do we need to
wait for? Will it go into 5.27.6?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343526
Joachim Wagner changed:
What|Removed |Added
Version|unspecified |4.1.22082
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=343526
--- Comment #7 from Joachim Wagner ---
Also confirmed in Kompare 4.1.22082 of KDE 5.99.0 + Qt 5.15.6 in openSUSE
Tumbleweed 2022-10-31.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=343526
Joachim Wagner changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=343526
--- Comment #5 from Joachim Wagner ---
Actually, the improvement seems to be fully due to the bigger screen I have
now. If I shrink the window to approximately the size of the screenshot in
comment 2 from 2015, the 1st digit in the left column
https://bugs.kde.org/show_bug.cgi?id=343526
--- Comment #4 from Joachim Wagner ---
Is Kompare 4.1.3 shipped with openSUSE Leap 15.3 recent enough? Both columns
have improved. The target file column shows all 5 digits. However, the source
file column (left), shows the first of the 5 digits only
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #44 from Joachim Wagner ---
> [...] home drive mounted with different
> minor device numbers
This phrasing is likely to cause confusion. Better to refer to the value
`stat.st_dev` that is used by baloo and that does not have a
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #39 from Joachim Wagner ---
(In reply to tagwerk19 from comment #38)
> Symlinks provide a bit of an edge case :-)
> [...]
> Does the "mount point" idea work here?
I don't know the internals of the indexer implementa
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #37 from Joachim Wagner ---
(In reply to tagwerk19 from comment #35)
> Accepted.
> Although I think we need to look at "what we can trust most".
> [...]
> This would mean including the filesystem ID in your "I&
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #34 from Joachim Wagner ---
(In reply to tagwerk19 from comment #33)
> statvfs and "stat -f" give a 64 bit "Filesystem ID" and I was imagining you
> were talking about that.
No, I meant "baloo-internal
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #32 from Joachim Wagner ---
(In reply to tagwerk19 from comment #31)
> Apologies, I fear you'll have to step through your process for me. I'm
> somehow missing something...
> [...]
> The mapping would have to work whe
https://bugs.kde.org/show_bug.cgi?id=448451
Bug ID: 448451
Summary: ksysguard, the kde system monitor, makes wrong
assumption about block devices
Product: ksysguard
Version: unspecified
Platform: openSUSE RPMs
https://bugs.kde.org/show_bug.cgi?id=402154
--- Comment #29 from Joachim Wagner ---
An alternative to relying on UUIDs and sub-volume IDs is to assume mount points
of filesystems do not change and to proceed as follows:
* Have a persistent table `I` mapping mount points to internal filesystem
https://bugs.kde.org/show_bug.cgi?id=402154
Joachim Wagner changed:
What|Removed |Added
CC||jwag...@computing.dcu.ie
--- Comment #28 from
https://bugs.kde.org/show_bug.cgi?id=413694
--- Comment #10 from Joachim Wagner ---
Yes, thanks. My logs confirm the re-indexing co-occurs with the use of a new
virtual device number for the btrfs filesystem.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=404057
Joachim Wagner changed:
What|Removed |Added
CC||jwag...@computing.dcu.ie
--- Comment #42 from
https://bugs.kde.org/show_bug.cgi?id=413694
--- Comment #8 from Joachim Wagner ---
Re the idea of recording the sha256 of each file, this may be problematic for
large files with only a small content area such as meta data and subtitles of a
video. Still, reading excessive amounts of data can be
https://bugs.kde.org/show_bug.cgi?id=413694
Joachim Wagner changed:
What|Removed |Added
CC||jwag...@computing.dcu.ie
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=283682
--- Comment #211 from Joachim Wagner ---
(In reply to Tristan Miller from comment #202)
> [...] because the problem has been fixed or because it has driven most of
> the user base away. I'd love to return to using KMail [...]
I didn&#
https://bugs.kde.org/show_bug.cgi?id=388302
Joachim Wagner changed:
What|Removed |Added
Version|5.7.2 |5.7.3
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=388302
Joachim Wagner changed:
What|Removed |Added
CC||jwag...@computing.dcu.ie
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=305849
--- Comment #9 from Joachim Wagner ---
Reading my old comment #5 an alternative to implementing smooth scrolling would
be to allow the user to change the number of displayed weeks. If 8 weeks were
shown I could now see all the way to the 20th of May
https://bugs.kde.org/show_bug.cgi?id=305849
--- Comment #8 from Joachim Wagner ---
Kontact is a container. The relevant project is KOrganizer and
https://cgit.kde.org/korganizer.git/log/ shows some activity. It seems that the
developers rate this feature request just high enough to not close it
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #48 from Joachim Wagner ---
It's also still around 9.5% CPU usage in a VM with KVM and both guest and host
using current OpenSUSE Leap 42.3 in a default setup. That's KDE 5.8.7.
For sddm-greeter instead of kscreenlocker_g
https://bugs.kde.org/show_bug.cgi?id=283682
--- Comment #186 from Joachim Wagner ---
As to "manually filtered" (comment #185), please distinguish between "manually
applied filters (menu: Message --> Apply Filter)" and "manually filtered by
moving messages between fol
https://bugs.kde.org/show_bug.cgi?id=326884
--- Comment #3 from Joachim Wagner ---
As explained in the 2nd paragraph of the initial report, the bug was already
fixed in 4.11.2 and the purpose of the report was to document a workaround for
other people running into this bug with older versions
https://bugs.kde.org/show_bug.cgi?id=297615
--- Comment #11 from Joachim Wagner ---
The unexpected behaviour is still present in KMail5 (tested with version 16.08
of current OpenSUSE Leap 42.2). However, reading comment #5 and observing that
"New Email Notify" boxes pop up even if kma
https://bugs.kde.org/show_bug.cgi?id=283682
--- Comment #162 from Joachim Wagner ---
Note that testing for a few hours might not be enough. Last time I tried, the
bug only showed after 2-3 weeks of daily use. That's also why I'm hesitant
about trying it again.
It would be nice if som
https://bugs.kde.org/show_bug.cgi?id=305849
Joachim Wagner changed:
What|Removed |Added
CC||jwag...@computing.dcu.ie
--- Comment #5 from
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #32 from Joachim Wagner ---
(In reply to Martin Gräßlin from comment #30)
> According to the backtrace: you are using llvmpipe, which means OpenGL is
> emulated on the CPU. Of course that's not going to be efficient.
This i
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #29 from Joachim Wagner ---
Maybe useful to see which of the above threads consumes CPU (command "top" + H
for threads):
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
3557 sddm 20 0 894
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #28 from Joachim Wagner ---
Thanks for providing the command. Note to others: "help t", "help t a", etc. on
the gdb prompt tells you what it does.
(gdb) help t a a
Apply a command to all threads.
(gdb) t a a
https://bugs.kde.org/show_bug.cgi?id=316348
--- Comment #26 from Joachim Wagner ---
On OpenSUSE Leap 42.1
(steps: find pid, e.g. from "top", run gdb -p pid and enter "backtrace" on the
"(gdb)" prompt)
#0 0x7fa9073eebbd in poll () at /lib64/libc.so.6
#1 0x0
33 matches
Mail list logo
