Re: Qt6 Location for Debian 12

2023-10-11 Thread Petric Frank
Hello,

Am Mittwoch, 11. Oktober 2023, 19:00:19 CEST schrieb Patrick Franz:
> Hej,
>
> Am Mittwoch, 11. Oktober 2023, 16:52:24 CEST schrieb Petric Frank:
> > Hello,
> >
> > is there a *.deb for Qt6 Location (-dev) module ?
> >
> > I have seen there is one for Qt6 Positioning in the stable repository
> > but i miss the above one.
> >
> > Or do i have to compile the Qt6 system myself ?
>
> There is no Location module for Qt 6.4. It never existed. However, it
> got reintroduced as a tech preview for 6.5.

I got a hint on a git project where Qt6Location was compiled for older Qt
Versions (< 6.5):
  https://github.com/ntadej/qtlocation

Maybe the 6.4.2 release of it could be a candidate for being repackaged as
*.deb ?

He made also a Qt Location plugin for maplibre-native-qt (open source fork/
rewrite of mapbox gl). It can be used accessing a versatiles mapping server.





Qt6 Location for Debian 12

2023-10-11 Thread Petric Frank
Hello,

is there a *.deb for Qt6 Location (-dev) module ?

I have seen there is one for Qt6 Positioning in the stable repository but i
miss the above one.

Or do i have to compile the Qt6 system myself ?

kind regards
  Petric





Re: auto add usb network to bridge

2023-09-25 Thread Petric Frank
Hello Reco,

the "allow-hotplug ..." and "up /sbin/ip ..." what what i was missing. Works
like a charm.

Thanks for your and others support.

regards
  Petric

Am Montag, 25. September 2023, 11:50:32 CEST schrieb Reco:
>   Hi.
>
> On Mon, Sep 25, 2023 at 11:35:50AM +0200, Petric Frank wrote:
> > My /etc/network/interfaces reads like this:
> > -- cut 
> > auto lo
> > iface lo inet loopback
> >
> > # onloard device
> > iface ens18 inet manual
> >
> > # usb device (not always there)
> > iface enx0 inet manual
> >
> > auto br0
> > iface br0 inet static
> >
> >   address 10.10.10.1/24
> >   bridge-ports ens18 enx0
> >   bridge-stp off
> >   bridge-fd 0
> >
> > -- cut 
> >
> > This works as long the usb device is plugged in at boot time.
> >
> > Connecting it later the usb network device appears but will not be
> > attached to  the bridge.
> You have to do it differently, like this:
>
> auto lo
> iface lo inet loopback
>
> # onloard device
> iface ens18 inet manual
>
> # usb device (not always there)
> allow-hotplug enx0
> iface enx0 inet manual
> up /sbin/ip link set $IFACE master br0
>
> auto br0
> iface br0 inet static
>   address 10.10.10.1/24
>   bridge-ports ens18
>   bridge-stp off
>   bridge-fd 0
>
> What that does is forces udev to execute "ifup enx0" on USB device
> detection, which in turn causes the network interface to attach to br0.
>
> Reco






auto add usb network to bridge

2023-09-25 Thread Petric Frank
Hello,

a special problem. I have a debian (12) machine which has an onboard network
card. This machine acts as dhcp-server also.

Now i want to add a usb network device. But this is not always there. It is
plugged in when needed. And it should serve the same network as the onboard
one.

My idea was to create a bridge and attach the host network interface to it.
The problem now is how to get the usb network card attached to the bridge when
plugged in.

My /etc/network/interfaces reads like this:
-- cut 
auto lo
iface lo inet loopback

# onloard device
iface ens18 inet manual

# usb device (not always there)
iface enx0 inet manual

auto br0
iface br0 inet static
  address 10.10.10.1/24
  bridge-ports ens18 enx0
  bridge-stp off
  bridge-fd 0
-- cut 

This works as long the usb device is plugged in at boot time.

Connecting it later the usb network device appears but will not be attached to
the bridge.

Any hints ?

regards
  Petric




qtcreator: no qml utility

2023-09-08 Thread Petric Frank
Hello,

on Debian 12 (Plasma Desktop) i've installed qtcreator from Debian repository.

In the settings of qtcreator the qt 5.15.8 is listed as Qt version. But with a
exclamation mark. Below i see "no QML utility installed".

But if i execute on cmdline

  qml -v

the output is

  Qml Runtime 5.15.8

"which qml" says /usr/bin/qml

This packages are installed:

  apt install qtcreator qml build-essential qtbase5-dev qt5-qmake cmake



Why qtcreator does not detect the qml utility ?
What is missing ?

kind regards
  Petric





Re: [Solved] Re: xrdp and KDE Plasma desktop

2023-07-18 Thread Petric Frank
Am Dienstag, 18. Juli 2023, 05:36:56 CEST schrieb Max Nikulin:
> On 15/07/2023 00:04, Petric Frank wrote:
> > After some debugging i found a working solution. Allocated file in/etc/
> > polkit-1/rules.d/99-networkmanager.rules containing:
> >
> > --- cut --
> > polkit.addRule(function(action, subject) {
> >
> >   if (action.id == "org.freedesktop.NetworkManager.network-control") {
> >
> > if (subject.isInGroup("netdev")) {
> >
> >  return polkit.Result.YES;
> >
> >}
> >
> >   }
> >
> > });
> > --- cut --
> >
> > Hope that helps others.
>
> https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.
> en.html#changes-to-polkit-configuration "5.1.13. Changes to polkit
> configuration":
>
> For consistency with upstream and other distributions, the polkit
> (formerly PolicyKit) service, which allows unprivileged programs to
> access privileged system services, has changed the syntax and location
> for local policy rules. You should now write local rules for customizing
> the security policy in JavaScript, and place them at
> /etc/polkit-1/rules.d/*.rules. Example rules using the new format can be
> found in /usr/share/doc/polkitd/examples/, and polkit(8) has further
> information.
>
> Previously, rules could be written in pkla format, and placed in
> subdirectories of /etc/polkit-1/localauthority or
> /var/lib/polkit-1/localauthority. However, .pkla files should now be
> considered deprecated, and will only continue to work if the
> polkitd-pkla package is installed. This package will usually be
> installed automatically when you upgrade to bookworm, but it is likely
> not to be included in future Debian releases, so any local policy
> overrides will need to be migrated to the JavaScript format.

Thanks for the link. It was a little problematic for me to find the correct
rules using the big "trash dump" like google and others. Finally i got it and
posted it here to help others with the same problem.

There are other services (device mount, etc.) affected by the "password
request" dialogs which also have to be covered this way when connecting via
xrdp. Maybe also driven by group membership.






[Solved] Re: xrdp and KDE Plasma desktop

2023-07-14 Thread Petric Frank
Am Freitag, 14. Juli 2023, 08:08:41 CEST schrieb Petric Frank:
> Am Donnerstag, 13. Juli 2023, 12:27:22 CEST schrieb Max Nikulin:
> > On 12/07/2023 20:51, Petric Frank wrote:
> > > If i look at the nmcli general permissions for the id i get:
> > >org.freedesktop.NetworkManager.network-control  auth
> > >
> > > If i log in locally i get:
> > >org.freedesktop.NetworkManager.network-control  yes
> > >
> > > It seems that something goes wrong - but what and how to fix it ?
> > > I use the same userid both times.
> >
> > Perhaps it is polkit that grants to local users more privileges than to
> > remote ones, e.g. to reboot or to power off. Moreover, it (or some other
> > daemon) may pass access e.g. to sound card on switch of currently active
> > session when several local users are logged in.
> >
> > Likely it is possible to change default policy to give more rights to a
> > specific user even when a remote session is started.
>
> Thanks for the hint.

After some debugging i found a working solution. Allocated file in /etc/
polkit-1/rules.d/99-networkmanager.rules containing:

--- cut --
polkit.addRule(function(action, subject) {
 if (action.id == "org.freedesktop.NetworkManager.network-control") {
   if (subject.isInGroup("netdev")) {
return polkit.Result.YES;
  }
 }
});
--- cut --

Hope that helps others.

kind regards
  Petric




Re: xrdp and KDE Plasma desktop

2023-07-14 Thread Petric Frank
Am Donnerstag, 13. Juli 2023, 12:27:22 CEST schrieb Max Nikulin:
> On 12/07/2023 20:51, Petric Frank wrote:
> > If i look at the nmcli general permissions for the id i get:
> >org.freedesktop.NetworkManager.network-control  auth
> >
> > If i log in locally i get:
> >org.freedesktop.NetworkManager.network-control  yes
> >
> > It seems that something goes wrong - but what and how to fix it ?
> > I use the same userid both times.
>
> Perhaps it is polkit that grants to local users more privileges than to
> remote ones, e.g. to reboot or to power off. Moreover, it (or some other
> daemon) may pass access e.g. to sound card on switch of currently active
> session when several local users are logged in.
>
> Likely it is possible to change default policy to give more rights to a
> specific user even when a remote session is started.

Thanks for the hint.

I found the page
  https://c-nergy.be/blog/?p=12073

which posts 2 possibilities for a similar problem on ubuntu.

The unsafe way (set Allow_Any = yes) works, but the safer one (define file in
/etc/polkit-1/localauthority.conf.d) not.

I created afiler named 02-networkmanager.conf containing:
--- cut 
polkit.addRule(function(action, subject) {
 if ((action.id == "org.freedesktop.NetworkManager.network-control") &&
 subject.isInGroup("{netdev}")) {
 return polkit.Result.YES;
 }
 });
--- cut 

I looks to me that either the directory is wrong and/or the file name is
wrong.

Any ideas ?

regards




xrdp and KDE Plasma desktop

2023-07-12 Thread Petric Frank
Hello,

i'm not sure where to look for this problem. Entering here because the Debian
Bookworm is used.

Installed Debian with Plasma desktop. The installed xrdp anf tigervnc-
standalone-server to allow RDP connections.

If i connect to this machine using xfreerdp the desktop is correctly shown.
But immediately a password request popup window is displayed containing this
(freely translated from german):

- cut 
Title: Authentication required
Action: Allow control of network connections
Identity: org.freedesktop.NetworkManager.network-control
...
- cut 

If i look at the nmcli general permissions for the id i get:

  org.freedesktop.NetworkManager.network-control  auth

If i log in locally i get:

  org.freedesktop.NetworkManager.network-control  yes


It seems that something goes wrong - but what and how to fix it ?
I use the same userid both times.

kind regards
  Petric