https://bugs.kde.org/show_bug.cgi?id=469182
--- Comment #2 from Rinigus ---
plasma-integration is used to make sure that icons are colored correctly.
That's until we write SFOS specific platformtheme - I haven't written that yet.
However, this bug would affect any Linux distribution without X11
https://bugs.kde.org/show_bug.cgi?id=469182
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: rinigus@gmail.com
Target Milestone: ---
SUMMARY
On Sailfish OS, we use Wayland only and there are no X11
https://bugs.kde.org/show_bug.cgi?id=469092
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=469181
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: va...@kde.org
Reporter: rinigus@gmail.com
CC: kdelibs-b...@kde.org
Target Milestone: ---
SUMMARY
On Sailfish OS, we use Wayland only
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: ecm-bugs-n...@kde.org
Reporter: rinigus@gmail.com
Target Milestone: ---
SUMMARY
On platform without X11, find_package(EGL) fails as it tries to compile code
https://bugs.kde.org/show_bug.cgi?id=468662
Rinigus changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=468662
--- Comment #2 from Rinigus ---
Yes, that works nicely! Runtime dependency can be ignored if the device has
some other style. Thank you very much!
--
You are receiving this mail because:
You are watching all bug changes.
: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: j...@kaidan.im
Reporter: rinigus@gmail.com
Target Milestone: ---
On mobile platforms, it doesn't make sense to have QQC2DesktopStyle. Please
make this requirement optional
https://bugs.kde.org/show_bug.cgi?id=458099
--- Comment #5 from Rinigus ---
Making `flickable` property as "read-only" in 5.97 caused the same issue in
Pure Maps and OSM Scout Server. Before, if I understood it correctly, it was
recommended to set that property to your flick
https://bugs.kde.org/show_bug.cgi?id=458097
--- Comment #4 from Rinigus ---
OK, fair enough. I was not aware (or didn't recall to be more precise) of it.
Thanks for looking into it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455789
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=458131
Rinigus changed:
What|Removed |Added
Version|5.96.0 |5.97.0
--
You are receiving this mail because:
You
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: rinigus@gmail.com
CC: notm...@gmail.com
Target Milestone: Not decided
Created attachment 151471
--> https://bugs.kde.org/attachment.cgi?id=151
https://bugs.kde.org/show_bug.cgi?id=458099
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--- Comment #1 from Rinigus
https://bugs.kde.org/show_bug.cgi?id=458097
--- Comment #1 from Rinigus ---
Looks like running with
QT_QUICK_CONTROLS_MOBILE=true QT_QUICK_CONTROLS_STYLE=Plasma flatpak run
org.kde.kirigami2.gallery
makes scroll bar selectable by mouse. But it is still impossible to flick.
--
You
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: rinigus@gmail.com
CC: notm...@gmail.com
Target Milestone: Not decided
SUMMARY
***
On mobile environment, I cannot scroll items in GlobalDrawer
https://bugs.kde.org/show_bug.cgi?id=435066
--- Comment #6 from Rinigus ---
Yes, I can do that. But in this case I will have to figure out the correct
width of that widener element. Something which is not super trivial as you have
to take into account all labels (on the left) and spacing between
https://bugs.kde.org/show_bug.cgi?id=435066
--- Comment #4 from Rinigus ---
I want to have forms as in "Preferences" in Pure Maps and OSM Scout Server. In
these forms, I would like to show
Tag | setting widget
description text
That should fill the width of the page to make it
https://bugs.kde.org/show_bug.cgi?id=435066
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=435066
--- Comment #2 from Rinigus ---
OK, so, already by design it does not allow to make a form that would fill the
available width if the child elements signal that they wish to do so. Right?
Any way to regulate the amount of area that is used in practice
: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
Target Milestone: Not decided
SUMMARY
It seems to be impossible to make Kirigami.FormLayout to fill the full width of
the page. In practice, in wide mode
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
Target Milestone: Not decided
SUMMARY
SwipeListItem currently allows to swipe the item into the actions exposing mode
and then proceed to interact with the rest
https://bugs.kde.org/show_bug.cgi?id=423239
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=422461
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
Target Milestone: Not decided
SUMMARY
Kirigami.FormData.buddyFor could be used to align label with an element in the
form. Not sure when it changed
https://bugs.kde.org/show_bug.cgi?id=420350
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
Target Milestone: Not decided
SUMMARY
To introduce and process pressAndHold signal in context drawer, it was
suggested to use displayComponent
https://bugs.kde.org/show_bug.cgi?id=420349
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
Target Milestone: Not decided
SUMMARY
When clicking on action in ContextDrawer, it is no highlighted
https://bugs.kde.org/show_bug.cgi?id=418030
--- Comment #3 from Rinigus ---
Maybe it will be better. Then the apps wishing to use it would just have to
inherit it from the base app, right?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=418030
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=418030
Rinigus changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417035
--- Comment #7 from Rinigus ---
Thank you, looks like KDE 5.14 Platform has been updated at Flathub! Submitting
Maliit extension for review over there and we should get it sorted soon.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=417035
--- Comment #6 from Rinigus ---
Thank you very much!
But those updated runtimes are not promoted to the distributed ones
immediately, right? At least "flatpak update" doesn't find 5.12 (from last
night) yet. Same goes for 5.14
--
You are
https://bugs.kde.org/show_bug.cgi?id=417035
--- Comment #4 from Rinigus ---
Thank you very much! I just submitted the same patch for 5.14 runtime as well,
please merge that too.
Do you know when could we expect it to be published/usable as a new version of
the runtime?
--
You are receiving
Severity: normal
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: rinigus@gmail.com
Target Milestone: ---
SUMMARY
When compared to 5.12, 5.14 with WebEngine BaseApp is able to playback less web
-provided videos than
https://bugs.kde.org/show_bug.cgi?id=417035
--- Comment #2 from Rinigus ---
Corresponding merge request has been submitted about a week ago at
https://invent.kde.org/kde/flatpak-kde-runtime/merge_requests/8
Its more general and allows to add PlatformInputContexts extensions.
Please review
https://bugs.kde.org/show_bug.cgi?id=417055
Rinigus changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #11 from Rinigus ---
Thanks! I presume that variable is acquired from underlying video card. Do you
know how that's done?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #9 from Rinigus ---
QSG_RENDER_LOOP=basic has been tested and improved the performance. Sorry, that
we did a while ago while discussing at Plasma Mobile IRC. Question is where its
set in Qt or GL, so I could start digging into why its wrong
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #6 from Rinigus ---
Its ARM device, no nvidia here. As its using libhybris (originally Android
phone), no surprise if something is off on GL level. So, vsync suspicion makes
sense. Any tips on how I can check whether vsync works properly
https://bugs.kde.org/show_bug.cgi?id=417055
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=417035
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
Priority: NOR
Component: components
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
Observed in Angelfish, but probably similar in other places. Using style Plasma
and having
https://bugs.kde.org/show_bug.cgi?id=417035
--- Comment #1 from Rinigus ---
Notice that I have not suggested any extension name. As I am new to Flatpaks, I
guess you would have a better idea regarding it. In general it is a bit
Sailfish specific, but we can use similar approach for other mobile
Severity: normal
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: rinigus@gmail.com
Target Milestone: ---
With this issue, I am asking you to add a keyboard extension for use with KDE
Flatpak runtime on Sailfish OS. Sailfish
https://bugs.kde.org/show_bug.cgi?id=416262
--- Comment #10 from Rinigus ---
Re disabling statx:
I am arguing that the patch which you use to disable statx is not working. As
such, you have statx enabled right now.
If you try to build KDE runtime for arm using QEMU, it will fail quite early
https://bugs.kde.org/show_bug.cgi?id=416262
Rinigus changed:
What|Removed |Added
Resolution|NOT A BUG |---
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=416262
--- Comment #7 from Rinigus ---
I think I have been hitting some issue with statx system call which is
triggered in QEMU or ARM32. Haven't looked deeper, but look to be related:
https://bugreports.qt.io/browse/QTBUG-64490
https://bugreports.qt.io
https://bugs.kde.org/show_bug.cgi?id=416262
--- Comment #5 from Rinigus ---
Feel free to close as it looks to be an issue with my emulation environment.
When running on native platform, all works as expected. I will have to figure
out meanwhile what's wrong in my setup, but that's not related
https://bugs.kde.org/show_bug.cgi?id=416262
--- Comment #4 from Rinigus ---
It maybe some issue with my local setup. On Flathub servers, all is working as
expected. I keep the issue open for now, will try to figure out what's going
on.
If someone can test cross-building of ARM package
https://bugs.kde.org/show_bug.cgi?id=416262
--- Comment #3 from Rinigus ---
I will look into it and will report back
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=416262
--- Comment #1 from Rinigus ---
Same issue is observed for KDE 5.13
--
You are receiving this mail because:
You are watching all bug changes.
Severity: normal
Priority: NOR
Component: general
Assignee: aleix...@kde.org
Reporter: rinigus@gmail.com
Target Milestone: ---
Created attachment 125125
--> https://bugs.kde.org/attachment.cgi?id=125125=edit
Example JSON taken from a part of Pure M
https://bugs.kde.org/show_bug.cgi?id=416262
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=405522
--- Comment #1 from Rinigus ---
>From discussions on Kirigami IRC, it seemed that the issue is probably in
KIconLoader. In particular, it seems that KIconLoader ignores fallback path set
by QIcon::setFallbackSearchPaths call.
In my applicat
https://bugs.kde.org/show_bug.cgi?id=405522
Rinigus changed:
What|Removed |Added
CC||kdelibs-b...@kde.org
Component|general
https://bugs.kde.org/show_bug.cgi?id=405522
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
CC: k...@davidedmundson.co.uk
Target Milestone: ---
SUMMARY
When
https://bugs.kde.org/show_bug.cgi?id=403845
--- Comment #2 from Rinigus ---
I have just updated the platform and now all works for me. Not sure what was
changed, but this bug is not there anymore. I suggest to close it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=403845
--- Comment #1 from Rinigus ---
When testing against Qt 5.12 compiled on desktop, without flatpak layer, all
works as expected. Here, I compiled Qt 5.12 from the source, installed all
dependencies and run the application using Qt 5.12 libraries.
So
https://bugs.kde.org/show_bug.cgi?id=404488
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=404488
--- Comment #1 from Rinigus ---
Sorry, pushed a wrong button. As for steps to reproduce, just hide a handle and
observe the issue after pushing two pages into the stack (one main page + 1
pushed to get navigation arrows).
Using current Master
: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
Target Milestone: Not decided
Created attachment 118156
--> https://bugs.kde.org/attachment.cgi
: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
Target Milestone: Not decided
SUMMARY
When declaring that a specific page should have no toolbar, toolbar is still
shown when using
https://bugs.kde.org/show_bug.cgi?id=404481
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=403845
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jgrul...@redhat.com
Reporter: rinigus@gmail.com
Target Milestone: ---
SUMMARY
I am developing an application that is using QML Audio for playing
Severity: normal
Priority: NOR
Component: general
Assignee: notm...@gmail.com
Reporter: rinigus@gmail.com
Target Milestone: Not decided
While API for PageRow pop funciton states that popped page is returned, that
seems to be not the case.
--
You
https://bugs.kde.org/show_bug.cgi?id=403437
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving
72 matches
Mail list logo
