[partitionmanager] [Bug 359819] Add support for more partition types
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: You are watching all bug changes.
[kio] [Bug 314451] sftp: Resuming partly transferred file >= 2 GiB is impossible - "unknown error code 166"
https://bugs.kde.org/show_bug.cgi?id=314451 Kevin Kofler changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Summary|sftp: Resuming partly |sftp: Resuming partly |transferred file is |transferred file >= 2 GiB |impossible - "unknown error |is impossible - "unknown |code 166" |error code 166" Ever confirmed|0 |1 CC||kevin.kof...@chello.at Status|NEEDSINFO |CONFIRMED --- Comment #8 from Kevin Kofler --- This still happens with current KDE 4 versions of kio_sftp. (The KF5 version may or may not be also affected.) At least, I had this moving files from a Fedora 21 source to a Fedora 24 destination with Krusader (kdelibs 4 version). The important part that is missing in the subject is that it only happens on files which do not fit in a 32-bit int. I never had this happen with any other file. I had it happen with a > 4 GiB file. The OP's was 3.6 GiB, so I guess the limit is probably the signed 32-bit int, so 2 GiB - 1 byte. The funny thing is that both source and destination machines are x86_64 and use 64-bit kio_sftp. So lack of large file support cannot be the issue. I guess the resume offset is stored in an int somehow. When moving the file from the source (local source, SFTP remote destination), I had exactly the behavior described here: the unknown numeric error code. I then tried to SFTP the remainder of the file the other way, running Krusader on the destination instead (SFTP remote source, local destination), and the result was even worse: It resumed, but the resume offset was truncated (as was visible immediately from the progress report)! As a result, it redownloaded parts that I already had in my .part file, corrupting the output file! So the whole hour I had spent transferring the first > 5 GiB until it broke down was wasted. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 367639] k3b fails to continue multisession (blue ray)
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 string "0", depending on what you actually meant. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] New: Please restore wodim support
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 Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: kevin.kof...@chello.at CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- In: https://quickgit.kde.org/?p=k3b.git&a=commitdiff&h=fcb0ff1f36c319fd1e2b4bd92c2c08fdc690212c you removed support for wodim. Please revert this commit. Fedora ships only cdrkit, not cdrtools, due to licensing issues: https://fedoraproject.org/wiki/Forbidden_items#cdrtools . If you need a distribution shipping wodim for testing, try Fedora. DVD support in wodim is crap and BluRay support is nonexistent, but that's why the code you removed, which prefers growisofs, is there! What will happen now that you removed the detection for wodim is that K3b will think that wodim is cdrecord (because it symlinks itself to cdrecord) and no longer disable use of wodim for things it does not support. Please do not remove code you don't understand. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
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::AbstractCdrtoolsProgram( QLatin1String( "cdrecord" ),
QLatin1String("cdrecord") )
(2 times the same command, probably not what you want)
-// but prefer growisofs to wodim for DVDs
+// but prefer growisofs for DVDs
if ( d->usedWritingApp == K3b::WritingAppAuto ) {
-if
(k3bcore->externalBinManager()->binObject("cdrecord")->hasFeature( "wodim" ))
-d->usedWritingApp = K3b::WritingAppGrowisofs;
-else
-d->usedWritingApp = K3b::WritingAppCdrecord;
+d->usedWritingApp = K3b::WritingAppCdrecord;
(The comment says "prefer growisofs", the code says "prefer cdrecord".)
but instead of fixing those errors, please revert this commit wholesale, or K3b
will have to be removed from Fedora.
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
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.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
https://bugs.kde.org/show_bug.cgi?id=137436
Kevin Kofler changed:
What|Removed |Added
CC||kevin.kof...@chello.at
--- Comment #15 from Kevin Kofler ---
Yes, in the long run, to work with something maintained, we will need K3b to
work well with http://libburnia-project.org/ . Cdrecord has licensing issues
preventing it from shipping in some distributions
(https://fedoraproject.org/wiki/Forbidden_items#cdrtools), cdrkit/wodim and
dvd+rw-tools/growisofs are both dead projects.
At the very least, its cdrskin tool should be supported similarly to wodim:
check for it (I would check for "cdrskin", "cdrecord" and "wodim" in that
order, or you end up picking up a "cdrecord" that is really wodim), then add
hasFeature("cdrskin") checks where useful, i.e., cdrskin is probably preferable
to growisofs for all burning tasks (both DVD and BluRay), and you need to check
its support for various features. The proposed patch from comment #1 is far
from sufficient. It only checks for the cdrskin binary (after wodim!), but it
treats it as if it were cdrecord, so you end up with all the workarounds for
cdrecord limitations.
But I think the best way would be to just use the libburn library and stop
spawning external tools entirely.
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
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 removed, you will notice that it took care to prefer growisofs over wodim for all DVD and BluRay burning tasks. (The only reason we need wodim at all is that growisofs does not support CDs.) In fact, ironically, your change actually made K3b attempt to use wodim for BluRay! (Then you added a followup to just unconditionally prefer growisofs: http://quickgit.kde.org/?p=k3b.git&a=commitdiff&h=f3f4602e30c67bf622b5a52ea39c78817b1dd020 , which I'm not sure is a good idea either. It is much better than wodim, but is it better than current versions of cdrecord? Probably not. You will need to revert that first so that you can revert fcb0ff1f.) -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
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), * xorriso (native CLI, also replaces mkisofs/genisoimage), * libburn (low-level, burning-only library), * libisoburn (higher-level library, can do everything xorriso can do, there is even an API (xorriso.h) that directly mimics the xorriso CLI). -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
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 for mkisofs, * to go with libburn (low-level library), there is a libisofs library. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
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 request to restore the code with a "NOPE!" in ALL CAPS is also not helpful. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
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: You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
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 packagers when announcing the new
release, so we do not end up with things working poorly because wodim is
getting silently picked up due to outdated dependencies in the package.
You should also make sure that cdrskin is preferred over wodim even if wodim is
installed/symlinked as "cdrecord" (because updating K3b, even if we add a
Requires: cdrskin, is not magically going to make installed wodim packages go
away, we cannot really use Obsoletes or Conflicts to force it removed).
> Yes, I am editing libk3b/core/k3bdefaultexternalprograms.cpp for adding
> cdrskin to K3b::AbstractCdrtoolsProgram( QLatin1String( "cdrskin" ),
> QLatin1String("cdrecord") )
But that is only the easy part. You need to look at all the places where a
decision what burning program to prefer is made (or checks for "if burning
program == cdrecord, apply workaround foo"), make it prefer cdrskin for things
it is actually better at (remember that growisofs is unmaintained too, though
not as long as wodim, so cdrskin is the better choice if it works), disable
cdrecord-specific workarounds (start by looking at those workarounds already
disabled for wodim in the code you removed, but keep in mind that cdrskin is
not a fork of cdrecord as wodim is, so probably does not need ANY of the
cdrecord workarounds), etc.
I have seen a bunch of cdrecord workarounds while browsing K3b code in the
past, but unfortunately I do not remember the exact locations in the code. For
example, there is something that says that cdrecord fails at doing some things
for audio CDs in DAO mode, so cdrdao (another unmaintained tool (no news since
2009), that in addition also uses libraries from cdrtools/cdrkit, so also uses
the unmaintained wodim code) is used for those instead. (Searching for "cdrdao"
will probably find that particular one.) You really want to go through all the
burning code and check whether what it is doing still makes sense if cdrecord
is actually cdrskin.
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
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 than genisoimage. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 372094] Please restore wodim support
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.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
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 because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
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-tools (growisofs): 2008-03-05 * cdrdao: 2009-10-05 -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 372391] f25 plasma "networks" and "instant messaging" icons are invisible.
https://bugs.kde.org/show_bug.cgi?id=372391 Kevin Kofler changed: What|Removed |Added URL||https://bugzilla.redhat.com ||/show_bug.cgi?id=1394449 --- Comment #1 from Kevin Kofler --- Note that the Fedora theme is basically just Breeze with a different default wallpaper. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372391] f25 plasma "networks" and "instant messaging" icons are invisible.
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|general |Theme - Breeze -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
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 that this write mode
> gets selected at all.
Or the code should in that case select a burning tool that can do that.
(cdrecord? wodim? cdrdao? Whatever supports it and is available on the user's
system.) If none is found, then graying it out in the UI is the best option.
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 422095] Bad printout quality of kmail
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. Falkon used to do that (I > had submitted that code back when the QtWebEngine did not have the print > method at all, only printToPdf), but switched to using the print method for > physical printers. What QtWebEngine cannot do is print directly to a QPrinter. The Chromium code can only output PDFs. Then you have to get that PDF to the printer somehow. How QtWebEngine does it is that it renders the PDF to a pixmap using the PDFium library that happens to be bundled with Chromium and then sends that pixmap to the printer. How Okular prints PDFs (and how Falkon used to do it at the beginning) is that it runs the lpr CLI command to send the PDF to the printer. The main difficulty with that is that you have to translate settings such as margins or page orientation or they will just get ignored, and that it also only works with printers that lpr knows about (e.g., you cannot print to PDF with that approach). -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 465675] kompare version 22.12.2
https://bugs.kde.org/show_bug.cgi?id=465675 Kevin Kofler changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Kevin Kofler --- .doc files are binary files and cannot be compared with Kompare. The error message is by design. .docx and .odt files are also binary files because they are compressed. You can try using a flat .odtf, which is uncompressed XML, but the diff between a text file and the ODT flat XML will also be mostly useless because all lines will be different. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415467] Can't circumvent Google's browser blocking with user agent manager
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 this mail because: You are watching all bug changes.
[Discover] [Bug 446924] Support distribution upgrades on Fedora
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. The distribution needs to support distribution upgrades in its PackageKit backend and in its AppStream metadata. Then it should just work in Discover, but also, e.g., in GNOME Software. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466248] Discover's Notifier Tray Icon does not show
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.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
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 mail because: You are watching all bug changes.
[plasmashell] [Bug 451217] "Open in terminal" menu item, like in Dolphin
https://bugs.kde.org/show_bug.cgi?id=451217 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #12 from Kevin Kofler --- For the record, the original author of the patch is Than Ngo: https://src.fedoraproject.org/rpms/kdebase-workspace/c/b5cfa5f91cd86113d415b3693154e728a8a99a94?branch=ae9448efad448b5721203c07651efabd659f8757 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
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 to ICU locales. So, for a custom glibc locale to work, Qt would need to be changed to use the POSIX APIs instead of ICU ones, and that would likely mean that POSIX, or at least glibc's implementation of it, would have to grow some additional locale APIs that Qt needs. (Last I checked, the maintainers of the Qt locale codes claimed that the POSIX/glibc locale APIs are not sufficient for their needs.) I still think that, as I had written in comment #6, KDE should just go back to using a KDE-specific locale and formatting implementation and bypassing the inferior Qt, POSIX, and ICU ones. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
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 principle. And it is a very bad concept, because not everyone in a, possibly large, country agrees on the correct format to use. Even in a small country like Austria, dates can be (and in practice are) formatted as 1.1.2022, 01.01.2022, 1.1.22, etc., currency amounts can be formatted as 12,34€, 12,34 €, €12,34, etc., some people might even want to use 12€34 to match the spoken version, though I do not remember having it ever seen spelled like that. I would expect even more variance in large countries such as the USA.) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
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 large enough tray to be readable. The tooltip uses a hardcoded date format that cannot be configured at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
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 are watching all bug changes.
[kompare] [Bug 468711] Unable to dock Navigation panel back into the main window again
https://bugs.kde.org/show_bug.cgi?id=468711 Kevin Kofler changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Kevin Kofler --- Sounds like an upstream Qt issue then. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 468711] Unable to dock Navigation panel back into the main window again
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.
[kig] [Bug 469962] Doesn't launch at all
https://bugs.kde.org/show_bug.cgi?id=469962 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #4 from Kevin Kofler --- We really need to stop abusing global write privileges to commit untested changes like this: https://invent.kde.org/education/kig/-/commit/c1f566d4790c33055fa42b60ae2b00728ba1a271 without even talking to the maintainer (or was the maintainer (here at KDE upstream) contacted this time? I know I never was when this kind of changes was committed to Kompare, which I maintain here), let alone testing that the application still runs after the change. These changes bring no user-visible improvements and can just break things. In this case, the breakage took 3 months (!) to get noticed and fixed, leading to two (supposedly) stable releases (23.04.0 and 23.04.1) shipping with a completely broken Kig. As the distribution packager for Kig at Fedora, I find this a completely unacceptable state of affairs. See: https://bugzilla.redhat.com/show_bug.cgi?id=2209374 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 467050] Crash after mail composition
https://bugs.kde.org/show_bug.cgi?id=467050 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #4 from Kevin Kofler --- I would be inclined to blame kf5-sonnet for this regression. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc freezes, both in Krusader and Dolphin
https://bugs.kde.org/show_bug.cgi?id=456348 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc freezes, both in Krusader and Dolphin
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/krusader -DCMAKE_C_FLAGS="-O2 > -fPIC" -DCMAKE_CXX_FLAGS="-O2 -fPIC" That is not an acceptable fix or even workaround. I cannot ship that in distribution packages, those MUST be installed to /usr. I suspect that something is invoking a wrong executable, from kdelibs 4 or even 3, see, e.g., bug #386859 for a similar issue. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc freezes, both in Krusader and Dolphin
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 this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc freezes, both in Krusader and Dolphin
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.
[krusader] [Bug 456348] KrArc freezes, both in Krusader and Dolphin
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 segfaulting:
[pid 45454] --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x8}
---
--
You are receiving this mail because:
You are watching all bug changes.
[krusader] [Bug 456348] KrArc segfaults the kioslave5 process, causing the client application's UI to hang, both in Krusader and Dolphin
https://bugs.kde.org/show_bug.cgi?id=456348 Kevin Kofler changed: What|Removed |Added Summary|KrArc freezes, both in |KrArc segfaults the |Krusader and Dolphin|kioslave5 process, causing ||the client application's UI ||to hang, both in Krusader ||and Dolphin -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc segfaults the kioslave5 process, causing the client application's UI to hang, both in Krusader and Dolphin
https://bugs.kde.org/show_bug.cgi?id=456348 Kevin Kofler changed: What|Removed |Added URL||https://bugzilla.redhat.com ||/show_bug.cgi?id=2114822 --- Comment #25 from Kevin Kofler --- This is a backtrace from ABRT: https://bugzilla.redhat.com/show_bug.cgi?id=2114822 > Thread no. 1 (8 frames) > #0 std::__atomic_base::load at > /usr/include/c++/12/bits/atomic_base.h:818 > #1 std::atomic::load at /usr/include/c++/12/atomic:579 > #2 QAtomicOps::loadRelaxed at > ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 > #3 QBasicAtomicPointer::loadRelaxed at > ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:248 > #4 QObject::thread at kernel/qobject.cpp:1487 > #5 KIO::SlaveBase::SlaveBase at > /usr/src/debug/kf5-kio-5.96.0-1.fc36.x86_64/src/core/slavebase.cpp:266 > #6 kio_krarcProtocol::kio_krarcProtocol at > /usr/src/debug/krusader-2.7.2-6.fc36.x86_64/krArc/krarc.cpp:144 > #7 kdemain at /usr/src/debug/krusader-2.7.2-6.fc36.x86_64/krArc/krarc.cpp:129 The reporter Wladimir Palant writes: > Judging from the backtrace, this is a regression from > https://invent.kde.org/frameworks/kio/-/commit/865d9b7a80a02979d46bf3dede2dc4d551d501ba > – the possibility that `qApp` might be null is not considered here. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc segfaults the kioslave5 process, causing the client application's UI to hang, both in Krusader and Dolphin
https://bugs.kde.org/show_bug.cgi?id=456348 Kevin Kofler changed: What|Removed |Added CC||fa...@kde.org --- Comment #26 from Kevin Kofler --- CCing the author of the pinpointed commit (David Faure). -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415467] Can't circumvent Google's browser blocking with user agent manager
https://bugs.kde.org/show_bug.cgi?id=415467 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #3 from Kevin Kofler --- Update: Firefox 57.0 is no longer accepted now, so I changed it to 105.0 and that works: Mozilla/5.0 (X11; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0 (for the domain accounts.google.com). (The Gecko/20100101 part is bogus, but they do not seem to check that.) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 415467] Can't circumvent Google's browser blocking with user agent manager
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 accepted by accounts.google.com. -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 460239] New: 3D graphs are not plotted on the PinePhone due to shader error
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
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: kevin.kof...@chello.at
Target Milestone: ---
SUMMARY
3D graph plots in KAlgebra Mobile are not rendered.
STEPS TO REPRODUCE
1. Install kalgebra on the PinePhone. I am using Manjaro ARM Plasma Mobile.
2. Run KAlgebra Mobile from the menu.
3. Go to Graph 3D.
4. Touch the circled + button to open the popup.
5. Touch the + button in the popup to add the example sin x*sin y plot. You can
also try any other function. It does not make a difference.
OBSERVED RESULT
The plot area remains completely black.
EXPECTED RESULT
The 3D graph is rendered.
SOFTWARE/OS VERSIONS
Manjaro ARM Plasma Mobile
Pine64 PinePhone (1.2) (Allwinner A64 / Cortex A53 aarch64)
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
kalgebra 22.08.1-1 (Manjaro ARM Package)
ADDITIONAL INFORMATION
This is the terminal output. I believe the first error to be the root cause and
the remaining ones to be followups that ultimately lead to nothing at all being
rendered:
QOpenGLShader::compile(Fragment): 0:4(2): error: No precision specified in this
scope for type `float'
*** Problematic Fragment shader source code ***
#ifdef GL_KHR_blend_equation_advanced
#extension GL_ARB_fragment_coord_conventions : enable
#extension GL_KHR_blend_equation_advanced : enable
#endif
#ifndef GL_FRAGMENT_PRECISION_HIGH
#define highp mediump
#endif
#line 1
uniform mediump vec4 color;
void main(void)
{
float w = 10.*gl_FragCoord.w;
highp vec4 zvec = vec4(w, w, w, 1.0); gl_FragColor = mix(color, zvec,
vec4(.5,.5,.5,1.));
}
***
QOpenGLShader::link: error: program lacks a fragment shader
QOpenGLShader::link: error: program lacks a fragment shader
QOpenGLShaderProgram::uniformLocation(matrix): shader program is not linked
QOpenGLShaderProgram::attributeLocation(vertex): shader program is not linked
QOpenGLShaderProgram::attributeLocation(normal): shader program is not linked
QOpenGLShaderProgram::attributeLocation(vertex): shader program is not linked
QOpenGLShaderProgram::uniformLocation(color): shader program is not linked
QOpenGLShaderProgram::uniformLocation(color): shader program is not linked
QOpenGLShaderProgram::uniformLocation(color): shader program is not linked
QOpenGLShaderProgram::attributeLocation(vertex): shader program is not linked
QOpenGLShaderProgram::uniformLocation(color): shader program is not linked
QOpenGLShader::link: error: program lacks a fragment shader
QOpenGLShaderProgram::uniformLocation(matrix): shader program is not linked
QOpenGLShaderProgram::attributeLocation(vertex): shader program is not linked
QOpenGLShaderProgram::attributeLocation(normal): shader program is not linked
QOpenGLShaderProgram::attributeLocation(vertex): shader program is not linked
QOpenGLShaderProgram::uniformLocation(color): shader program is not linked
QOpenGLShaderProgram::uniformLocation(color): shader program is not linked
QOpenGLShaderProgram::uniformLocation(color): shader program is not linked
QOpenGLShaderProgram::attributeLocation(vertex): shader program is not linked
QOpenGLShaderProgram::uniformLocation(color): shader program is not linked
--
You are receiving this mail because:
You are watching all bug changes.
[kalgebra] [Bug 460239] 3D graphs are not plotted on the PinePhone due to shader error
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.
[kalgebra] [Bug 460239] 3D graphs are not plotted on the PinePhone due to shader error
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.
[analitza] [Bug 460239] KAlgebra 3D graphs are not plotted on the PinePhone due to shader error
https://bugs.kde.org/show_bug.cgi?id=460239 Kevin Kofler changed: What|Removed |Added CC||percy.camilo...@gmail.com Version|22.08.1 |unspecified Summary|3D graphs are not plotted |KAlgebra 3D graphs are not |on the PinePhone due to |plotted on the PinePhone |shader error|due to shader error Product|kalgebra|analitza Component|general |analitzaplot -- You are receiving this mail because: You are watching all bug changes.
[analitza] [Bug 460239] KAlgebra 3D graphs are not plotted on the PinePhone due to shader error
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.
[analitza] [Bug 460239] KAlgebra 3D graphs are not plotted on the PinePhone due to shader error
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.
[analitza] [Bug 460239] KAlgebra 3D graphs are not plotted on the PinePhone due to shader error
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.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
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.
[Falkon] [Bug 433181] Add Gemini support
https://bugs.kde.org/show_bug.cgi?id=433181 Kevin Kofler changed: What|Removed |Added CC||jurajora...@mailo.com --- Comment #1 from Kevin Kofler --- One would just need to write a KIO worker (formerly known as kioslave) for Gemini like the existing kio_gopher for Gopher. (Yes, Gopher already works in Falkon if one has kio_gopher installed! I am surprised that Juraj appears not to be aware of that, at least judging from his mailing list reply. The only known issue is that the URLs do not end up in the browser history, see bug #406375, which sadly has not even been acknowledged by a maintainer for more than 4 years now. Support for Gemini could be implemented the same way, though I am not aware of any implementation at this time.) See https://userbase.kde.org/Kio_gopher and https://invent.kde.org/network/kio-gopher . -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 406375] Falkon KDE Frameworks Integration: KIO URLs are not saved in the browser history
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.
[Falkon] [Bug 406375] Falkon KDE Frameworks Integration: KIO URLs are not saved in the browser history
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.
[Falkon] [Bug 406375] Falkon KDE Frameworks Integration: KIO URLs are not saved in the browser history
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 requires a browser restart, but then it will be listed in allowedSchemes. So I have no remaining concern with the code, it should work as is. Thanks again for the fix! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 478121] New: Elisa mobile UI: playlist drawer cannot be closed anymore
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 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: kevin.kof...@chello.at Target Milestone: --- SUMMARY In Elisa 23.08.3, in the mobile/touch UI, if the playlist drawer is open, there is no way to close it. Dragging it to the screen edge with the finger no longer works, it does not move even by a single pixel. Touching outside of the playlist also does nothing. Touching the "Show playlist" button again is not possible because it is covered by the drawer (and even if it were not, I guess it would not respond anyway). Hitting the X button on the bottom closes the entire application (which appears to be the only way to get rid of the playlist drawer). STEPS TO REPRODUCE 1. Install Elisa on Plasma Mobile. (I use the Manjaro ARM elisa-qtmm package, but I doubt it depends on the multimedia backend.) 2. Open Elisa. 3. Touch (click) the "Show playlist" button. 4. Try to close the playlist drawer in various ways. OBSERVED RESULT The playlist drawer does not budge. EXPECTED RESULT The playlist drawer can be closed. SOFTWARE/OS VERSIONS Hardware: PINE64 PinePhone (original Allwinner A64 model, Beta Edition with Convergence Package (dock not plugged in)) Linux/KDE Plasma: Manjaro ARM (Plasma Mobile Edition, aarch64) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Elisa Version: elisa-qtmm 23.08.3-1 ADDITIONAL INFORMATION This is a regression compared to at least 22.12.3. (Since intermediate versions were not packaged as elisa-qtmm, I cannot tell the exact version where the regression happened.) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 478121] Elisa mobile UI: playlist drawer cannot be closed anymore
https://bugs.kde.org/show_bug.cgi?id=478121 Kevin Kofler changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Kevin Kofler --- I suspect that the regression is caused by this commit: https://invent.kde.org/multimedia/elisa/-/commit/6df31bbb78145633a187c56aa25389fee7e45a10 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 478121] Elisa mobile UI: playlist drawer cannot be closed anymore
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.
[Elisa] [Bug 478121] Elisa mobile UI: playlist drawer cannot be closed anymore
https://bugs.kde.org/show_bug.cgi?id=478121 Kevin Kofler changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/mult ||imedia/elisa/-/commit/2d734 ||16c9382b5b6a3535612719ff2c9 ||4dc0246a --- Comment #5 from Kevin Kofler --- Git commit 2d73416c9382b5b6a3535612719ff2c94dc0246a by Kevin Kofler. Committed on 10/12/2023 at 06:36. Pushed by kkofler into branch 'release/23.08'. Make context drawer interactive on mobile (#478121) src/qml/ElisaMainWindow.qml (contextDrawer): Change interactive: false to interactive: Kirigami.Settings.isMobile. Otherwise, it is impossible to close the context (playlist) drawer (with touch only) on mobile platforms such as the PinePhone. Update the comment accordingly. M +4-3src/qml/ElisaMainWindow.qml https://invent.kde.org/multimedia/elisa/-/commit/2d73416c9382b5b6a3535612719ff2c94dc0246a -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 478121] Elisa mobile UI: playlist drawer cannot be closed anymore
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 |imedia/elisa/-/commit/2d734 |imedia/elisa/-/commit/b8df2 |16c9382b5b6a3535612719ff2c9 |8c83f3561e213a006b3c7697174 |4dc0246a|9506be72 --- Comment #6 from Kevin Kofler --- Git commit b8df28c83f3561e213a006b3c76971749506be72 by Kevin Kofler. Committed on 10/12/2023 at 06:45. Pushed by kkofler into branch 'master'. Make context drawer interactive on mobile (#478121) src/qml/ElisaMainWindow.qml (contextDrawer): Change interactive: false to interactive: Kirigami.Settings.isMobile. Otherwise, it is impossible to close the context (playlist) drawer (with touch only) on mobile platforms such as the PinePhone. Update the comment accordingly. M +4-3src/qml/ElisaMainWindow.qml https://invent.kde.org/multimedia/elisa/-/commit/b8df28c83f3561e213a006b3c76971749506be72 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] New: CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
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 URL: https://bugzilla.redhat.com/show_bug.cgi?id=2290894 OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Session Management Assignee: plasma-b...@kde.org Reporter: kevin.kof...@chello.at CC: natalie_clar...@yahoo.de Target Milestone: 1.0 SUMMARY The GUI buttons to shutdown or restart do not work on X11 under plasma-workspace 6.0.5.1. They work under 6.0.5. STEPS TO REPRODUCE 1. Start the "Plasma (X11)" session. 2. Try to shutdown or restart from the UI. OBSERVED RESULT The buttons do not work. EXPECTED RESULT The buttons work. SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.5 with plasma-workspace 6.0.5.1 (plasma-workspace 6.0.5 works!) ADDITIONAL INFORMATION See https://bugzilla.redhat.com/show_bug.cgi?id=2290894 for details. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
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 not fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
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 watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
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.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
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/?23a726b30013e7aa#5ZX2ivqqZCnpwnAu13bSxz4aeaqXMRDsw6hjZnCkowCo "dolphin" didn't output anything except if I walked through some folders. That's why there is some spam in the output. The file "/run/user/1000/iceauth_MfWxAr" points to the tmp folder as you can see in the output. "MIT-MAGIC-COOKIE 1" appears inside it many times. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
https://bugs.kde.org/show_bug.cgi?id=488187 Kevin Kofler changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
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 used to do that. I have not been involved with those settings for a while, so I would have to double-check. (To be honest, I have always complained that we still print way too many debugging messages to the terminal and would have restricted the logging even further if it had been my decision to make, silencing anything except qFatal.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
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 qWarning: https://code.qt.io/cgit/qt/qtbase.git/tree/src/plugins/platforms/xcb/qxcbsessionmanager.cpp?h=6.7.2#n343 so it should be shown by default. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
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.
[plasmashell] [Bug 488187] CVE-2024-36041 patches in 6.0.5.1 break shutdown/restart on X11
https://bugs.kde.org/show_bug.cgi?id=488187 Kevin Kofler changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #15 from Kevin Kofler --- We now have at least 3 users who can reproduce this downstream. This is not a configuration issue on an individual machine. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
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 settings be per country (or per language/country pair for those countries speaking more than one language) just cannot cover it. And many users prefer having their system in English (or some other foreign language), but still expect date formats etc. to follow the rules of their country (but not using its language for weekdays, month names, etc.), which is not covered by the locale system either. So the status quo is frequently not just not according to the user preferences, but genuinely wrong. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 340982] No way to change just the date format but not its actual translated text
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 in everything except Qt applications and en_SE working only in Qt applications, making those popular workarounds for more international-friendly English locales useless. And for the same reason, a custom glibc locale will also not work in Qt applications. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 481584] New: Allow stretched scaling (horizontal ratio ≠ vertical ratio) on Wayland
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 OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kevin.kof...@chello.at Target Milestone: --- Under X11, I can scale outputs (at X11 level) ignoring the aspect ratio. This is essential to unify outputs with different aspect ratios, for presentations and meetings. E.g., my notebook has a 1280×800 (8:5/16:10) display. Using xrandr --scale-from, I can stretch this to 16:9, or even to 1024×768 4:3 which is then stretched to 16:9 by the TV. So I see the same thing on the notebook's built-in screen and on the TV, slightly distorted, but workable. (Yes, it is blurry and/or some pixels are lost. But it does not look that bad in practice.) Today, I tried to do this trick with my PinePhone (using the convergence dock and HDMI output). Plasma Mobile forces Wayland on me. So I look at the options of kscreen-doctor, which is purportedly the replacement of xrandr, and well, that can only apply one scale factor, not different ones for horizontal and vertical. So I cannot get truly unified outputs. Instead, one or the other display ends up truncated and impossible to work with. (Also because, on mirrored configurations, Plasma insists on filling the larger display and truncating the smaller one instead of filling the smaller one and letterboxing the larger one as it should, independently of which of the displays I set to be primary.) Ever since the introduction of the XRandR X11 extension, the one way to get my use case working has always been to talk to XRandR directly over the CLI and bypass Plasma entirely. Even fractional scaling on X11 is a non-issue if you just let X11 do the scaling, so that neither Plasma nor the applications even realize that their display is being scaled, let alone that it is being fractionally scaled with a different fraction horizontally and vertically. They just see a framebuffer of the size they want, and everything is scaled by X11/XRandR behind their back. So it just works (with the aforementioned blurriness / lost pixels, true). Unfortunately, this is not an option in Wayland because there is no X server that can do the scaling behind Plasma's back under Wayland. So for Wayland, I need KScreen to handle that stretching mode. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 484997] Kdiff3 and Kompare can't see the home folder or media folder
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.
[kompare] [Bug 484736] why is kompare still in qt5
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/2422cb5c16ad7091dc93a8cfb7c6deabe110b8af because that library is also used in KDevelop, which is not yet ready for KF6. It should theoretically be possible to build either master with the above libkomparediff2 commit reverted or the dedicated kf6 branches against KF6, but you will be building libkomparediff2 with a non-finalized API that is still subject to change (master has the same API as the KF5 version even if you build it against KF6, the kf6 branch has some API changes, but it might be getting some more for KDevelop), and you also need a separate KF5 build of libkomparediff2 for KDevelop. Those are probably the reasons why your downstream distribution is still building Kompare against KF5. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 480069] Add syntax highlighting
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 (e.g., many KatePart syntax highlighting definitions use green and red text for some syntax), what to do if the highlighting definition specifies a background color (which it can do, e.g., several use red background for what they think are syntax errors), etc. But those can be sorted out if and when someone actually has the time to do the work. I do not. -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 486463] Opening a link in a new tab automatically and unexpectedly switches you to that tab and show a popup largely blocking the tab switcher button to switch back
https://bugs.kde.org/show_bug.cgi?id=486463 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #7 from Kevin Kofler --- > Default to not switching to new tabs I am not convinced just changing the default for this flag is the proper fix for the issue, unless its behavior has changed since last time I tried it. I have found this behavior of links opening in new tabs activating that tab annoying as well, so I tried to run with "switchToNewTab=false" for a while. I have given up on it because I actually found it MORE annoying. The issue is that this also applies not only to tabs opened from links, but also to tabs that I open explicitly from the Angelfish menus. And those tabs, I most definitely DO want to switch to, because that is what I opened them for. So with "switchToNewTab=false", I have to then do 2 extra touches to actually switch to the tab I just opened before entering the URL in it. So what I would like to see as the default, or at least as an option, is a mode where switching to new tabs is disabled for tabs opened from links (either because the website says so or because I picked "Open in new tab"), but enabled for tabs opened explicitly through the "new tab" button in the Angelfish UI. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcontacts] [Bug 446665] New: Cannot set Addressee birthday from QML (e.g., from plasma-phonebook)
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://invent.kde.org/plasma-mobile/plasma-phonebook/
-/issues/6
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: kevin.kof...@chello.at
Target Milestone: ---
As can be seen in:
https://invent.kde.org/frameworks/kcontacts/-/blob/c0bd98e873075d57eed2555f9f4126ba660dc59a/src/addressee.h#L85
the birthday property in Addressee is not writable, and neither is there a
scriptable explicit setter.
This is the root cause of this plasma-phonebook regression:
https://invent.kde.org/plasma-mobile/plasma-phonebook/-/issues/6#note_307938
As the comment in addressee.h says, the issue that makes this not
straightforward is the withTime argument. I think the best that can be done is
something like:
Q_PROPERTY(QDateTime birthday READ birthday WRITE setBirthdayProperty)
void setBirthdayProperty(const QDateTime &birthday) {
setBirthday(birthday, birthday.time().msecsSinceStartOfDay() != 0);
}
(which will treat an explicit time of midnight the same as no time, but at
least it should do the right thing in the context of the Phonebook application
where we do not allow setting a time to begin with, and even with a time, it
will do the right thing in most cases).
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
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 linked https://gitlab.gnome.org/GNOME/gtk/-/issues/3737#note_1385359 . So, is there more that I can do to help getting this fixed?) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcontacts] [Bug 446665] Cannot set Addressee birthday from QML (e.g., from plasma-phonebook)
https://bugs.kde.org/show_bug.cgi?id=446665 Kevin Kofler changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kcontacts/commit/8b4 ||ba9c0ed465ded679e626071feeb ||e8aabe481c Status|ASSIGNED|RESOLVED --- Comment #5 from Kevin Kofler --- Git commit 8b4ba9c0ed465ded679e626071feebe8aabe481c by Kevin Kofler. Committed on 30/03/2022 at 23:03. Pushed by kkofler into branch 'master'. Addressee: make birthday writable from QML Add a private Addressee::setBirthdayProperty(const QDateTime &) wrapper method that guesses the extra withTime argument and use that as the WRITE method for the Q_PROPERTY birthday. A non-midnight time spec will lead to the birthday being recorded with the time, a time spec exactly at midnight to a date-only birthday (the common case). This is the best we can do for a property setter. This should make setting the birthday in Plasma Phonebook work again. (It last worked when Plasma Phonebook had its own QML wrapper for the Addressee class, which has been dropped since.) See also: https://invent.kde.org/plasma-mobile/plasma-phonebook/-/issues/6#note_307938 M +5-0src/addressee.cpp M +2-1src/addressee.h https://invent.kde.org/frameworks/kcontacts/commit/8b4ba9c0ed465ded679e626071feebe8aabe481c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447819] Plasma mobile: do not show SSD title bar for GTK apps
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.
[kwin] [Bug 452967] New: kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
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: https://gitlab.gnome.org/GNOME/gtk/-/issues/3737 OS: Linux Status: REPORTED Severity: major Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: kevin.kof...@chello.at Target Milestone: --- SUMMARY On Plasma Mobile (which uses kwin_wayland), popup menus in any GTK application do not respond to touch input. Touching any menu entry or any other control in the GTK popover just closes the popup without taking any action. The same effect can be seen for Chromium popups, including ones from QtWebEngine (though Angelfish ≥ 21.12 has a workaround using QML popups instead, so you will not be able to reproduce the issue with recent versions of Angelfish). This happens only for touch input using Wayland. Plugging in a USB mouse into the PinePhone and clicking with it works. Forcing the application to use X11 (using GDK_BACKEND=x11 for GTK apps or QT_QPA_PLATFORM=xcb for QtWebEngine apps) also works (sorta, because that causes several other issues such as no virtual keyboard coming up). This issue makes most GTK applications unusable on Plasma Mobile (e.g., Password Safe cannot be used because you cannot add a new password entry without going through a popup), and reduces the functionality of most of the remaining ones (e.g., in Geary, you cannot autocomplete addresses, switch between plain text and rich text (HTML) composing, etc.), so IMHO it should be treated as a showstopper. According to GTK developer Carlos Garnacho, the issue is that the GTK popover/popup menu is a subsurface, and kwin_wayland is incorrectly sending the touch event to the main surface instead. STEPS TO REPRODUCE As stated above, make sure you are using: 1. Wayland, both in KWin AND in the application (the bug canNOT be reproduced with X11), AND 2. touch (finger) input (the bug canNOT be reproduced with a mouse). A good device to try it on is a PinePhone running the default Manjaro ARM Plasma Mobile edition. Once that is set, there are several ways to reproduce the bug, e.g.: * In Geary, I "click" (touch) Inbox, then the "new message" button, then the "⋮" menu button. The popup menu that results does not work. * Also in Geary, the autocompletion popup in the "To" field (when I start typing a known address) does not work. * Password Safe is not usable because the "Add" popup does not work. (I do not remember the exact way to get to it because I uninstalled the application due to being unable to use it because of this bug.) * To see that this also happens with Chromium/QtWebEngine popups, fire up Angelfish < 21.12, or presumably another QtWebEngine browser that does not have Angelfish's workaround, and try opening https://www.falter.at/lokalfuehrer and using the search filters there (the popups like "ALLE BUNDESLÄNDER"). OBSERVED RESULT The popup closes without any action being taken. EXPECTED RESULT The click on the popup is processed. SOFTWARE/OS VERSIONS Manjaro ARM PinePhone Plasma Mobile Edition Last tested with: KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 with KDE backports ADDITIONAL INFORMATION This longstanding issue was initially reported at: https://invent.kde.org/plasma/plasma-mobile/-/issues/65 There, it was claimed to be a GTK issue, so: https://gitlab.gnome.org/GNOME/gtk/-/issues/3737 was filed. Then nothing had happened for months. From a log file I uploaded, GTK developer Carlos Garnacho was able to locate the issue in KWin: https://gitlab.gnome.org/GNOME/gtk/-/issues/3737#note_1385359 and Vlad Zahorodnii intended to investigate further, but nothing has now happened for 2 months. So I am filing this here now, in the hope that it will finally get the attention of somebody who is able to fix it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
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 session (pick "Plasma (X11)" instead of "Plasma (Wayland)" in SDDM) to work around this issue. (I am running Plasma Desktop on X11 on Fedora all the time.) That is not really an option on Plasma Mobile. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 446956] Webcams appear in scanner list
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 this mail because: You are watching all bug changes.
[kompare] [Bug 449796] Allow paste text from copy-clipboard in Kompare diff viewer.
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.
[kompare] [Bug 441131] Saving Fails with missing destination
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 changes.
[Falkon] [Bug 449735] Printable and shareable and readable RSS feeds
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.
[Discover] [Bug 436277] Allow skip checking for updates when using metered network connection
https://bugs.kde.org/show_bug.cgi?id=436277 Kevin Kofler changed: What|Removed |Added CC||kevin.kof...@chello.at --- Comment #7 from Kevin Kofler --- Why is this still open? This issue costs your users real money! E.g., while I normally have mobile data disabled on my PinePhone, today, I had to enable it, and while my actual usage only cost me 2 or 3 eurocents, I had to reboot the PinePhone twice because of crashes, which each time triggered Discover, resulting in twice 18 eurocents (so a total of 0,36€) wasted by Discover for no reason in only a few minutes. There is already the isConnectionAdequate() check in Discover for unattended updates. The same check should be used to decide whether to automatically check for updates. By default, since users can still check for updates manually if they need it. If you insist on making it an option, it should be opt-in. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436277] Allow skip checking for updates when using metered network connection
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!). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436277] Allow skip checking for updates when using metered network connection
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 before the reboot: 0.170 MB up, 2.368 MB down → 0.023€, * in the 4 minutes between the two reboots: 0.329 MB up, 19.625 MB down → 0.180€, * in the <10 minutes after the second reboot: 0.299 MB up, 19.579 MB down → 0.179€, and I would not know what else downloads so much at startup time other than Discover. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436277] Allow skip checking for updates when using metered network connection
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-org.kde.discover.notifier@autostart.service should "fix" the issue through the sledgehammer method, and I have done that on my PinePhone, though I am not in a mood right now to try reenabling mobile data to confirm (and if not, wasting at least 0,18€ again). In any case, it definitely does stop the notifier from autostarting (but you need to actually mask it with the second command, just disabling it through the first command does not work). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
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.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
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 changes.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
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 |ma/kwin/commit/94ee33e9be13 |ma/kwin/commit/dccb6f6472ce |2175587a65d02934ed1bbfc9601 |9dcad259f0b3852896792dfb73b |5 |2 --- Comment #10 from Kevin Kofler --- Git commit dccb6f6472ce9dcad259f0b3852896792dfb73b2 by Kevin Kofler, on behalf of Aleix Pol. Committed on 04/08/2022 at 21:41. Pushed by kkofler into branch 'Plasma/5.25'. wayland: Fix touch event delivery to subsurfaces Use SurfaceInterface::inputSurfaceAt when deciding which surface are we entering when sending a pointer event from a touch, in case it falls onto a subsurface. M +18 -7src/wayland/seat_interface.cpp M +4-7src/wayland/touch_interface.cpp M +1-2src/wayland/touch_interface.h https://invent.kde.org/plasma/kwin/commit/dccb6f6472ce9dcad259f0b3852896792dfb73b2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452967] kwin_wayland: touch input does not reach GTK or Chromium popup menus (subsurfaces)
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: You are watching all bug changes.
[marble] [Bug 432598] New: Marble uses ws.geonames.org, which is gone, should use api.geonames.org
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: https://www.geonames.org/export/ws-overview.html OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: kevin.kof...@chello.at Target Milestone: --- SUMMARY The geonames-based Marble plugins, such as the Wikipedia one, use the ws.geonames.org server. But that domain appears to be gone. As a result, the services do not work. STEPS TO REPRODUCE 1. Start Marble. 2. Enable the Wikipedia service. OBSERVED RESULT Nothing happens. EXPECTED RESULT Wikipedia buttons start showing up. SOFTWARE/OS VERSIONS I use Fedora 32, but it should not matter. All branches of Marble use the same obsolete URL. ADDITIONAL INFORMATION According to: https://www.geonames.org/export/ws-overview.html the services use api.geonames.org now. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 432598] Marble uses ws.geonames.org, which is gone, should use api.geonames.org
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 should apply to the current master) fixes the issue for me. Are you OK with me committing (and pushing) this patch? -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 441131] Saving Fails with missing destination
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 changes.
