https://bugs.kde.org/show_bug.cgi?id=359819
Kevin Kofler changed:
What|Removed |Added
Version Fixed In||2.1.0
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=314451
Kevin Kofler changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Summary|sftp: Resuming partly
https://bugs.kde.org/show_bug.cgi?id=367639
--- Comment #53 from Kevin Kofler ---
In these commits, I see things like ,ms[0] == 0 or ms[1] != 0, where ms is a
QStringList, so you are comparing a QString against 0. This doesn't look right.
Either use isEmpty() or compare with the stri
https://bugs.kde.org/show_bug.cgi?id=372094
Bug ID: 372094
Summary: Please restore wodim support
Product: k3b
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: major
https://bugs.kde.org/show_bug.cgi?id=372094
--- Comment #1 from Kevin Kofler ---
I will also note that your changes have several logic errors:
-: K3b::AbstractCdrtoolsProgram( QLatin1String( "cdrecord" ),
QLatin1String( "wodim" ) )
+: K3b::AbstractCdrtoolsPr
https://bugs.kde.org/show_bug.cgi?id=372094
--- Comment #2 from Kevin Kofler ---
And in the long run, to work with something maintained, see wishlist bug
#137436.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=137436
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--- Comment #15 from
https://bugs.kde.org/show_bug.cgi?id=372094
--- Comment #3 from Kevin Kofler ---
Also, your change is labeled "Use cdrecord for burning blueray instead of
wodim.", but K3b did not attempt to use wodim to burn BluRay even before your
change. If you look more closely at the code you re
https://bugs.kde.org/show_bug.cgi?id=137436
--- Comment #16 from Kevin Kofler ---
There are actually 4 options to use libburnia:
* cdrskin (cdrecord-like CLI, needs minimal changes, but you should still
detect it and disable cdrecord-specific workarounds for it, similarly to how
wodim is handled
https://bugs.kde.org/show_bug.cgi?id=137436
--- Comment #17 from Kevin Kofler ---
Of course, there are also options for standalone ISO generation:
* to go with cdrskin (drop-in replacement for cdrecord), there is a xorrisofs
command (actually implemented by xorriso) that is a drop-in replacement
https://bugs.kde.org/show_bug.cgi?id=372094
--- Comment #6 from Kevin Kofler ---
Removing working detection code just because you did not understand what it
really does is not helpful. Especially when your "fixes" actually make the code
misbehave on our distribution. And answering a
https://bugs.kde.org/show_bug.cgi?id=372094
--- Comment #7 from Kevin Kofler ---
And we will default to libburnia if you add tested support for it. But I object
to removing wodim support before a replacement is ready. We cannot use cdrecord
in Fedora.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=372094
--- Comment #9 from Kevin Kofler ---
> but I want to ship still-maintaining && BUGFREE product to end-users.
I actually agree with you there. I really think we need to switch to libburnia.
You should just clearly communicate this to pac
https://bugs.kde.org/show_bug.cgi?id=372094
--- Comment #10 from Kevin Kofler ---
Also, please keep in mind that cdrtools/cdrkit is not only cdrecord/wodim, but
also mkisofs/genisoimage. You will also want to detect and use xorrisofs from
libburnia, which is likely a better mkisofs replacement
https://bugs.kde.org/show_bug.cgi?id=372094
--- Comment #12 from Kevin Kofler ---
Looks OK to me.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=137436
--- Comment #24 from Kevin Kofler ---
> I think the missing features are covered by cdrdao.
Unfortunately, cdrdao seems also dead upstream (last release in 2009). :-(
The burning tool situation is really sad.
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=137436
--- Comment #25 from Kevin Kofler ---
Latest/last release of:
* cdrkit (wodim, genisoimage): 2010-10-17 (but things like the DVD writing code
have not really been touched for longer than that; after 2007, mostly only
genisoimage got fixes)
* dvd+rw
https://bugs.kde.org/show_bug.cgi?id=372391
Kevin Kofler changed:
What|Removed |Added
URL||https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=372391
Kevin Kofler changed:
What|Removed |Added
Assignee|k...@davidedmundson.co.uk|visual-des...@kde.org
Component
https://bugs.kde.org/show_bug.cgi?id=137436
--- Comment #56 from Kevin Kofler ---
> If the program gets to the case
>else if( d->writingMode == K3b::WritingModeRaw ) {
> then you have no other choice but to refuse burning.
> Actually it should be prevented in the user dialog
https://bugs.kde.org/show_bug.cgi?id=422095
--- Comment #5 from Kevin Kofler ---
Printing to a real printer still sends a bitmap to the printer. As I wrote:
> For output to a physical printer, the only way to avoid the rasterization is
> to use the FilePrinter class from Okular though.
https://bugs.kde.org/show_bug.cgi?id=465675
Kevin Kofler changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=415467
--- Comment #8 from Kevin Kofler ---
FYI, accounts.google.com now also uses the play.google.com domain for some
reason, so you now have to set the same fake user agent also for
play.google.com in addition to accounts.google.com.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=446924
--- Comment #9 from Kevin Kofler ---
(In reply to Nate Graham from comment #5)
> Please do. In fact every distro needs to be individually supported.
As far as I can tell, the code that was added to Discover is not
distribution-specific.
https://bugs.kde.org/show_bug.cgi?id=466248
--- Comment #5 from Kevin Kofler ---
I do not see how that merge request can possibly fix this issue, because
Discover uses native SNI, not xembedsniproxy.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452967
--- Comment #11 from Kevin Kofler ---
Confirmed fixed in 5.25.5:
https://forum.manjaro.org/t/arm-stable-update-2022-09-11-plasma-5-25-5-kde-gear-22-08-thunderbird-102-firefox-104-and-kernels/121546/16?u=kevin_kofler
Thanks!
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=451217
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #220 from Kevin Kofler ---
One issue is that dropping a locale file into a folder for glibc will not be
sufficient to fix it, because Qt does not actually use POSIX locales
internally, but ICU locales, and has a hardcoded mapping from POSIX
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #221 from Kevin Kofler ---
(The POSIX, ICU, and Qt implementations are all based on a closed set of
locales determining all formatting preferences at country granularity. I do not
see that ever changing, because it is a core design
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #226 from Kevin Kofler ---
> Indeed, the date format in the plasma clock widget is already completely
> customizable with a field to enter the format code.
Only if you have it permanently displayed in the tray, which assumes a
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #227 from Kevin Kofler ---
(e.g., the tooltip shows me today's date as "So. Sep. 25 2022" which is a
completely broken format, we do not put the month before the day in Austria)
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=468711
Kevin Kofler changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=468711
--- Comment #4 from Kevin Kofler ---
Normally https://bugreports.qt.io/ but they are not likely to fix this in Qt 5
at this point, only Qt 6 if it is still an issue there.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469962
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=467050
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--- Comment #4 from
https://bugs.kde.org/show_bug.cgi?id=456348
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=456348
--- Comment #21 from Kevin Kofler ---
> FROM:
> cmake ../krusader -DCMAKE_INSTALL_PREFIX=/usr/ -DCMAKE_C_FLAGS="-O2 -fPIC"
> -DCMAKE_CXX_FLAGS="-O2 -fPIC"
> TO:
> cmake ../krusader -DCMAKE_INSTALL_PREFIX=/opt/kru
https://bugs.kde.org/show_bug.cgi?id=456348
--- Comment #22 from Kevin Kofler ---
According to strace, it runs /usr/libexec/kf5/kioslave5 correctly, with
/usr/lib64/qt5/plugins/kio_krarc.so, so the paths seem all right. I guess I
need to strace the kioslave5 process next.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=456348
--- Comment #23 from Kevin Kofler ---
As far as I can tell, the kioslave5 process crashes on startup when using
kio_krarc, which is why it looks unresponsive to Krusader.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456348
--- Comment #24 from Kevin Kofler ---
Using this to debug further:
strace -f kioclient5 ls krarc:/path/to/archive.7z/ 2>&1 | less
I get the same hanging behavior as in Krusader, and indeed, as I suspected, the
kioslave5 child process is segf
https://bugs.kde.org/show_bug.cgi?id=456348
Kevin Kofler changed:
What|Removed |Added
Summary|KrArc freezes, both in |KrArc segfaults the
|Krusader
https://bugs.kde.org/show_bug.cgi?id=456348
Kevin Kofler changed:
What|Removed |Added
URL||https://bugzilla.redhat.com
https://bugs.kde.org/show_bug.cgi?id=456348
Kevin Kofler changed:
What|Removed |Added
CC||fa...@kde.org
--- Comment #26 from Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=415467
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--- Comment #3 from
https://bugs.kde.org/show_bug.cgi?id=415467
--- Comment #7 from Kevin Kofler ---
Thank you for the quick fix. I can confirm that the user agent:
"Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0"
that will be in the new presets with 22.08.02 is currently a
https://bugs.kde.org/show_bug.cgi?id=460239
Bug ID: 460239
Summary: 3D graphs are not plotted on the PinePhone due to
shader error
Classification: Applications
Product: kalgebra
Version: 22.08.1
Platform: Manjaro
https://bugs.kde.org/show_bug.cgi?id=460239
--- Comment #1 from Kevin Kofler ---
And in case it matters:
Kernel version: 5.19.11-1-MANJARO-ARM
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460239
--- Comment #2 from Kevin Kofler ---
And I am using the qt5-es2-{base,declarative,multimedia} (OpenGL ES) builds.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460239
Kevin Kofler changed:
What|Removed |Added
CC||percy.camilo...@gmail.com
Version
https://bugs.kde.org/show_bug.cgi?id=460239
--- Comment #3 from Kevin Kofler ---
Looks like the offending code is actually part of analitza(plot).
I am using: analitza 22.08.1-1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460239
--- Comment #4 from Kevin Kofler ---
Apparently a regression from this 2015 commit:
https://invent.kde.org/education/analitza/-/commit/80a3833ee306ee62ef61126d31fd7649bc7394af
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460239
--- Comment #5 from Kevin Kofler ---
I guess it should say "highp float w = …" instead of "float w = …".
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #269 from Kevin Kofler ---
The problem with the en_SE workaround is: Qt has en_SE, but no en_DK, whereas
glibc has en_DK, but no en_SE.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433181
Kevin Kofler changed:
What|Removed |Added
CC||jurajora...@mailo.com
--- Comment #1 from Kevin
https://bugs.kde.org/show_bug.cgi?id=406375
--- Comment #5 from Kevin Kofler ---
Thanks. Though this is only going to work if the scheme is explicitly allowed,
not if the "allow all unknown schemes" option is used.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406375
--- Comment #6 from Kevin Kofler ---
Or is that option gone anyway? I have seen it while searching the code, but
cannot find it again now.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=406375
--- Comment #7 from Kevin Kofler ---
I see that your code here:
https://invent.kde.org/network/falkon/-/commit/205018775ce1c66b349d6b5a20abcb08e5ed19f6#1fcf115ea7bc0529cad80661
registers the scheme on first use, which is a bit suboptimal because it
https://bugs.kde.org/show_bug.cgi?id=478121
Bug ID: 478121
Summary: Elisa mobile UI: playlist drawer cannot be closed
anymore
Classification: Applications
Product: Elisa
Version: 23.08.3
Platform: Manjaro
https://bugs.kde.org/show_bug.cgi?id=478121
Kevin Kofler changed:
What|Removed |Added
CC||n...@kde.org
--- Comment #1 from Kevin Kofler
https://bugs.kde.org/show_bug.cgi?id=478121
--- Comment #2 from Kevin Kofler ---
This should probably say:
interactive: Kirigami.Settings.isMobile
instead of:
interactive: false
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=478121
Kevin Kofler changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://bugs.kde.org/show_bug.cgi?id=478121
Kevin Kofler changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/mult |https://invent.kde.org/mult
https://bugs.kde.org/show_bug.cgi?id=488187
Bug ID: 488187
Summary: CVE-2024-36041 patches in 6.0.5.1 break
shutdown/restart on X11
Classification: Plasma
Product: plasmashell
Version: 6.0.5
Platform: Fedora RPMs
https://bugs.kde.org/show_bug.cgi?id=488187
--- Comment #4 from Kevin Kofler ---
The plasma-workspace-6.0.5.1-2.fc40 build that the reporter is using already
has this patch applied:
https://src.fedoraproject.org/rpms/plasma-workspace/c/227a33c9b49cb70649c05ac16476f349667d6e36?branch=f40
It does
https://bugs.kde.org/show_bug.cgi?id=488187
--- Comment #5 from Kevin Kofler ---
Maybe we should revert the "Remove iceauth dependency" parts, keep only the
actual security fix, and just add a Requires: iceauth to the package?
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=488187
--- Comment #6 from Kevin Kofler ---
(Though I have not verified whether that fixes it or whether the security fix
alone is already enough to trigger the bug.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488187
--- Comment #8 from Kevin Kofler ---
Quoting the downstream report:
--- Comment [https://bugzilla.redhat.com/show_bug.cgi?id=2290894#c15] from
EpicTux123 ---
Hi there Kevin. Thanks for making it easier for me.
Here you go:
https://0.jaegers.net
https://bugs.kde.org/show_bug.cgi?id=488187
Kevin Kofler changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=488187
--- Comment #10 from Kevin Kofler ---
At what message level is that printed? It might be that the message is not
shown by default on Fedora because the default settings are quite restrictive
to limit terminal spam from KDE applications. At least we
https://bugs.kde.org/show_bug.cgi?id=488187
--- Comment #11 from Kevin Kofler ---
These are the settings we ship:
https://src.fedoraproject.org/rpms/qt6-qtbase/blob/rawhide/f/qtlogging.ini
[Rules]
*.debug=false
qt.qpa.xcb.xcberror.warning=false
But the message appears to be an uncategorized
https://bugs.kde.org/show_bug.cgi?id=488187
--- Comment #14 from Kevin Kofler ---
We already have a duplicate report downstream:
https://bugzilla.redhat.com/show_bug.cgi?id=2291334
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=488187
Kevin Kofler changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #255 from Kevin Kofler ---
I am in general very much for consistency, but being consistently wrong is just
not helpful. Even within a country, there can be distinct regional, local,
ethnical, or personal preferences, so just having these
https://bugs.kde.org/show_bug.cgi?id=340982
--- Comment #256 from Kevin Kofler ---
Also, there is no consistency anyway, since console and GTK applications use
glibc locales, whereas Qt uses ICU locales and only tries to map the glibc
locales to those internally. So you end up with en_DK working
https://bugs.kde.org/show_bug.cgi?id=481584
Bug ID: 481584
Summary: Allow stretched scaling (horizontal ratio ≠ vertical
ratio) on Wayland
Classification: Plasma
Product: KScreen
Version: master
Platform: Manjaro
https://bugs.kde.org/show_bug.cgi?id=484997
--- Comment #7 from Kevin Kofler ---
I don't know who maintains the Flatpak for Kompare on Flathub. I don't.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=484736
--- Comment #1 from Kevin Kofler ---
Kompare can technically be built against KF6 since May 2023. But it was
disabled for the required dependency libkomparediff2:
https://invent.kde.org/sdk/libkomparediff2/-/commit
https://bugs.kde.org/show_bug.cgi?id=480069
--- Comment #1 from Kevin Kofler ---
Sure, this would be nice. But mainly, this needs someone to implement it. There
are then also some concerns about the details, e.g., contrast issues if the
highlighting colors are too close to the background colors
https://bugs.kde.org/show_bug.cgi?id=486463
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=446665
Bug ID: 446665
Summary: Cannot set Addressee birthday from QML (e.g., from
plasma-phonebook)
Product: frameworks-kcontacts
Version: git
Platform: Other
URL: https:/
https://bugs.kde.org/show_bug.cgi?id=452967
--- Comment #1 from Kevin Kofler ---
Ping? (3 more weeks have passed…) Is there anything more you need from me? (I
have already posted GTK Wayland debugging logs that show that the KWin
compositor is delivering the events to the wrong surface, see the
https://bugs.kde.org/show_bug.cgi?id=446665
Kevin Kofler changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=447819
--- Comment #1 from Kevin Kofler ---
Are you sure the title bar is an SSD title bar? I think it is a CSD one.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452967
Bug ID: 452967
Summary: kwin_wayland: touch input does not reach GTK or
Chromium popup menus (subsurfaces)
Product: kwin
Version: 5.24.4
Platform: Manjaro
URL: http
https://bugs.kde.org/show_bug.cgi?id=452967
--- Comment #3 from Kevin Kofler ---
Well, yes, I am not surprised that this can also be reproduced with a
desktop/notebook/tablet with a touch device.
At least, if you are using Plasma Desktop on Fedora KDE, you have the option to
switch to an X11
https://bugs.kde.org/show_bug.cgi?id=446956
--- Comment #3 from Kevin Kofler ---
Well, you can use *any* scanning app to take pictures from a webcam thanks to
the libsane V4L backend… except now Skanpage where you explicitly removed this
useful feature for no good reason.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=449796
--- Comment #2 from Kevin Kofler ---
A lot of features are interesting, but if nobody is willing to implement a
feature, it is not going to happen, sorry.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=441131
--- Comment #3 from Kevin Kofler ---
Looks like there was some actual breakage in the code here, see the proposed
fix at: https://invent.kde.org/sdk/libkomparediff2/-/merge_requests/2
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=449735
--- Comment #8 from Kevin Kofler ---
My main question is: why would we want to use this instead of Akregator?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=436277
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=436277
--- Comment #8 from Kevin Kofler ---
The metadata that the check for updates downloads is already around 20 MB. This
can be more than even the update itself. It is a very bad idea to download that
at 0.009€/MB (20 MB * 0.009 €/MB = 0.18€. At every boot
https://bugs.kde.org/show_bug.cgi?id=436277
--- Comment #9 from Kevin Kofler ---
If you wonder why I know this so precisely: I had mobile data enabled for less
than an hour, with, as I already wrote, two reboots, and the call detail record
has the data usage per connection:
* in the ~45 minutes
https://bugs.kde.org/show_bug.cgi?id=436277
--- Comment #10 from Kevin Kofler ---
If you can live without Discover checking for updates any time at all (even on
WiFi or Ethernet), then:
systemctl --user disable --now app-org.kde.discover.notifier@autostart.service
systemctl --user mask app
https://bugs.kde.org/show_bug.cgi?id=452967
--- Comment #7 from Kevin Kofler ---
Can this bugfix be backported to the upcoming 5.25.4 bugfix release?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452967
--- Comment #8 from Kevin Kofler ---
5.25.4 is scheduled for August 4, so there are 5 days left to backport this.
IMHO, this is a critical bugfix and definitely ought to be backported.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=452967
Kevin Kofler changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=452967
Kevin Kofler changed:
What|Removed |Added
Version Fixed In|5.26|5.25.5
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=432598
Bug ID: 432598
Summary: Marble uses ws.geonames.org, which is gone, should use
api.geonames.org
Product: marble
Version: unspecified
Platform: Fedora RPMs
URL: http
https://bugs.kde.org/show_bug.cgi?id=432598
--- Comment #1 from Kevin Kofler ---
Created attachment 135880
--> https://bugs.kde.org/attachment.cgi?id=135880&action=edit
marble-19.12.2-kde#432598.patch
The attached patch (against the old version of Marble I am still running, but
it
https://bugs.kde.org/show_bug.cgi?id=441131
--- Comment #1 from Kevin Kofler ---
Well, if the file does not exist in one of the folders, diff does the
comparison with /dev/null instead. Obviously, you cannot save to /dev/null.
--
You are receiving this mail because:
You are watching all bug
1 - 100 of 385 matches
Mail list logo
