On 11/15/18 4:47 PM, Thierry Laurion wrote:
I would strongly advise digging into the skulls project anyone
interested in flashing coreboot into their x230 themselves :
https://github.com/merge/skulls/blob/master/README.md
Hi,
They suggest updating the original BIOS before flashing Skull. But
Hello!
So, I switched to KDE as you can see in some other threads, and honestly I like
it way better than XFCE.
My biggest issue right now however is, that the network manager applet does not
show in KDE. I get notification when I start my session that I am connected to
my network, and I do
On 11/17/2018 04:44 AM, aaq via qubes-users wrote:
Hello!
So, I switched to KDE as you can see in some other threads, and honestly I like
it way better than XFCE.
My biggest issue right now however is, that the network manager applet does not
show in KDE. I get notification when I start my
On Wednesday, July 11, 2018 at 6:52:55 AM UTC+3, Sphere wrote:
> On Tuesday, July 10, 2018 at 12:26:03 PM UTC, awokd wrote:
> > On Tue, July 10, 2018 6:17 am, Sphere wrote:
> > > Here is info about my System:
> > > Dell Inspiron 15 Gaming 7577
> > > Intel Core i7-7700HQ CPU @ 2.80GHz
> > > Intel
Hello,
I'm trying to install Qubes 4.0.1-rc1 on 'Dell Inspiron 15 7000 Gaming' laptop.
The installer first works fine without crashes, then when reaching
'qubes-mgmt-salt-base-topd.noarch' it freezes.
I need help to get this Qubes installed on the laptop because I love Qubes!
I'm currently
sm...@tutamail.com:
> ...again I want to thank the Whonix/Qubes team for everything they do!! You
> are awesome...
>
> In the spirit of feedback:
>
> I just tried updating Whonix-ws-14 and started receiving errors? I saw
> another post with similar
>
Probably transient issue.
Documented here:
https://www.whonix.org/wiki/Qubes/Update
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Dave:
> Success! but not without a few snags...
>
> Using Qube-Manager to remove templateVM resulted in:
> [Dom0] Error removing Qube! ERROR: Domain is in use: details in system log
>
> ran QVM-LS; verified Qube state halted
>
> found reference:
Documentation was upgraded meanwhile.
Black Beard:
>
> Hey Community,
>
>
> i tried to following the tutorial to upgrade Whonix 13 to 14.
>
> https://www.whonix.org/wiki/Qubes/Install
>
> I first start to try uninstall the old Version of Whonix with Option B.
>
> When i tried to install the
Máté Kovács:
> After I installed the new version of qubes, I tried everything today
> afternoon to make it work but it wasn't successfull. Update every software.
> Got these error messages.
If you are talking about Whonix...
Qubes-Whonix support ending for Qubes 3.2(.1) - upgrade to Qubes R4.0
Stay tuned!
Basically it's hopefully all been covered in news.
https://www.whonix.org/wiki/Stay_Tuned
Qubes-Whonix documentation:
https://www.whonix.org/wiki/Qubes
https://www.whonix.org/wiki/Qubes/Install
https://www.whonix.org/wiki/Qubes/Reinstall
qubes-...@tutanota.com:
> Hi, I learned that in Whonix-14 in Qubes 4.0 there is no default support for
> pEp in Enigmail-Thunderbird. Is it Qubes specific or Whonix specific? Is
> there any reason for not supporting pEp in Whonix?
>
> In other templates after installing the Enigmail addon the
Franz:
> I succesfully updated to whonix 14, when the VM start a message tells:
> "connected to tor" making me happy, But if I ping google I get:
>
> user@host:~$ ping google.com
> PING google.com (216.58.207.206) 56(84) bytes of data.
>>From 10.137.5.34 (10.137.5.34) icmp_seq=1 Destination Port
Franz:
> On Thu, Nov 15, 2018 at 4:47 PM pieter lems wrote:
>
>> is sys-net connected to the network?
>>
>
> yes
>
> And are you using an ethernet cable to connect to internet,
>>
>
> no I am connected by wifi
>
Qubes-Whonix support ending for Qubes 3.2(.1) - upgrade to Qubes R4.0 or
above
William Fisher:
> Turned out to be a clock settings problem. Set the clock to UTC and poof it
> works!
>
Host clock or VM clock?
How did you do it?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
b...@damon.com:
> I went thru the steps to remove any existing whonix. No errors were reported.
> Then I issued the command to re-install whonix-14.
>
> Whonix does not work. Whenever I boot up one of the VMs based on the new
> whonix, I find that qrexec-agent is crashing.
>
> [ 15.903799]
Hi,
It seems that the i3 window manager has been in the testing repository for a
while, and I don't see many bug reports or posts on the mailing lists with
problems associated to the i3 window manager.
Anything else required to make this package stable or when it can be moved to
the stable
Hey community,
i hope, that someone can help me by following probleme.
My main OS is Qubes 4.0. No Dual-boot or other stuff. Only Qubes 4.0 installed.
My target:
Install Chuckoo Sandbox in Virtualbox on Debian9
https://cuckoo.sh/docs/installation/host/index.html
On my Debian9 Template i
lørdag den 17. november 2018 kl. 17.01.02 UTC+1 skrev Patrick Schleizer:
> Franz:
> > I succesfully updated to whonix 14, when the VM start a message tells:
> > "connected to tor" making me happy, But if I ping google I get:
> >
> > user@host:~$ ping google.com
> > PING google.com
Den lør. 17. nov. 2018 kl. 13.54 skrev Chris Laprise :
> On 11/17/2018 04:44 AM, aaq via qubes-users wrote:
> > Hello!
> >
> > So, I switched to KDE as you can see in some other threads, and honestly
> I like it way better than XFCE.
> >
> > My biggest issue right now however is, that the network
20 matches
Mail list logo