/produktinformationen.html)
Bevor wirklich der teure, proprietäre Kram gekauft werden muss, schaue ich noch
nach OS-Alternativen, um weitere Abhängigkeiten von Archikart AG zu verhindern.
Gibt man in Google einfach nur "Flurstücksverwaltung" ein, dann ist da
Archikart AG ganz oben.
Beste Grüße
Xave
quot; show the added
partition when calling sinfo on them.
Is the stored slurm.conf on every instance just a fallback for when
connection is down or what is the purpose? The documentation only says:
"This file should be consistent across all nodes in the cluster."
Best regards,
Xaver
--
w I feel like using the master to setup workers is
the better structure.
Best regards,
Xaver
On 08.04.24 18:18, Brian Andrus via slurm-users wrote:
Xaver,
You may want to look at the ResumeRate option in slurm.conf:
ResumeRate
The rate at which nodes in power save mode are retur
).
Is this somehow possible?
Best regards,
Xaver
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubscribe send an email to slurm-users-le...@lists.schedmd.com
them, no matter what -
and if that is not possible or desirable, uAPI has to be changed, for
example by introducing the mentioned "pageflip failed" event.
Looking forward to some answers,
Xaver Hugl
Am Mi., 6. März 2024 um 18:19 Uhr schrieb Mario Limonciello
:
> So the idea being if the compositor isn't using it we let
> power-profiles-daemon (or any other software) take control via sysfs and
> if the compositor does want to control it then it then it writes a DRM
> cap and we destroy the
Like already mentioned in the power profiles daemon repository, I don't think
this makes sense. This is a display setting, which compositors have interest
in controlling, for example to:
- disable it in a bright environment, because afaiu it reduces the maximum
screen brightness
- disable it
Am Mi., 6. März 2024 um 18:19 Uhr schrieb Mario Limonciello
:
> So the idea being if the compositor isn't using it we let
> power-profiles-daemon (or any other software) take control via sysfs and
> if the compositor does want to control it then it then it writes a DRM
> cap and we destroy the
Like already mentioned in the power profiles daemon repository, I don't think
this makes sense. This is a display setting, which compositors have interest
in controlling, for example to:
- disable it in a bright environment, because afaiu it reduces the maximum
screen brightness
- disable it
to handle "NOT_RESPONDING".
I would really like to improve my question if necessary.
Best regards,
Xaver
On 23.02.24 18:55, Xaver Stiensmeier wrote:
Dear slurm-user list,
I have a cloud node that is powered up and down on demand. Rarely it
can happen that slurm's resumeTimeout
er a while NOT_RESPONDING is removed, but I would like to move it
directly from within my fail script if possible so that the node can
return to service immediately and not be blocked by "NOT_RESPONDING".
Best regards,
Xaver
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsub
of the job.
Is there some way to achieve the described effect i.e. tell Slurm: "You
can stop waiting, the node won't come alive." or am I missing the
correct way how this should be handled in Slurm?
Best regards,
Xaver
--
slurm-users mailing list -- slurm-users@lists.schedmd.com
To unsubs
Signed-off-by: Xaver Hugl
---
drivers/gpu/drm/drm_connector.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c
index b0516505f7ae..01e13984629b 100644
--- a/drivers/gpu/drm/drm_connector.c
+++ b/drivers/gpu/drm
/slurm` and that was enough, but I must admit that I am not
completely familiar with it, but I will now look into it closer and also
double check whether such a key is stored there in the old slurm version.
Best regards,
Xaver
On 08.02.24 11:07, Luke Sudbery via slurm-users wrote:
Your systemctl
It might be coming from a
previous problem I tried to fix (basically a few deprecated keys in the
configuration).
I will try to restart the entire cluster with the added changes to rule
out any follow up errors, but maybe it's something obvious a fellow list
user can see.
Best regards,
Xaver
--
slurm-users ma
Am Mo., 22. Jan. 2024 um 16:50 Uhr schrieb Harry Wentland
:
>
>
>
> On 2024-01-19 13:25, Ville Syrjälä wrote:
> > On Fri, Jan 19, 2024 at 03:12:35PM -0300, André Almeida wrote:
> >> AMD GPUs can do async flips with changes on more properties than just
> >> the FB ID, so implement a custom
Am Mo., 22. Jan. 2024 um 16:50 Uhr schrieb Harry Wentland
:
>
>
>
> On 2024-01-19 13:25, Ville Syrjälä wrote:
> > On Fri, Jan 19, 2024 at 03:12:35PM -0300, André Almeida wrote:
> >> AMD GPUs can do async flips with changes on more properties than just
> >> the FB ID, so implement a custom
his and in what
> > > situations?
> > > >>>
> > > >>> Or is this not meant for generic userspace?
> > > >>
> > > >> Sorry, I forgot to document this. So the idea is that userspace will
> > > >> query what they
his and in what
> > > situations?
> > > >>>
> > > >>> Or is this not meant for generic userspace?
> > > >>
> > > >> Sorry, I forgot to document this. So the idea is that userspace will
> > > >> query what they
having capabilities for each prop.
> >
> > That's the theory, but do you have a practical example?
> >
> > What other planes and props would one want change in some specific use
> > case?
> >
> > Is it just "all or nothing", or would th
having capabilities for each prop.
> >
> > That's the theory, but do you have a practical example?
> >
> > What other planes and props would one want change in some specific use
> > case?
> >
> > Is it just "all or nothing", or would th
Great, thank you!
Am Do., 11. Jan. 2024 um 19:05 Uhr schrieb André Almeida <
andrealm...@igalia.com>:
> Em 11/01/2024 14:59, Xaver Hugl escreveu:
> > Am Do., 11. Jan. 2024 um 18:13 Uhr schrieb Simon Ser
> > mailto:cont...@emersion.fr>>:
> >
> > Are we
Am Do., 11. Jan. 2024 um 18:13 Uhr schrieb Simon Ser :
> Are we sure that all drivers handle these two props properly with async
> page-flips? This is a new codepath not taken by the legacy uAPI.
>
I've only tested on amdgpu so far. Afacs the other drivers that would need
testing / that support
Like with FB_ID, the driver never has to do bandwidth validation to use
these properties, so there's no reason not to allow them.
Signed-off-by: Xaver Hugl
---
drivers/gpu/drm/drm_atomic_uapi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm
Am Mi., 10. Jan. 2024 um 01:28 Uhr schrieb Zack Rusin <
zack.ru...@broadcom.com>:
> On Tue, Jan 9, 2024 at 11:06 AM Xaver Hugl wrote:
> >
> > Hi,
> >
> > KWin does use DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT.
>
> Can you point me to the code that implements
[
https://issues.apache.org/jira/browse/MBUILDCACHE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804848#comment-17804848
]
Xaver edited comment on MBUILDCACHE-73 at 1/9/24 8:30 PM:
--
Hi there,
V1.0.1
[
https://issues.apache.org/jira/browse/MBUILDCACHE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804848#comment-17804848
]
Xaver commented on MBUILDCACHE-73:
--
Hi there,
V1.0.1 works awesome (we use it in a large multi
Hi,
KWin does use DRM_CLIENT_CAP_CURSOR_PLANE_HOTSPOT. Tying the check to
DRM_CLIENT_CAP_ATOMIC instead would IMO make more sense though (even if it's
still weird) and would work with older versions of KWin and other compositors.
Greetings,
Xaver Hugl
Hi,
I tested the patch and it fixes the issue for me too. Consider it
Tested-By Xaver Hugl
- Xaver
Am Mo., 1. Jan. 2024 um 22:37 Uhr schrieb Joshua Ashton :
> From the issue:
>
> ```
> Thank you for for fixing this!
> I built a custom kernel with this patch on the fedora
(s) got
removed immediately.
I will take a look at /var/log. That's a good idea. I don't think that
there will be anything unusual, but it's something I haven't thought
about yet (the reason of the error being somewhere else).
Best regards
Xaver
On 10.12.23 00:41, Brian Andrus wrote:
Xaver
hat Slurmd is placing in this dir that fills
up the space. Do you have any ideas? Due to the workflow used, we have a
hard time reconstructing the exact scenario that caused this error. I
guess, the "fix" is to just pick a bit larger disk, but I am unsure
whether Slurm behaves normal here.
Sorry, it looks like I sent this too soon. I tested the patch on a
second PC and it doesn't fix the issue there.
Am Do., 7. Dez. 2023 um 19:25 Uhr schrieb Xaver Hugl :
>
> With VRR, every atomic commit affecting a given display must trigger
> a new scanout cycle, so that userspac
://gitlab.freedesktop.org/drm/amd/-/issues/3034
Cc: sta...@vger.kernel.org
Signed-off-by: Xaver Hugl
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display
Sorry, it looks like I sent this too soon. I tested the patch on a
second PC and it doesn't fix the issue there.
Am Do., 7. Dez. 2023 um 19:25 Uhr schrieb Xaver Hugl :
>
> With VRR, every atomic commit affecting a given display must trigger
> a new scanout cycle, so that userspac
://gitlab.freedesktop.org/drm/amd/-/issues/3034
Cc: sta...@vger.kernel.org
Signed-off-by: Xaver Hugl
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
b/drivers/gpu/drm/amd/display
or not, but it's worth a try.
Best regards
Xaver
On 06.12.23 12:03, Ole Holm Nielsen wrote:
On 12/6/23 11:51, Xaver Stiensmeier wrote:
Good idea. Here's our current version:
```
sinfo -V
slurm 22.05.7
```
Quick googling told me that the latest version is 23.11. Does the
upgrade change anything
Hi Ole,
Good idea. Here's our current version:
```
sinfo -V
slurm 22.05.7
```
Quick googling told me that the latest version is 23.11. Does the
upgrade change anything in that regard? I will keep reading.
Xaver
On 06.12.23 11:09, Ole Holm Nielsen wrote:
Hi Xaver,
Your version of Slurm may
at
`DebugFlags=Power`. `PrivateData=cloud` was an annoying thing to find
out; SLURM plans/planned to change that in the future (cloud key behaves
different than any other key in PrivateData). Of course our setup
differs a little in the details.
Best regards
Xaver
On 06.12.23 10:30, Ole Holm Nielsen wrote
Maybe someone has a great idea how to tackle this problem.
Best regards
Xaver Stiensmeier
I'm afraid that would not be very useful. It indeed depends on the refresh
rate, but also on how close to vblank the compositor does its commits / on
what the latency requirements for the currently shown content are.
When the compositor presents a fullscreen video with frames that are queued
up in
I'm afraid that would not be very useful. It indeed depends on the refresh
rate, but also on how close to vblank the compositor does its commits / on
what the latency requirements for the currently shown content are.
When the compositor presents a fullscreen video with frames that are queued
up in
Am Fr., 27. Okt. 2023 um 12:01 Uhr schrieb Sebastian Wick <
sebastian.w...@redhat.com>:
> On Fri, Oct 27, 2023 at 10:59:25AM +0200, Michel Dänzer wrote:
> > On 10/26/23 21:25, Alex Goins wrote:
> > > On Thu, 26 Oct 2023, Sebastian Wick wrote:
> > >> On Thu, Oct 26, 2023 at 11:57:47AM +0300, Pekka
Am Fr., 27. Okt. 2023 um 12:01 Uhr schrieb Sebastian Wick <
sebastian.w...@redhat.com>:
> On Fri, Oct 27, 2023 at 10:59:25AM +0200, Michel Dänzer wrote:
> > On 10/26/23 21:25, Alex Goins wrote:
> > > On Thu, 26 Oct 2023, Sebastian Wick wrote:
> > >> On Thu, Oct 26, 2023 at 11:57:47AM +0300, Pekka
Hi,
Victoria wanted to take part in this meeting, but she's on vacation during
that week. Would you mind having the meeting the week afterwards instead?
Best regards,
Xaver
Am Do., 17. Aug. 2023 um 21:44 Uhr schrieb Simon Zeni :
> Hello there!
>
> Apologies again for the duplicated g
Hi everyone,
Monday 7th of August 2023, 11:00 CEST has been selected for next weeks
meeting.
Best regards,
Xaver
Am Do., 3. Aug. 2023 um 00:58 Uhr schrieb Xaver Hugl :
> This is a meeting annoucement.
>
> The Wayland Governance Meeting is semi-regular meeting to drive
> discussio
of August.
Notes of previous meetings can be found
here:https://gitlab.freedesktop.org/wayland/wayland-protocols/-/wikis/meetings
In the interest of not having the meeting-link publically available,
please contact me under xaver.h...@kde.org if you wish to
participate.
Best regards,
Xaver Hugl
art slurmd*
# master
run without any issues afterwards.
Thank you for all your help!
Best regards,
Xaver
On 19.07.23 17:05, Xaver Stiensmeier wrote:
Hi Hermann,
count doesn't make a difference, but I noticed that when I reconfigure
slurm and do reloads afterwards, the error "gpu c
rect, so I assume it must be the gpus entry, but I don't see where
it's wrong:
NodeName=NName SocketsPerBoard=8 CoresPerSocket=1 RealMemory=8000
Gres=gpu:1 State=CLOUD # bibiserv
Thanks for all the help,
Xaver
On 19.07.23 15:04, Hermann Schwärzler wrote:
Hi Xaver,
I think you are missing
her. I am thankful for any ideas in that regard.
Best regards,
Xaver
On 19.07.23 10:23, Xaver Stiensmeier wrote:
Alright,
I tried a few more things, but I still wasn't able to get past: srun:
error: Unable to allocate resources: Invalid generic resource (gres)
specification.
I should ment
t=0,max_sched_time=2,partition_job_depth=0,sched_max_job_start=0,sched_min_interval=2
I am a bit unsure what to do next to further investigate this issue.
Best regards,
Xaver
On 17.07.23 15:57, Groner, Rob wrote:
That would certainly do it. If you look at the slurmctld log when it
comes up, i
for testing purposes. Could this be the issue?
Best regards,
Xaver Stiensmeier
On 17.07.23 14:11, Hermann Schwärzler wrote:
Hi Xaver,
what kind of SelectType are you using in your slurm.conf?
Per https://slurm.schedmd.com/gres.html you have to consider:
"As for the --gpu* option, these op
) and using one of
those didn't work in my case.
Obviously, I am misunderstanding something, but I am unsure where to look.
Best regards,
Xaver Stiensmeier
:
Allowing all nodes to be powered up, but without automatic suspending
for some nodes except when triggering power down manually.
---
I tried using negative times for SuspendTime, but that didn't seem to
work as no nodes are powered up then.
Best regards,
Xaver Stiensmeier
I can't say anything about the other commits in this series, but
"Document in which order the CTM matrix elements are stored" is
Reviewed-by: Xaver Hugl
I can't say anything about the other commits in this series, but
"Document in which order the CTM matrix elements are stored" is
Reviewed-by: Xaver Hugl
partitions and allocates
all 8 nodes.
Best regards,
Xaver Stiensmeier
question asks
how to have multiple default partitions which could include having
others that are not default.
Best regards,
Xaver Stiensmeier
On 17.04.23 11:12, Xaver Stiensmeier wrote:
Dear slurm-users list,
is it possible to somehow have two default partitions? In the best case
in a way
Dear slurm-users list,
is it possible to somehow have two default partitions? In the best case
in a way that slurm schedules to partition1 on default and only to
partition2 when partition1 can't handle the job right now.
Best regards,
Xaver Stiensmeier
ere larger instances started than needed? ...
I know that this question is currently very open, but I am still trying
to narrow down where I have to look. The final goal is of course to use
this evaluation to pick better timeout values and improve cloud scheduling.
Best regards,
Xaver Stiensmeier
.
So I am basically looking for custom requirements.
Best regards,
Xaver Stiensmeier
ition" in `JobSubmitPlugins`
and this might be the solution. However, I think this is something so
basic that it probably shouldn't need a plugin so I am unsure.
Can anyone point me towards how setting the default partition is done?
Best regards,
Xaver Stiensmeier
Dear community,
we are currently facing the challenge that some devices at which we import
.p12 certificate containers from our OpenXPKI, are having problems
processing them.
After checking with the vendor of one of the devices, it seems that
OpenXPKI are encrypting the .p12 container with
ent - close windows and adopt a penguin!
[Anhang "attleugg.txt" gelöscht von Franz-Xaver Birnboeck/KG/Lindner]
[Anhang "att7wvqf.txt" gelöscht von Franz-Xaver Birnboeck/KG/Lindner]
___
OpenXPKI-users mailing list
OpenXPKI-users@lists.
Dear community,
we currently have the challenge that we need a TLS-certificate that has
"IP security end system (1.3.6.1.5.5.7.3.5)" as extended key usage
configured.
Looking at the options in the certificate profiles, we can set a wide
variety of extended usages like code_signing ,
e
maximum explicit.
Best regards,
Xaver Stiensmeier
PS: This is the first time I use the slurm-user list and I hope I am not
violating any rules with this question. Please let me know, if I do.
great!
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kwin in Ubuntu.
https://bugs.launchpad.net/bugs/1990783
Title:
[radeon] Distorted mouse pointer under Wayland in Kubuntu 22.10
To manage notifications about this bug go to:
.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kwin in Ubuntu.
https://bugs.launchpad.net/bugs/1990783
Title:
[radeon] Distorted mouse pointer under Wayland in Kubuntu 22.10
To manage notifications about this bug go to:
Can someone with an affected setup confirm whether or not it's still an
issue with 5.26?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kwin in Ubuntu.
https://bugs.launchpad.net/bugs/1990783
Title:
[radeon] Distorted mouse pointer under
** Summary changed:
- wait_for_server doesn't actually wait till server is state=active
+ wait_for_server doesn't actually wait till server is state=active (mistake,
can be deleted)
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a
Public bug reported:
openstack connection states that wait_for_server "Wait for a server to
reach ACTIVE status." but it doesn't. It waits longer than usual, but
not until server reaches ACTIVE status.
** Affects: nova
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
Description: When using connections available_floating_ip(network, server) in
the past it automatically attached an existing un-attached floating-ip (or
created a new one) to the given server.
Now available_floating_ip(network, server) only returns the ip address when
Dear community,
we upgraded to version 3.20 a while ago since we wanted to test out the
new SCEP features, to get some systems working that have problems with it
currently. After we enabled the new scepv3 script in webserver, we get the
following error when trying to request the ca certs via
,
Xaver
zamundaaa added a comment.
If you want to make it official, would you be interested in helping to make
tiling a part of KWin directly? https://invent.kde.org/plasma/kwin/-/issues/10
If it's bult-in then more integration could be done, for example with effects
and the current quick tile
schrieb am So. 20. Juni 2021
um 12:00:
> Send NetBehaviour mailing list submissions to
> netbehaviour@lists.netbehaviour.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.netbehaviour.org/mailman/listinfo/netbehaviour
> or, via email, send a
company it will be lot money
to pay. And you don't know if other companies will money to...
Greetings Xaver
-Ursprüngliche Nachricht-
Von: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@lists.swinog.ch] Im
Auftrag von roger mgz
Gesendet: Sonntag, 28. Februar 2021 14:53
An: swinog
. And Migros and Coop are not delivery things in other countries...
Greetings
Xaver
-Ursprüngliche Nachricht-
Von: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@lists.swinog.ch] Im
Auftrag von roger mgz
Gesendet: Sonntag, 28. Februar 2021 14:53
An: swinog@lists.swinog.ch
Betreff: Re
https://bugs.kde.org/show_bug.cgi?id=421212
Xaver changed:
What|Removed |Added
CC||emailic...@gmail.com
--- Comment #2 from Xaver
https://bugs.kde.org/show_bug.cgi?id=422702
Xaver changed:
What|Removed |Added
CC||emailic...@gmail.com
--- Comment #2 from Xaver
https://bugs.kde.org/show_bug.cgi?id=370726
Xaver changed:
What|Removed |Added
CC||emailic...@gmail.com
--- Comment #4 from Xaver
https://bugs.kde.org/show_bug.cgi?id=370726
Xaver changed:
What|Removed |Added
CC||emailic...@gmail.com
--- Comment #4 from Xaver
https://bugs.kde.org/show_bug.cgi?id=365787
Xaver changed:
What|Removed |Added
CC||emailic...@gmail.com
--- Comment #8 from Xaver
https://bugs.kde.org/show_bug.cgi?id=375951
Xaver changed:
What|Removed |Added
CC||emailic...@gmail.com
--- Comment #36 from Xaver
https://bugs.kde.org/show_bug.cgi?id=360478
--- Comment #72 from Xaver ---
If I had to guess where your problem comes from then I'd say the driver is
doing mode changes on login (had that one for a while too, on my 5700 XT and
multiple monitors) and then Plasma shifts the widgets around to make
https://bugs.kde.org/show_bug.cgi?id=360478
--- Comment #70 from Xaver ---
There seems to be a lot of confusion here. This is *not* a bug in the code that
needs to be fixed. This is *not* an accidental change of widget positions, it's
*intentional*.
This bug report is a feature request
https://bugs.kde.org/show_bug.cgi?id=362990
Xaver changed:
What|Removed |Added
CC||emailic...@gmail.com
--- Comment #1 from Xaver ---
I
: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: xaver...@web.de
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.18.5)
Qt Version: 5.14.2
Frameworks
https://bugs.kde.org/show_bug.cgi?id=421254
Bug ID: 421254
Summary: Optional mouse edge resistance between monitors
Product: kwin
Version: git master
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=360478
Xaver changed:
What|Removed |Added
CC||emailic...@gmail.com
--- Comment #46 from Xaver
On 02.04.20 20:38, Richard Kimberly Heck wrote:
On 4/2/20 12:09 PM, Xaver Gerster wrote:
Dear LyX users,
I am lacking a "revtex4-2.layout" in my (latest) LyX ver. 2.3.4.2. Is
this really true?
Stemming from the APS, the revtex package is probably among some of
the most heavily
Dear LyX users,
I am lacking a "revtex4-2.layout" in my (latest) LyX ver. 2.3.4.2. Is
this really true?
Stemming from the APS, the revtex package is probably among some of the
most heavily used latex packages in natural science and physics. The 4.2
version of revtex is out since more than a
https://bugs.kde.org/show_bug.cgi?id=417323
--- Comment #2 from Xaver ---
Yes I am. I read on Phabricator that multi GPU support for Wayland in general
is still on the TODO list, so I guess this issue is probably gonna be solved
once that's done.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=417323
Bug ID: 417323
Summary: iGPU multi-monitor support missing
Product: kwin
Version: git master
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: normal
eck: 0:00:00 ago on Mon 27 Aug 2018 09:08:56 AM
> +08.
> Dependencies resolved.
> Nothing to do.
> Complete!
Thanks in advance
Xaver
Sent with [ProtonMail](https://protonmail.com) Secure Email.
--
You received this message because you are subscribed to the Google Groups
"qubes
Hello,
Could someone from Sunrise TV me contact offline
Thanks
And Greetings
Xaver
___
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
nicht in der Hotline.
Gruss Xaver
-Ursprüngliche Nachricht-
Von: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@lists.swinog.ch] Im
Auftrag von Matthias Cramer
Gesendet: Freitag, 28. Juni 2019 09:37
An: swinog@lists.swinog.ch
Betreff: Re: [swinog] Geldspielgesetz: Zugangssperren Q
der Provider eine Schadensersatzzahlung in Millionenhöhe leisten. Ich
weiss und ein Schweizer ISP hat gegen Apple oder Google sehr schlechte Karten.
Mit freundlichen Grüssen
X. Aerni
Xaver Aerni
Xariffusion Informatik & Telecom
Zürichstrasse 10a
8340 Hinwil
Tel. +41 43 843 78 78
Befürworter
haben total falsche Angaben gemacht. Weil die Sperren über die Spielbanken
gehen.
Mit freundlichen Grüssen
X. Aerni
Xaver Aerni
Xariffusion Informatik & Telecom
Zürichstrasse 10a
8340 Hinwil
Tel. +41 43 843 78 78
+1 707 361 68 39
Fax +41 43 843 78 70
xae...@pop.ch
uild Host : swkj07
Relocations : (not relocatable)
Packager: packman@links2linux.de
Vendor : http://packman.links2linux.de
Best wishes
Xaver Hellauer
___
Packman mailing list
Packman@links2linux.de
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Sunday, February 17, 2019 9:49 PM, wrote:
> Reading through the post questioning the trustworthiness of Whonix, I can't
> tell whether we can continue trusting/using Whonix or not. Can someone
> (preferably in a
1 - 100 of 916 matches
Mail list logo
