[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-04-20 Thread 'Антон Чехов' via qubes-users
On Friday, April 20, 2018 at 1:38:36 AM UTC+2, cooloutac wrote:
> On Thursday, April 19, 2018 at 6:38:57 AM UTC-4, Антон Чехов wrote:
> > On Thursday, April 19, 2018 at 12:27:25 PM UTC+2, cooloutac wrote:
> > > On Thursday, April 19, 2018 at 6:19:45 AM UTC-4, Антон Чехов wrote:
> > > > On Saturday, February 17, 2018 at 1:06:16 AM UTC+1, Daniel Moerner 
> > > > wrote:
> > > > > On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner 
> > > > > wrote:
> > > > > > Hi all,
> > > > > > 
> > > > > > After a recent reboot, the devices and VM tray icons no longer are 
> > > > > > appearing on boot in Xfce. I have no idea what might have caused 
> > > > > > this. There were no dom0 updates in the meantime. If I try to 
> > > > > > manually run them, e.g., python3 -mqui.tray.devices, I get the 
> > > > > > following:
> > > > > > 
> > > > > > ERROR:dbus.proxies.Introspect error on 
> > > > > > org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> > > > > > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 
> > > > > > Message recipient disconnected from message bus without replying
> > > > > > 
> > > > > > Followed by a backtrace, the relevant part appears to be:
> > > > > > File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 
> > > > > > 22, in 
> > > > > >DOMAINS = qui.models.qubes.DomainManager()
> > > > > > 
> > > > > > Any advice would be appreciated, since with no icons, I'm also not 
> > > > > > appearing to get notifications for devices and VM actions.
> > > > > > 
> > > > > > Best,
> > > > > > Daniel
> > > > > 
> > > > > Interesting discovery: this problem arose as a result of setting 
> > > > > qrexec_timeout on an arbitrary VM to a value larger than an INT32. So 
> > > > > the moral of the story: Don't try to set qrexec_timeout too high!
> > > > > 
> > > > > Daniel
> > > > 
> > > > Hello,
> > > > 
> > > > I am experiencing the same problem with the final version of 4.0 but I 
> > > > did not change a setting of qrexec_timeout. The device tray icon 
> > > > disappeared suddenly.
> > > > 
> > > > I am getting tons of "GTK error" when trying to run manually via 
> > > > "python3 -mqui.tray.devices"?
> > > > 
> > > > So far I haven't been able to get the devices tray appear again but I 
> > > > can attach devices via command line.
> > > > 
> > > > Anyone having the same problem?
> > > 
> > > no,  weird.  have you tried to use qubes-manager at all?
> > 
> > Do you mean the VM manager? If so, yes! It does work with a lot of bugs 
> > like a lot of people reported already. I don't see all apps in the VM 
> > manager and the lights indicating a working app do only appear or disappear 
> > when clicking an app. Sometimes I forget an app is still running.
> > VPN apps I created don't appear in the VM manager at all, so I do need to 
> > use CLI.
> > 
> > Having a working devices tray icon would be nice, though.
> 
> ya hope they fix that issue soon.  What I do is keep hitting the green 
> refresh icon on top to refresh the manager to see the current vm states.  For 
> some reason it doesn't refresh on its own.   Weird that custom appvms you 
> create don't appear in the manager.
> 
> Have you made alot of customizations in dom0?

None at all!
I tried using Qubes 4 before the final release but had problems during install. 
The final version worked flawlessly. I did not want to import any VMs from 3.2 
because I had problems before and I wanted to do a clean install with 
everything built in Qubes 4. 
So far I can't complain. The problems I am having are all of minor importance. 
I had some problems with localization and keyboard, and problems with icons and 
the VM manager. All in all the system is working fine but I prefer working with 
3.2 in the meantime. The icons and the look is really great. I hope that Qubes 
4 will get there eventually.

I am using a Lenovo T420 with 16GB and stock BIOS. I am planning on using 
coreboot sometime in the future.

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d1ce1cc1-cf5f-4e8a-a5e2-f60b13f7eb21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-04-19 Thread cooloutac
On Thursday, April 19, 2018 at 6:38:57 AM UTC-4, Антон Чехов wrote:
> On Thursday, April 19, 2018 at 12:27:25 PM UTC+2, cooloutac wrote:
> > On Thursday, April 19, 2018 at 6:19:45 AM UTC-4, Антон Чехов wrote:
> > > On Saturday, February 17, 2018 at 1:06:16 AM UTC+1, Daniel Moerner wrote:
> > > > On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner wrote:
> > > > > Hi all,
> > > > > 
> > > > > After a recent reboot, the devices and VM tray icons no longer are 
> > > > > appearing on boot in Xfce. I have no idea what might have caused 
> > > > > this. There were no dom0 updates in the meantime. If I try to 
> > > > > manually run them, e.g., python3 -mqui.tray.devices, I get the 
> > > > > following:
> > > > > 
> > > > > ERROR:dbus.proxies.Introspect error on 
> > > > > org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> > > > > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 
> > > > > Message recipient disconnected from message bus without replying
> > > > > 
> > > > > Followed by a backtrace, the relevant part appears to be:
> > > > > File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 22, 
> > > > > in 
> > > > >DOMAINS = qui.models.qubes.DomainManager()
> > > > > 
> > > > > Any advice would be appreciated, since with no icons, I'm also not 
> > > > > appearing to get notifications for devices and VM actions.
> > > > > 
> > > > > Best,
> > > > > Daniel
> > > > 
> > > > Interesting discovery: this problem arose as a result of setting 
> > > > qrexec_timeout on an arbitrary VM to a value larger than an INT32. So 
> > > > the moral of the story: Don't try to set qrexec_timeout too high!
> > > > 
> > > > Daniel
> > > 
> > > Hello,
> > > 
> > > I am experiencing the same problem with the final version of 4.0 but I 
> > > did not change a setting of qrexec_timeout. The device tray icon 
> > > disappeared suddenly.
> > > 
> > > I am getting tons of "GTK error" when trying to run manually via "python3 
> > > -mqui.tray.devices"?
> > > 
> > > So far I haven't been able to get the devices tray appear again but I can 
> > > attach devices via command line.
> > > 
> > > Anyone having the same problem?
> > 
> > no,  weird.  have you tried to use qubes-manager at all?
> 
> Do you mean the VM manager? If so, yes! It does work with a lot of bugs like 
> a lot of people reported already. I don't see all apps in the VM manager and 
> the lights indicating a working app do only appear or disappear when clicking 
> an app. Sometimes I forget an app is still running.
> VPN apps I created don't appear in the VM manager at all, so I do need to use 
> CLI.
> 
> Having a working devices tray icon would be nice, though.

ya hope they fix that issue soon.  What I do is keep hitting the green refresh 
icon on top to refresh the manager to see the current vm states.  For some 
reason it doesn't refresh on its own.   Weird that custom appvms you create 
don't appear in the manager.

Have you made alot of customizations in dom0?

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/085a4c69-5cde-4284-897f-98bc8855e217%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-04-19 Thread 'Антон Чехов' via qubes-users
On Thursday, April 19, 2018 at 12:27:25 PM UTC+2, cooloutac wrote:
> On Thursday, April 19, 2018 at 6:19:45 AM UTC-4, Антон Чехов wrote:
> > On Saturday, February 17, 2018 at 1:06:16 AM UTC+1, Daniel Moerner wrote:
> > > On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner wrote:
> > > > Hi all,
> > > > 
> > > > After a recent reboot, the devices and VM tray icons no longer are 
> > > > appearing on boot in Xfce. I have no idea what might have caused this. 
> > > > There were no dom0 updates in the meantime. If I try to manually run 
> > > > them, e.g., python3 -mqui.tray.devices, I get the following:
> > > > 
> > > > ERROR:dbus.proxies.Introspect error on 
> > > > org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> > > > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 
> > > > Message recipient disconnected from message bus without replying
> > > > 
> > > > Followed by a backtrace, the relevant part appears to be:
> > > > File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 22, 
> > > > in 
> > > >DOMAINS = qui.models.qubes.DomainManager()
> > > > 
> > > > Any advice would be appreciated, since with no icons, I'm also not 
> > > > appearing to get notifications for devices and VM actions.
> > > > 
> > > > Best,
> > > > Daniel
> > > 
> > > Interesting discovery: this problem arose as a result of setting 
> > > qrexec_timeout on an arbitrary VM to a value larger than an INT32. So the 
> > > moral of the story: Don't try to set qrexec_timeout too high!
> > > 
> > > Daniel
> > 
> > Hello,
> > 
> > I am experiencing the same problem with the final version of 4.0 but I did 
> > not change a setting of qrexec_timeout. The device tray icon disappeared 
> > suddenly.
> > 
> > I am getting tons of "GTK error" when trying to run manually via "python3 
> > -mqui.tray.devices"?
> > 
> > So far I haven't been able to get the devices tray appear again but I can 
> > attach devices via command line.
> > 
> > Anyone having the same problem?
> 
> no,  weird.  have you tried to use qubes-manager at all?

Do you mean the VM manager? If so, yes! It does work with a lot of bugs like a 
lot of people reported already. I don't see all apps in the VM manager and the 
lights indicating a working app do only appear or disappear when clicking an 
app. Sometimes I forget an app is still running.
VPN apps I created don't appear in the VM manager at all, so I do need to use 
CLI.

Having a working devices tray icon would be nice, though.

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fa424de1-e570-44c8-b6e7-101ab0b37781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-04-19 Thread cooloutac
On Thursday, April 19, 2018 at 6:19:45 AM UTC-4, Антон Чехов wrote:
> On Saturday, February 17, 2018 at 1:06:16 AM UTC+1, Daniel Moerner wrote:
> > On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner wrote:
> > > Hi all,
> > > 
> > > After a recent reboot, the devices and VM tray icons no longer are 
> > > appearing on boot in Xfce. I have no idea what might have caused this. 
> > > There were no dom0 updates in the meantime. If I try to manually run 
> > > them, e.g., python3 -mqui.tray.devices, I get the following:
> > > 
> > > ERROR:dbus.proxies.Introspect error on 
> > > org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> > > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: 
> > > Message recipient disconnected from message bus without replying
> > > 
> > > Followed by a backtrace, the relevant part appears to be:
> > > File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 22, in 
> > > 
> > >DOMAINS = qui.models.qubes.DomainManager()
> > > 
> > > Any advice would be appreciated, since with no icons, I'm also not 
> > > appearing to get notifications for devices and VM actions.
> > > 
> > > Best,
> > > Daniel
> > 
> > Interesting discovery: this problem arose as a result of setting 
> > qrexec_timeout on an arbitrary VM to a value larger than an INT32. So the 
> > moral of the story: Don't try to set qrexec_timeout too high!
> > 
> > Daniel
> 
> Hello,
> 
> I am experiencing the same problem with the final version of 4.0 but I did 
> not change a setting of qrexec_timeout. The device tray icon disappeared 
> suddenly.
> 
> I am getting tons of "GTK error" when trying to run manually via "python3 
> -mqui.tray.devices"?
> 
> So far I haven't been able to get the devices tray appear again but I can 
> attach devices via command line.
> 
> Anyone having the same problem?

no,  weird.  have you tried to use qubes-manager at all?

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/021da6c5-57ab-4d9a-8794-cf878cd22b65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-04-19 Thread 'Антон Чехов' via qubes-users
On Saturday, February 17, 2018 at 1:06:16 AM UTC+1, Daniel Moerner wrote:
> On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner wrote:
> > Hi all,
> > 
> > After a recent reboot, the devices and VM tray icons no longer are 
> > appearing on boot in Xfce. I have no idea what might have caused this. 
> > There were no dom0 updates in the meantime. If I try to manually run them, 
> > e.g., python3 -mqui.tray.devices, I get the following:
> > 
> > ERROR:dbus.proxies.Introspect error on 
> > org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
> > recipient disconnected from message bus without replying
> > 
> > Followed by a backtrace, the relevant part appears to be:
> > File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 22, in 
> > 
> >DOMAINS = qui.models.qubes.DomainManager()
> > 
> > Any advice would be appreciated, since with no icons, I'm also not 
> > appearing to get notifications for devices and VM actions.
> > 
> > Best,
> > Daniel
> 
> Interesting discovery: this problem arose as a result of setting 
> qrexec_timeout on an arbitrary VM to a value larger than an INT32. So the 
> moral of the story: Don't try to set qrexec_timeout too high!
> 
> Daniel

Hello,

I am experiencing the same problem with the final version of 4.0 but I did not 
change a setting of qrexec_timeout. The device tray icon disappeared suddenly.

I am getting tons of "GTK error" when trying to run manually via "python3 
-mqui.tray.devices"?

So far I haven't been able to get the devices tray appear again but I can 
attach devices via command line.

Anyone having the same problem?

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/8fc3b326-1b29-4cc7-9272-4b56da7c804d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: R4.0 rc4: Devices and VM tray icons disappeared

2018-02-16 Thread Daniel Moerner
On Friday, February 16, 2018 at 6:48:22 PM UTC-5, Daniel Moerner wrote:
> Hi all,
> 
> After a recent reboot, the devices and VM tray icons no longer are appearing 
> on boot in Xfce. I have no idea what might have caused this. There were no 
> dom0 updates in the meantime. If I try to manually run them, e.g., python3 
> -mqui.tray.devices, I get the following:
> 
> ERROR:dbus.proxies.Introspect error on 
> org.qubes.DomainManager1:/org/qubes/DomainManager1: 
> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
> recipient disconnected from message bus without replying
> 
> Followed by a backtrace, the relevant part appears to be:
> File "/usr/lib/python3.5/site-packages/qui/tray/devices.py", line 22, in 
> 
>DOMAINS = qui.models.qubes.DomainManager()
> 
> Any advice would be appreciated, since with no icons, I'm also not appearing 
> to get notifications for devices and VM actions.
> 
> Best,
> Daniel

Interesting discovery: this problem arose as a result of setting qrexec_timeout 
on an arbitrary VM to a value larger than an INT32. So the moral of the story: 
Don't try to set qrexec_timeout too high!

Daniel

-- 
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 qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/1f5e2f2a-3c6f-4798-beb5-21e1d7e596d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.