Re: [qubes-users] ERROR: Device attach failed

2018-01-27 Thread beso
On Saturday, January 27, 2018 at 4:33:47 PM UTC+2, awokd wrote:
> On Sat, January 27, 2018 2:20 pm, beso wrote:
> 
> >> On Sat, January 27, 2018 6:31 am, beso wrote:
> >>
> >>> ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [:
> >>> Illegal
> >>> number: stash: printf: I/O error.
> >>> How to solve this problem?
> >>>
> 
> > Sorry,
> 
> No trouble!
> 
> > Qubes - 3.2;
> > Attached device - Samsung M3 Portable 1TB;
> > Command I used to attach to one of my appVm - qvm-usb -a appvm
> > sys-net:3-1;
> 
> I'm assuming the ";" at the end of sys-net:3-1 is a separator and not
> actually part of the command you are entering, right? Has this device
> worked before on your system or is this the first time you are trying it?
> If it was working before, when did it start giving you the error?

Yes, that is separator here. No, it never worked.

-- 
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/2b2e84f6-77f9-4d82-a72e-91e43d6c872a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] ERROR: Device attach failed

2018-01-27 Thread beso
On Saturday, January 27, 2018 at 3:58:35 PM UTC+2, awokd wrote:
> On Sat, January 27, 2018 6:31 am, beso wrote:
> > ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [: Illegal
> > number: stash: printf: I/O error.
> > How to solve this problem?
> 
> Not to sound cranky, but can you review
> https://www.qubes-os.org/mailing-lists/ Discussion list guidelines?
> There's not enough information in your question to be able to answer it.
> For example: Qubes version, type of USB device, speed of USB device,
> command or method you are using to attach it, etc.

Sorry,

Qubes - 3.2;
Attached device - Samsung M3 Portable 1TB;
Command I used to attach to one of my appVm - qvm-usb -a appvm sys-net:3-1;

-- 
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/a7284e2d-3eff-4290-b28e-4746f3978853%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] ERROR: Device attach failed

2018-01-26 Thread beso
ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [: Illegal number: 
stash: printf: I/O error.
How to solve this 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/b0c6b3d2-f849-40d0-8bb9-1273a92ac55c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] No space left

2018-01-25 Thread beso
On Thursday, January 25, 2018 at 4:03:16 PM UTC+2, Yuraeitha wrote:
> On Thursday, January 25, 2018 at 2:32:38 PM UTC+1, beso wrote:
> > On Thursday, January 25, 2018 at 1:13:53 PM UTC+2, donoban wrote:
> > > On 01/24/2018 07:11 PM, beso wrote:
> > > > On Wednesday, January 24, 2018 at 2:47:55 PM UTC+2, donoban wrote:
> > > >> On 01/24/2018 09:34 AM, beso wrote:
> > > >>> On Tuesday, January 23, 2018 at 3:53:15 PM UTC+2, steve.coleman wrote:
> > > >>>> On 01/23/2018 04:55 AM, beso wrote:
> > > >>>>> Something is eating free space in my system. It step by step 
> > > >>>>> decreasing. I haven't found any good solution for that.
> > > >>>>>
> > > >>>>
> > > >>>> This command should give you a clue as to where the space is going:
> > > >>>>
> > > >>>> $ sudo du -h / | sort  -g | tail -100
> > > >>>>
> > > >>
> > > >> Try reversing the sort output:
> > > >>
> > > >> sudo du -h / | sort  -g -r | tail -100
> > > > 
> > > > sudo du -h / | sort -g -r | tail -100
> > > > du: `/proc/5947/task/5947/fd/4' ei saa kasutada: No such file or 
> > > > directory
> > > > du: `/proc/5947/task/5947/fdinfo/4' ei saa kasutada: No such file or 
> > > > directory
> > > > du: `/proc/5947/fd/3' ei saa kasutada: No such file or directory
> > > > du: `/proc/5947/fdinfo/3' ei saa kasutada: No such file or directory
> > > > 0   /proc/109/ns
> > > > 0   /proc/109/net/stat
> > > 
> > > Ouch, try better this way:
> > > 
> > > cd /
> > > sudo du -sh *
> > > 
> > > You should see each dir on / and its disk usage
> > > 
> > > then cd what you think it's using more than expected and du -sh * again.
> > 
> > Thank you for the answer. Actually I know generally that some of my appvm-s 
> > are quite big and there is quite few room(about 6G). Thing I don't 
> > understand and would like to know is that this free room is disappearing 
> > sometimes(not always) "in my eyes"(free space checker shows me in real time 
> > :-))
> 
> It may be, "possible" that discard / fstrim only partially works? For example 
> if it works in dom0, but not in some, or all your VM's, then numbers may 
> change, but they won't be exact. This too means some VM's can grow larger 
> than the actual files they hold, i.e. if you once had more files in, but no 
> longer have that much now. If it can't shrink back down, then it'll stay 
> large. Does your VM's shrink back down too? 
> 
> I modified donoban's command slightly, it's a good command and it's a good 
> advice he gives. The only reason I modified it to AppVM folder, is because 
> it's a likely source for your disk changes, so it's a good place to start 
> looking too in addition to overall root at "/". 
> 
> Try:
> 
> in dom0: cd /var/lib/qubes/appvms 
> in dom0: sudo du -sh *
> 
> It'll show all your AppVM's and their total disk usage, it's way simpler than 
> the "qvm-ls --format disk" dommand I gave you earlier. 
> 
> It's recommendable that you save these logs over some days, i.e. sudo nano 
> and copy-paste into it, and save with ctrl+x and follow the guideline to 
> save. 
> 
> By keeping these logs, you can easily narrow down where it changes in an 
> uncontrollable manner when compared. You can even post them here if you 
> prefer, or cross out the VM names with numbers instead if you prefer privacy 
> (just be sure they match numbers between logs). 
> 
> As donoban also said, if you do this properly, you'll be able to narrow down 
> the possible culprit. Run the commands once a day over a few days, on both 
> "/" and "/var/lib/qubes/appvms", and keep one log for each path, for some 
> days.
> 
> This way, you'll quickly narrow it down with minimal effort once a day, only 
> requiring a bit of patience and a few quick commands daily, max 3-4 minutes.


Actually I haven't trimmed dom0 itself only templates/appvms/standalones. Is 
this link https://www.qubes-os.org/doc/disk-trim/ correctway to do that?

-- 
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/2d249d6b-852d-4a08-94a0-1026703f191f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: USB3 attach problem

2018-01-25 Thread beso
On Thursday, January 25, 2018 at 1:44:37 PM UTC+2, Ilpo Järvinen wrote:
> On Wed, 24 Jan 2018, beso wrote:
> 
> > On Thursday, January 25, 2018 at 5:01:00 AM UTC+2, cooloutac wrote:
> > > On Wednesday, January 24, 2018 at 2:35:14 PM UTC-5, beso wrote:
> > > > ERROR: Device attach failed: USB SuperSpeed require kernel >= 
> > > > 4.13/usr/lib/qubes/usb-import: line 71: printf: write error: Invalid 
> > > > argument
> > > 
> > > I don't have this issue on 3.2.  are you using 4.0?
> > 
> > No, I use 3.2.
> 
> Qubes usb-proxy recently gained support for USB3 [1] but perhaps it might 
> need to check that the kernel is new enough to support it?
> 
> R3.2 stable repo only has 4.9 series kernel in stable repo, whereas 
> testing has new enough kernel.
> 
> Perhaps these different experiences you see come from different kernel / 
> usb-proxy versions installed?
> 
> -- 
>  i.
> 
> 
> [1] 
> https://github.com/QubesOS/qubes-app-linux-usb-proxy/commit/5f94e1064fd5946f127e1257062756be75f92f99

What kernel it shoud be? Unstable repo has also 4.9 kernels.

-- 
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/97cc7f91-c04c-4e47-9e11-be05cde20b75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] No space left

2018-01-25 Thread beso
On Thursday, January 25, 2018 at 1:13:53 PM UTC+2, donoban wrote:
> On 01/24/2018 07:11 PM, beso wrote:
> > On Wednesday, January 24, 2018 at 2:47:55 PM UTC+2, donoban wrote:
> >> On 01/24/2018 09:34 AM, beso wrote:
> >>> On Tuesday, January 23, 2018 at 3:53:15 PM UTC+2, steve.coleman wrote:
> >>>> On 01/23/2018 04:55 AM, beso wrote:
> >>>>> Something is eating free space in my system. It step by step 
> >>>>> decreasing. I haven't found any good solution for that.
> >>>>>
> >>>>
> >>>> This command should give you a clue as to where the space is going:
> >>>>
> >>>> $ sudo du -h / | sort  -g | tail -100
> >>>>
> >>
> >> Try reversing the sort output:
> >>
> >> sudo du -h / | sort  -g -r | tail -100
> > 
> > sudo du -h / | sort -g -r | tail -100
> > du: `/proc/5947/task/5947/fd/4' ei saa kasutada: No such file or directory
> > du: `/proc/5947/task/5947/fdinfo/4' ei saa kasutada: No such file or 
> > directory
> > du: `/proc/5947/fd/3' ei saa kasutada: No such file or directory
> > du: `/proc/5947/fdinfo/3' ei saa kasutada: No such file or directory
> > 0   /proc/109/ns
> > 0   /proc/109/net/stat
> 
> Ouch, try better this way:
> 
> cd /
> sudo du -sh *
> 
> You should see each dir on / and its disk usage
> 
> then cd what you think it's using more than expected and du -sh * again.

Thank you for the answer. Actually I know generally that some of my appvm-s are 
quite big and there is quite few room(about 6G). Thing I don't understand and 
would like to know is that this free room is disappearing sometimes(not always) 
"in my eyes"(free space checker shows me in real time :-))

-- 
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/43c73ab1-74de-4872-ae7c-bb58cf9fd216%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: No space left

2018-01-24 Thread beso
On Thursday, January 25, 2018 at 2:12:25 AM UTC+2, Yuraeitha wrote:
> On Tuesday, January 23, 2018 at 10:55:15 AM UTC+1, beso wrote:
> > Something is eating free space in my system. It step by step decreasing. I 
> > haven't found any good solution for that.
> 
> I forgot to add, before you right click on the /rw folder of any VM you might 
> suspect to have space issues, make sure first that invisible folders and 
> files are shown, otherwise they won't be counted in the size calculation. In 
> fedora templates, the normal files window manager, simply just hold Ctrl, and 
> then type "H" once. Then all hidden files should be shown in that folder, and 
> all sub-folders, and a more accurate measure of the actual used size will 
> show.
> 
> For example Firefox's hidden folder in /home is usually use several 100MB's, 
> and it can make a difference in your size comparison. Thunderbird can also be 
> quite big, i.e. my Thunderbird hidden folder in /home is several GB's in 
> size. 
> 
> Keep in mind that /rw (read / write) folder, is where your /home folder is, 
> among other folders, which an AppVM needs to have write access to.

Thank for the answer. Actually I didn't understand "qvm-ls --format disk" 
command. So I couldn't compare them. I trimmed again all my appvm-s, I got back 
about 5G. 
One strange thing for me - in case I start some appvm, free space is increasing 
about 500MB. It is different every time.
So its increasing and then starts decreasing. Sometimes this decreasing stops 
but sometime it goes to 0.  

-- 
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/4f63b4bd-2f28-4999-8a3a-4585ef040fdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: USB3 attach problem

2018-01-24 Thread beso
On Thursday, January 25, 2018 at 5:01:00 AM UTC+2, cooloutac wrote:
> On Wednesday, January 24, 2018 at 2:35:14 PM UTC-5, beso wrote:
> > ERROR: Device attach failed: USB SuperSpeed require kernel >= 
> > 4.13/usr/lib/qubes/usb-import: line 71: printf: write error: Invalid 
> > argument
> 
> I don't have this issue on 3.2.  are you using 4.0?

No, I use 3.2.

-- 
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/23b44686-4fb8-45eb-b4d6-61647dc6825c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] USB3 attach problem

2018-01-24 Thread beso
ERROR: Device attach failed: USB SuperSpeed require kernel >= 
4.13/usr/lib/qubes/usb-import: line 71: printf: write error: Invalid argument

-- 
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/5228e1b7-7bd2-4b1d-ab8a-1f3afe5cdd97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] No space left

2018-01-24 Thread beso
On Wednesday, January 24, 2018 at 2:47:55 PM UTC+2, donoban wrote:
> On 01/24/2018 09:34 AM, beso wrote:
> > On Tuesday, January 23, 2018 at 3:53:15 PM UTC+2, steve.coleman wrote:
> >> On 01/23/2018 04:55 AM, beso wrote:
> >>> Something is eating free space in my system. It step by step decreasing. 
> >>> I haven't found any good solution for that.
> >>>
> >>
> >> This command should give you a clue as to where the space is going:
> >>
> >> $ sudo du -h / | sort  -g | tail -100
> >>
> 
> Try reversing the sort output:
> 
> sudo du -h / | sort  -g -r | tail -100

sudo du -h / | sort -g -r | tail -100
du: `/proc/5947/task/5947/fd/4' ei saa kasutada: No such file or directory
du: `/proc/5947/task/5947/fdinfo/4' ei saa kasutada: No such file or directory
du: `/proc/5947/fd/3' ei saa kasutada: No such file or directory
du: `/proc/5947/fdinfo/3' ei saa kasutada: No such file or directory
0   /proc/109/ns
0   /proc/109/net/stat
0   /proc/109/net/netfilter
0   /proc/109/net/dev_snmp6
0   /proc/109/net
0   /proc/109/map_files
0   /proc/109/fdinfo
0   /proc/109/fd
0   /proc/109/attr
0   /proc/109
0   /proc/108/task/108/ns
0   /proc/108/task/108/net/stat
0   /proc/108/task/108/net/netfilter
0   /proc/108/task/108/net/dev_snmp6
0   /proc/108/task/108/net
0   /proc/108/task/108/fdinfo
0   /proc/108/task/108/fd
0   /proc/108/task/108/attr
0   /proc/108/task/108
0   /proc/108/task
0   /proc/108/ns
0   /proc/108/net/stat
0   /proc/108/net/netfilter
0   /proc/108/net/dev_snmp6
0   /proc/108/net
0   /proc/108/map_files
0   /proc/108/fdinfo
0   /proc/108/fd
0   /proc/108/attr
0   /proc/108
0   /proc/106/task/106/ns
0   /proc/106/task/106/net/stat
0   /proc/106/task/106/net/netfilter
0   /proc/106/task/106/net/dev_snmp6
0   /proc/106/task/106/net
0   /proc/106/task/106/fdinfo
0   /proc/106/task/106/fd
0   /proc/106/task/106/attr
0   /proc/106/task/106
0   /proc/106/task
0   /proc/106/ns
0   /proc/106/net/stat
0   /proc/106/net/netfilter
0   /proc/106/net/dev_snmp6
0   /proc/106/net
0   /proc/106/map_files
0   /proc/106/fdinfo
0   /proc/106/fd
0   /proc/106/attr
0   /proc/106
0   /proc/105/task/105/ns
0   /proc/105/task/105/net/stat
0   /proc/105/task/105/net/netfilter
0   /proc/105/task/105/net/dev_snmp6
0   /proc/105/task/105/net
0   /proc/105/task/105/fdinfo
0   /proc/105/task/105/fd
0   /proc/105/task/105/attr
0   /proc/105/task/105
0   /proc/105/task
0   /proc/105/ns
0   /proc/105/net/stat
0   /proc/105/net/netfilter
0   /proc/105/net/dev_snmp6
0   /proc/105/net
0   /proc/105/map_files
0   /proc/105/fdinfo
0   /proc/105/fd
0   /proc/105/attr
0   /proc/105
0   /proc/10
0   /proc/1
0   /proc
0   /dev/xen
0   /dev/vfio
0   /dev/snd/by-path
0   /dev/snd
0   /dev/raw
0   /dev/qubes_dom0
0   /dev/pts
0   /dev/net
0   /dev/mqueue
0   /dev/mapper
0   /dev/lightnvm
0   /dev/input/by-path
0   /dev/input
0   /dev/dri
0   /dev/disk/by-uuid
0   /dev/disk/by-partuuid
0   /dev/disk/by-partlabel
0   /dev/disk/by-id
0   /dev/disk
0   /dev/cpu/3
0   /dev/cpu/2
0   /dev/cpu/1
0   /dev/cpu/0
0   /dev/cpu
0   /dev/char
0   /dev/bsg
0   /dev/block


-- 
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/00343d00-2601-4409-8c88-7b5da1444bdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] No space left

2018-01-24 Thread beso
On Tuesday, January 23, 2018 at 3:53:15 PM UTC+2, steve.coleman wrote:
> On 01/23/2018 04:55 AM, beso wrote:
> > Something is eating free space in my system. It step by step decreasing. I 
> > haven't found any good solution for that.
> > 
> 
> This command should give you a clue as to where the space is going:
> 
> $ sudo du -h / | sort  -g | tail -100
> 
> Once you know where the space is going, its just a matter of what is 
> putting it all there.

[x@dom0 /]$ sudo du -h / | sort -g | tail -100
du: `/proc/17545/task/17545/fd/4' ei saa kasutada: No such file or directory
du: `/proc/17545/task/17545/fdinfo/4' ei saa kasutada: No such file or directory
du: `/proc/17545/fd/3' ei saa kasutada: No such file or directory
du: `/proc/17545/fdinfo/3' ei saa kasutada: No such file or directory
928K/usr/lib/modules/4.9.35-20.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K
/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K
/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K/usr/share/icons/Adwaita/16x16/status
928K/usr/share/icons/Adwaita/24x24/status
928K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
932K
/usr/lib/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/usr/lib/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
932K
/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
932K
/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
932K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
932K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
936K/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/crypto
936K
/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
936K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/crypto
936K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
940K/usr/lib64/python3.4/email
940K
/usr/lib/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
944K/usr/lib/firmware/ath6k
944K/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/isdn/hisax
944K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/build/include/media
944K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/build/scripts/gcc-plugins
944K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/build/include/media
944K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/build/scripts/gcc-plugins
944K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/build/include/media
944K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/build/scripts/gcc-plugins
944K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/isdn/hisax
948K/usr/lib/modules/4.

Re: [qubes-users] No space left

2018-01-24 Thread beso
On Tuesday, January 23, 2018 at 3:53:15 PM UTC+2, steve.coleman wrote:
> On 01/23/2018 04:55 AM, beso wrote:
> > Something is eating free space in my system. It step by step decreasing. I 
> > haven't found any good solution for that.
> > 
> 
> This command should give you a clue as to where the space is going:
> 
> $ sudo du -h / | sort  -g | tail -100
> 
> Once you know where the space is going, its just a matter of what is 
> putting it all there.

[x@dom0 /]$ sudo du -h / | sort -g | tail -100
du: `/proc/17545/task/17545/fd/4' ei saa kasutada: No such file or directory
du: `/proc/17545/task/17545/fdinfo/4' ei saa kasutada: No such file or directory
du: `/proc/17545/fd/3' ei saa kasutada: No such file or directory
du: `/proc/17545/fdinfo/3' ei saa kasutada: No such file or directory
928K/usr/lib/modules/4.9.35-20.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K
/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K
/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K/usr/share/icons/Adwaita/16x16/status
928K/usr/share/icons/Adwaita/24x24/status
928K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
928K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/intersil
928K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/sound/pci/echoaudio
932K
/usr/lib/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/usr/lib/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
932K
/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
932K
/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
932K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
932K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
932K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/input/touchscreen
936K/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/crypto
936K
/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
936K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/crypto
936K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/marvell
940K/usr/lib64/python3.4/email
940K
/usr/lib/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/usr/lib/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
940K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/net/wireless/ath/ath9k
944K/usr/lib/firmware/ath6k
944K/usr/lib/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/isdn/hisax
944K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/build/include/media
944K
/var/lib/qubes/vm-kernels/4.9.35-20/modules/4.9.35-20.pvops.qubes.x86_64/build/scripts/gcc-plugins
944K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/build/include/media
944K
/var/lib/qubes/vm-kernels/4.9.45-21/modules/4.9.45-21.pvops.qubes.x86_64/build/scripts/gcc-plugins
944K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/build/include/media
944K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/build/scripts/gcc-plugins
944K
/var/lib/qubes/vm-kernels/4.9.56-21/modules/4.9.56-21.pvops.qubes.x86_64/kernel/drivers/isdn/hisax
948K/usr/lib/modules/4.

[qubes-users] No space left

2018-01-23 Thread beso
Something is eating free space in my system. It step by step decreasing. I 
haven't found any good solution for that. 

-- 
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/7f0a9529-a25c-4644-9a77-e77c539c4f54%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: XFCE Settings menu gone

2018-01-20 Thread beso
I have 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/39a1d83f-11c6-433f-9c1e-20abbdbf7276%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Upgrade Fedora-24 template to Fedora-25

2017-12-03 Thread beso
"Error: Error downloading packages:
  Cannot download libdvdcss-1.4.0-2.fc25.x86_64.rpm: All mirrors were tried"

How to solve this issue?

-- 
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/5dceae6e-e1a5-402a-9c2a-e6a1f422e303%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Hibernate Lenovo X1

2017-12-03 Thread beso
"systemctl hibernate:
Failed to execute operation. Sleep verb not supported."

How to solve this issue?

-- 
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/1d9c5ee6-d8a4-4b79-a5af-d3b04c7d5836%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Mobile broadband-not enabled

2017-11-27 Thread beso
I'll try that. Thanks!

-- 
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/4f7e901e-65f6-4964-9960-78c20918cbd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Mobile broadband-not enabled

2017-11-24 Thread beso
On Thursday, November 23, 2017 at 1:50:53 AM UTC+2, Yuraeitha wrote:
> On Wednesday, November 22, 2017 at 11:13:35 PM UTC, beso wrote:
> > On Thursday, November 23, 2017 at 1:07:28 AM UTC+2, Yuraeitha wrote:
> > > On Wednesday, November 22, 2017 at 10:49:46 PM UTC, beso wrote:
> > > > On Thursday, November 23, 2017 at 12:37:59 AM UTC+2, Yuraeitha wrote:
> > > > > On Wednesday, November 22, 2017 at 10:03:22 PM UTC, beso wrote:
> > > > > > On Wednesday, November 22, 2017 at 11:49:16 PM UTC+2, Yuraeitha 
> > > > > > wrote:
> > > > > > > On Wednesday, November 22, 2017 at 9:37:38 PM UTC, beso wrote:
> > > > > > > > On Wednesday, November 22, 2017 at 11:22:47 PM UTC+2, Yuraeitha 
> > > > > > > > wrote:
> > > > > > > > > On Wednesday, November 22, 2017 at 9:11:18 PM UTC, beso wrote:
> > > > > > > > > > On Wednesday, November 22, 2017 at 5:48:43 PM UTC+2, beso 
> > > > > > > > > > wrote:
> > > > > > > > > > > On Wednesday, November 22, 2017 at 3:00:41 PM UTC+2, beso 
> > > > > > > > > > > wrote:
> > > > > > > > > > > > On Monday, October 2, 2017 at 2:06:38 PM UTC+3, beso 
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > On Monday, October 2, 2017 at 12:01:41 AM UTC+3, 
> > > > > > > > > > > > > One7two99 wrote:
> > > > > > > > > > > > > > Hello Beso,
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > > Mobile Broadband is enabled in 
> > > > > > > > > > > > > > > NetworkManager Applet. 
> > > > > > > > > > > > > > > I can create new Mobile Broadband 
> > > > > > > > > > > > > > > connection but it keeps connecting 
> > > > > > > > > > > > > > > and nothing else
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > >  I am using mobile broadband within Qubes and am 
> > > > > > > > > > > > > > happy to help, but honestly your question/problem 
> > > > > > > > > > > > > > is to unqualified. 
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > - what version of Qubes are you running?
> > > > > > > > > > > > > > - what modell of mobile broadband card are you 
> > > > > > > > > > > > > > using? 
> > > > > > > > > > > > > > - how is the broadband card connected? Probably as 
> > > > > > > > > > > > > > an internal USB device. 
> > > > > > > > > > > > > > - are you using sys-usb to connect the card to your 
> > > > > > > > > > > > > > sys-net VM? Or are you passing through the whole 
> > > > > > > > > > > > > > USB controller?
> > > > > > > > > > > > > > - have you tried to boot up a Fedora live Linux and 
> > > > > > > > > > > > > > check if your mobile broadband is working there?
> > > > > > > > > > > > > > - what does "keeps connecting" means?
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > My suggestion:
> > > > > > > > > > > > > > Try to get the mobile broadband card working 
> > > > > > > > > > > > > > without Qubes (Linux Live Boot from USB-Stick).
> > > > > > > > > > > > > > If you got it working try to make it work in Qubes.
> > > > > > > > > > > > > > 
> > > > > > > > > > > > > > [799]
> > > > > > > > > > > > > 
> > > > > > > > > > > > > - Laptop is ThinkPad X1 Carbon 4th gen.
> > > > > > > > > > > > > - Qubes release 3.2(R3.2)
> > > > > >

Re: [qubes-users] Mobile broadband-not enabled

2017-11-22 Thread beso
On Thursday, November 23, 2017 at 1:07:28 AM UTC+2, Yuraeitha wrote:
> On Wednesday, November 22, 2017 at 10:49:46 PM UTC, beso wrote:
> > On Thursday, November 23, 2017 at 12:37:59 AM UTC+2, Yuraeitha wrote:
> > > On Wednesday, November 22, 2017 at 10:03:22 PM UTC, beso wrote:
> > > > On Wednesday, November 22, 2017 at 11:49:16 PM UTC+2, Yuraeitha wrote:
> > > > > On Wednesday, November 22, 2017 at 9:37:38 PM UTC, beso wrote:
> > > > > > On Wednesday, November 22, 2017 at 11:22:47 PM UTC+2, Yuraeitha 
> > > > > > wrote:
> > > > > > > On Wednesday, November 22, 2017 at 9:11:18 PM UTC, beso wrote:
> > > > > > > > On Wednesday, November 22, 2017 at 5:48:43 PM UTC+2, beso wrote:
> > > > > > > > > On Wednesday, November 22, 2017 at 3:00:41 PM UTC+2, beso 
> > > > > > > > > wrote:
> > > > > > > > > > On Monday, October 2, 2017 at 2:06:38 PM UTC+3, beso wrote:
> > > > > > > > > > > On Monday, October 2, 2017 at 12:01:41 AM UTC+3, 
> > > > > > > > > > > One7two99 wrote:
> > > > > > > > > > > > Hello Beso,
> > > > > > > > > > > > 
> > > > > > > > > > > > > Mobile Broadband is enabled in 
> > > > > > > > > > > > > NetworkManager Applet. 
> > > > > > > > > > > > > I can create new Mobile Broadband 
> > > > > > > > > > > > > connection but it keeps connecting 
> > > > > > > > > > > > > and nothing else
> > > > > > > > > > > > 
> > > > > > > > > > > >  I am using mobile broadband within Qubes and am happy 
> > > > > > > > > > > > to help, but honestly your question/problem is to 
> > > > > > > > > > > > unqualified. 
> > > > > > > > > > > > 
> > > > > > > > > > > > - what version of Qubes are you running?
> > > > > > > > > > > > - what modell of mobile broadband card are you using? 
> > > > > > > > > > > > - how is the broadband card connected? Probably as an 
> > > > > > > > > > > > internal USB device. 
> > > > > > > > > > > > - are you using sys-usb to connect the card to your 
> > > > > > > > > > > > sys-net VM? Or are you passing through the whole USB 
> > > > > > > > > > > > controller?
> > > > > > > > > > > > - have you tried to boot up a Fedora live Linux and 
> > > > > > > > > > > > check if your mobile broadband is working there?
> > > > > > > > > > > > - what does "keeps connecting" means?
> > > > > > > > > > > > 
> > > > > > > > > > > > My suggestion:
> > > > > > > > > > > > Try to get the mobile broadband card working without 
> > > > > > > > > > > > Qubes (Linux Live Boot from USB-Stick).
> > > > > > > > > > > > If you got it working try to make it work in Qubes.
> > > > > > > > > > > > 
> > > > > > > > > > > > [799]
> > > > > > > > > > > 
> > > > > > > > > > > - Laptop is ThinkPad X1 Carbon 4th gen.
> > > > > > > > > > > - Qubes release 3.2(R3.2)
> > > > > > > > > > > - Previous linux distros worked (ubuntu 16.04)
> > > > > > > > > > > - from qvm-usb I can see that card is: Sierra Wireless 
> > > > > > > > > > > Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7
> > > > > > > > > > > - do I have to attach it somewhere?
> > > > > > > > > > > - As I mentioned I can create new broadband connection 
> > > > > > > > > > > and even select it from applet menu but it keeps 
> > > > > > > > > > > connecting(applet shows "circles" as trying connect).
> > > > > > > > > > > I am trying to make scre

Re: [qubes-users] Mobile broadband-not enabled

2017-11-22 Thread beso
On Thursday, November 23, 2017 at 12:37:59 AM UTC+2, Yuraeitha wrote:
> On Wednesday, November 22, 2017 at 10:03:22 PM UTC, beso wrote:
> > On Wednesday, November 22, 2017 at 11:49:16 PM UTC+2, Yuraeitha wrote:
> > > On Wednesday, November 22, 2017 at 9:37:38 PM UTC, beso wrote:
> > > > On Wednesday, November 22, 2017 at 11:22:47 PM UTC+2, Yuraeitha wrote:
> > > > > On Wednesday, November 22, 2017 at 9:11:18 PM UTC, beso wrote:
> > > > > > On Wednesday, November 22, 2017 at 5:48:43 PM UTC+2, beso wrote:
> > > > > > > On Wednesday, November 22, 2017 at 3:00:41 PM UTC+2, beso wrote:
> > > > > > > > On Monday, October 2, 2017 at 2:06:38 PM UTC+3, beso wrote:
> > > > > > > > > On Monday, October 2, 2017 at 12:01:41 AM UTC+3, One7two99 
> > > > > > > > > wrote:
> > > > > > > > > > Hello Beso,
> > > > > > > > > > 
> > > > > > > > > > > Mobile Broadband is enabled in 
> > > > > > > > > > > NetworkManager Applet. 
> > > > > > > > > > > I can create new Mobile Broadband 
> > > > > > > > > > > connection but it keeps connecting 
> > > > > > > > > > > and nothing else
> > > > > > > > > > 
> > > > > > > > > >  I am using mobile broadband within Qubes and am happy to 
> > > > > > > > > > help, but honestly your question/problem is to unqualified. 
> > > > > > > > > > 
> > > > > > > > > > - what version of Qubes are you running?
> > > > > > > > > > - what modell of mobile broadband card are you using? 
> > > > > > > > > > - how is the broadband card connected? Probably as an 
> > > > > > > > > > internal USB device. 
> > > > > > > > > > - are you using sys-usb to connect the card to your sys-net 
> > > > > > > > > > VM? Or are you passing through the whole USB controller?
> > > > > > > > > > - have you tried to boot up a Fedora live Linux and check 
> > > > > > > > > > if your mobile broadband is working there?
> > > > > > > > > > - what does "keeps connecting" means?
> > > > > > > > > > 
> > > > > > > > > > My suggestion:
> > > > > > > > > > Try to get the mobile broadband card working without Qubes 
> > > > > > > > > > (Linux Live Boot from USB-Stick).
> > > > > > > > > > If you got it working try to make it work in Qubes.
> > > > > > > > > > 
> > > > > > > > > > [799]
> > > > > > > > > 
> > > > > > > > > - Laptop is ThinkPad X1 Carbon 4th gen.
> > > > > > > > > - Qubes release 3.2(R3.2)
> > > > > > > > > - Previous linux distros worked (ubuntu 16.04)
> > > > > > > > > - from qvm-usb I can see that card is: Sierra Wireless 
> > > > > > > > > Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7
> > > > > > > > > - do I have to attach it somewhere?
> > > > > > > > > - As I mentioned I can create new broadband connection and 
> > > > > > > > > even select it from applet menu but it keeps 
> > > > > > > > > connecting(applet shows "circles" as trying connect).
> > > > > > > > > I am trying to make screenshot if it helps
> > > > > > > 
> > > > > > > PS.
> > > > > > > [user@sys-net ~]$ ifconfig
> > > > > > > enp0s1f6: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
> > > > > > > ether 54:ee:75:aa:4d:e3  txqueuelen 1000  (Ethernet)
> > > > > > > RX packets 0  bytes 0 (0.0 B)
> > > > > > > RX errors 0  dropped 0  overruns 0  frame 0
> > > > > > > TX packets 0  bytes 0 (0.0 B)
> > > > > > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > > > > > > device interrupt 26  memory 0xe120-e122  
> > > > > > > 
> > > > > > > lo:

Re: [qubes-users] Mobile broadband-not enabled

2017-11-22 Thread beso
On Wednesday, November 22, 2017 at 11:49:16 PM UTC+2, Yuraeitha wrote:
> On Wednesday, November 22, 2017 at 9:37:38 PM UTC, beso wrote:
> > On Wednesday, November 22, 2017 at 11:22:47 PM UTC+2, Yuraeitha wrote:
> > > On Wednesday, November 22, 2017 at 9:11:18 PM UTC, beso wrote:
> > > > On Wednesday, November 22, 2017 at 5:48:43 PM UTC+2, beso wrote:
> > > > > On Wednesday, November 22, 2017 at 3:00:41 PM UTC+2, beso wrote:
> > > > > > On Monday, October 2, 2017 at 2:06:38 PM UTC+3, beso wrote:
> > > > > > > On Monday, October 2, 2017 at 12:01:41 AM UTC+3, One7two99 wrote:
> > > > > > > > Hello Beso,
> > > > > > > > 
> > > > > > > > > Mobile Broadband is enabled in 
> > > > > > > > > NetworkManager Applet. 
> > > > > > > > > I can create new Mobile Broadband 
> > > > > > > > > connection but it keeps connecting 
> > > > > > > > > and nothing else
> > > > > > > > 
> > > > > > > >  I am using mobile broadband within Qubes and am happy to help, 
> > > > > > > > but honestly your question/problem is to unqualified. 
> > > > > > > > 
> > > > > > > > - what version of Qubes are you running?
> > > > > > > > - what modell of mobile broadband card are you using? 
> > > > > > > > - how is the broadband card connected? Probably as an internal 
> > > > > > > > USB device. 
> > > > > > > > - are you using sys-usb to connect the card to your sys-net VM? 
> > > > > > > > Or are you passing through the whole USB controller?
> > > > > > > > - have you tried to boot up a Fedora live Linux and check if 
> > > > > > > > your mobile broadband is working there?
> > > > > > > > - what does "keeps connecting" means?
> > > > > > > > 
> > > > > > > > My suggestion:
> > > > > > > > Try to get the mobile broadband card working without Qubes 
> > > > > > > > (Linux Live Boot from USB-Stick).
> > > > > > > > If you got it working try to make it work in Qubes.
> > > > > > > > 
> > > > > > > > [799]
> > > > > > > 
> > > > > > > - Laptop is ThinkPad X1 Carbon 4th gen.
> > > > > > > - Qubes release 3.2(R3.2)
> > > > > > > - Previous linux distros worked (ubuntu 16.04)
> > > > > > > - from qvm-usb I can see that card is: Sierra Wireless 
> > > > > > > Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7
> > > > > > > - do I have to attach it somewhere?
> > > > > > > - As I mentioned I can create new broadband connection and even 
> > > > > > > select it from applet menu but it keeps connecting(applet shows 
> > > > > > > "circles" as trying connect).
> > > > > > > I am trying to make screenshot if it helps
> > > > > 
> > > > > PS.
> > > > > [user@sys-net ~]$ ifconfig
> > > > > enp0s1f6: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
> > > > > ether 54:ee:75:aa:4d:e3  txqueuelen 1000  (Ethernet)
> > > > > RX packets 0  bytes 0 (0.0 B)
> > > > > RX errors 0  dropped 0  overruns 0  frame 0
> > > > > TX packets 0  bytes 0 (0.0 B)
> > > > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > > > > device interrupt 26  memory 0xe120-e122  
> > > > > 
> > > > > lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
> > > > > inet 127.0.0.1  netmask 255.0.0.0
> > > > > inet6 ::1  prefixlen 128  scopeid 0x10
> > > > > loop  txqueuelen 1  (Local Loopback)
> > > > > RX packets 636  bytes 74412 (72.6 KiB)
> > > > > RX errors 0  dropped 0  overruns 0  frame 0
> > > > > TX packets 636  bytes 74412 (72.6 KiB)
> > > > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > > > > 
> > > > > vif2.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> > > > > inet 10.137.1.1  netmask 255.255.255.255  br

Re: [qubes-users] Mobile broadband-not enabled

2017-11-22 Thread beso
On Wednesday, November 22, 2017 at 11:22:47 PM UTC+2, Yuraeitha wrote:
> On Wednesday, November 22, 2017 at 9:11:18 PM UTC, beso wrote:
> > On Wednesday, November 22, 2017 at 5:48:43 PM UTC+2, beso wrote:
> > > On Wednesday, November 22, 2017 at 3:00:41 PM UTC+2, beso wrote:
> > > > On Monday, October 2, 2017 at 2:06:38 PM UTC+3, beso wrote:
> > > > > On Monday, October 2, 2017 at 12:01:41 AM UTC+3, One7two99 wrote:
> > > > > > Hello Beso,
> > > > > > 
> > > > > > > Mobile Broadband is enabled in 
> > > > > > > NetworkManager Applet. 
> > > > > > > I can create new Mobile Broadband 
> > > > > > > connection but it keeps connecting 
> > > > > > > and nothing else
> > > > > > 
> > > > > >  I am using mobile broadband within Qubes and am happy to help, but 
> > > > > > honestly your question/problem is to unqualified. 
> > > > > > 
> > > > > > - what version of Qubes are you running?
> > > > > > - what modell of mobile broadband card are you using? 
> > > > > > - how is the broadband card connected? Probably as an internal USB 
> > > > > > device. 
> > > > > > - are you using sys-usb to connect the card to your sys-net VM? Or 
> > > > > > are you passing through the whole USB controller?
> > > > > > - have you tried to boot up a Fedora live Linux and check if your 
> > > > > > mobile broadband is working there?
> > > > > > - what does "keeps connecting" means?
> > > > > > 
> > > > > > My suggestion:
> > > > > > Try to get the mobile broadband card working without Qubes (Linux 
> > > > > > Live Boot from USB-Stick).
> > > > > > If you got it working try to make it work in Qubes.
> > > > > > 
> > > > > > [799]
> > > > > 
> > > > > - Laptop is ThinkPad X1 Carbon 4th gen.
> > > > > - Qubes release 3.2(R3.2)
> > > > > - Previous linux distros worked (ubuntu 16.04)
> > > > > - from qvm-usb I can see that card is: Sierra Wireless Incorporated 
> > > > > Sierra Wireless EM7455 Qualcomm Snapdragon X7
> > > > > - do I have to attach it somewhere?
> > > > > - As I mentioned I can create new broadband connection and even 
> > > > > select it from applet menu but it keeps connecting(applet shows 
> > > > > "circles" as trying connect).
> > > > > I am trying to make screenshot if it helps
> > > 
> > > PS.
> > > [user@sys-net ~]$ ifconfig
> > > enp0s1f6: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
> > > ether 54:ee:75:aa:4d:e3  txqueuelen 1000  (Ethernet)
> > > RX packets 0  bytes 0 (0.0 B)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 0  bytes 0 (0.0 B)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > > device interrupt 26  memory 0xe120-e122  
> > > 
> > > lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
> > > inet 127.0.0.1  netmask 255.0.0.0
> > > inet6 ::1  prefixlen 128  scopeid 0x10
> > > loop  txqueuelen 1  (Local Loopback)
> > > RX packets 636  bytes 74412 (72.6 KiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 636  bytes 74412 (72.6 KiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > > 
> > > vif2.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> > > inet 10.137.1.1  netmask 255.255.255.255  broadcast 0.0.0.0
> > > inet6 fe80::fcff::feff:  prefixlen 64  scopeid 0x20
> > > ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
> > > RX packets 102007  bytes 32168371 (30.6 MiB)
> > > RX errors 0  dropped 0  overruns 0  frame 0
> > > TX packets 228493  bytes 219299357 (209.1 MiB)
> > > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> > > 
> > > wlp0s2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> > > inet 192.168.43.181  netmask 255.255.255.0  broadcast 
> > > 192.168.43.255
> > > inet6 fe80::e6a4:71ff:fe8a:d310  prefixlen 64  scopeid 0x20
> > > ether e4:a4:71:8a:d3:

Re: [qubes-users] Mobile broadband-not enabled

2017-11-22 Thread beso
On Wednesday, November 22, 2017 at 5:48:43 PM UTC+2, beso wrote:
> On Wednesday, November 22, 2017 at 3:00:41 PM UTC+2, beso wrote:
> > On Monday, October 2, 2017 at 2:06:38 PM UTC+3, beso wrote:
> > > On Monday, October 2, 2017 at 12:01:41 AM UTC+3, One7two99 wrote:
> > > > Hello Beso,
> > > > 
> > > > > Mobile Broadband is enabled in 
> > > > > NetworkManager Applet. 
> > > > > I can create new Mobile Broadband 
> > > > > connection but it keeps connecting 
> > > > > and nothing else
> > > > 
> > > >  I am using mobile broadband within Qubes and am happy to help, but 
> > > > honestly your question/problem is to unqualified. 
> > > > 
> > > > - what version of Qubes are you running?
> > > > - what modell of mobile broadband card are you using? 
> > > > - how is the broadband card connected? Probably as an internal USB 
> > > > device. 
> > > > - are you using sys-usb to connect the card to your sys-net VM? Or are 
> > > > you passing through the whole USB controller?
> > > > - have you tried to boot up a Fedora live Linux and check if your 
> > > > mobile broadband is working there?
> > > > - what does "keeps connecting" means?
> > > > 
> > > > My suggestion:
> > > > Try to get the mobile broadband card working without Qubes (Linux Live 
> > > > Boot from USB-Stick).
> > > > If you got it working try to make it work in Qubes.
> > > > 
> > > > [799]
> > > 
> > > - Laptop is ThinkPad X1 Carbon 4th gen.
> > > - Qubes release 3.2(R3.2)
> > > - Previous linux distros worked (ubuntu 16.04)
> > > - from qvm-usb I can see that card is: Sierra Wireless Incorporated 
> > > Sierra Wireless EM7455 Qualcomm Snapdragon X7
> > > - do I have to attach it somewhere?
> > > - As I mentioned I can create new broadband connection and even select it 
> > > from applet menu but it keeps connecting(applet shows "circles" as trying 
> > > connect).
> > > I am trying to make screenshot if it helps
> 
> PS.
> [user@sys-net ~]$ ifconfig
> enp0s1f6: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
> ether 54:ee:75:aa:4d:e3  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 26  memory 0xe120-e122  
> 
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Local Loopback)
> RX packets 636  bytes 74412 (72.6 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 636  bytes 74412 (72.6 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> vif2.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 10.137.1.1  netmask 255.255.255.255  broadcast 0.0.0.0
> inet6 fe80::fcff::feff:  prefixlen 64  scopeid 0x20
> ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
> RX packets 102007  bytes 32168371 (30.6 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 228493  bytes 219299357 (209.1 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> wlp0s2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 192.168.43.181  netmask 255.255.255.0  broadcast 192.168.43.255
> inet6 fe80::e6a4:71ff:fe8a:d310  prefixlen 64  scopeid 0x20
> ether e4:a4:71:8a:d3:10  txqueuelen 1000  (Ethernet)
> RX packets 238240  bytes 225553537 (215.1 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 108834  bytes 37072683 (35.3 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


sudo dmesg:
[ 3847.841147] NetworkManager[6145]: segfault at 38 ip 732046957569 sp 
7ffe0cc871f0 error 4 in libnm-wwan.so[73204695+11000]

-- 
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/c2344c54-07ad-454c-ae2f-93cde7e8756f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Mobile broadband-not enabled

2017-11-22 Thread beso
On Wednesday, November 22, 2017 at 3:00:41 PM UTC+2, beso wrote:
> On Monday, October 2, 2017 at 2:06:38 PM UTC+3, beso wrote:
> > On Monday, October 2, 2017 at 12:01:41 AM UTC+3, One7two99 wrote:
> > > Hello Beso,
> > > 
> > > > Mobile Broadband is enabled in 
> > > > NetworkManager Applet. 
> > > > I can create new Mobile Broadband 
> > > > connection but it keeps connecting 
> > > > and nothing else
> > > 
> > >  I am using mobile broadband within Qubes and am happy to help, but 
> > > honestly your question/problem is to unqualified. 
> > > 
> > > - what version of Qubes are you running?
> > > - what modell of mobile broadband card are you using? 
> > > - how is the broadband card connected? Probably as an internal USB 
> > > device. 
> > > - are you using sys-usb to connect the card to your sys-net VM? Or are 
> > > you passing through the whole USB controller?
> > > - have you tried to boot up a Fedora live Linux and check if your mobile 
> > > broadband is working there?
> > > - what does "keeps connecting" means?
> > > 
> > > My suggestion:
> > > Try to get the mobile broadband card working without Qubes (Linux Live 
> > > Boot from USB-Stick).
> > > If you got it working try to make it work in Qubes.
> > > 
> > > [799]
> > 
> > - Laptop is ThinkPad X1 Carbon 4th gen.
> > - Qubes release 3.2(R3.2)
> > - Previous linux distros worked (ubuntu 16.04)
> > - from qvm-usb I can see that card is: Sierra Wireless Incorporated Sierra 
> > Wireless EM7455 Qualcomm Snapdragon X7
> > - do I have to attach it somewhere?
> > - As I mentioned I can create new broadband connection and even select it 
> > from applet menu but it keeps connecting(applet shows "circles" as trying 
> > connect).
> > I am trying to make screenshot if it helps

PS.
[user@sys-net ~]$ ifconfig
enp0s1f6: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
ether 54:ee:75:aa:4d:e3  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 26  memory 0xe120-e122  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1  (Local Loopback)
RX packets 636  bytes 74412 (72.6 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 636  bytes 74412 (72.6 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vif2.0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 10.137.1.1  netmask 255.255.255.255  broadcast 0.0.0.0
inet6 fe80::fcff::feff:  prefixlen 64  scopeid 0x20
ether fe:ff:ff:ff:ff:ff  txqueuelen 32  (Ethernet)
RX packets 102007  bytes 32168371 (30.6 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 228493  bytes 219299357 (209.1 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp0s2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
inet 192.168.43.181  netmask 255.255.255.0  broadcast 192.168.43.255
inet6 fe80::e6a4:71ff:fe8a:d310  prefixlen 64  scopeid 0x20
ether e4:a4:71:8a:d3:10  txqueuelen 1000  (Ethernet)
RX packets 238240  bytes 225553537 (215.1 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 108834  bytes 37072683 (35.3 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

-- 
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/8bb90d02-af3c-4b14-aef9-f2ca7440089d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Mobile broadband-not enabled

2017-10-02 Thread beso
On Monday, October 2, 2017 at 12:01:41 AM UTC+3, One7two99 wrote:
> Hello Beso,
> 
> > Mobile Broadband is enabled in 
> > NetworkManager Applet. 
> > I can create new Mobile Broadband 
> > connection but it keeps connecting 
> > and nothing else
> 
>  I am using mobile broadband within Qubes and am happy to help, but honestly 
> your question/problem is to unqualified. 
> 
> - what version of Qubes are you running?
> - what modell of mobile broadband card are you using? 
> - how is the broadband card connected? Probably as an internal USB device. 
> - are you using sys-usb to connect the card to your sys-net VM? Or are you 
> passing through the whole USB controller?
> - have you tried to boot up a Fedora live Linux and check if your mobile 
> broadband is working there?
> - what does "keeps connecting" means?
> 
> My suggestion:
> Try to get the mobile broadband card working without Qubes (Linux Live Boot 
> from USB-Stick).
> If you got it working try to make it work in Qubes.
> 
> [799]

- Laptop is ThinkPad X1 Carbon 4th gen.
- Qubes release 3.2(R3.2)
- Previous linux distros worked (ubuntu 16.04)
- from qvm-usb I can see that card is: Sierra Wireless Incorporated Sierra 
Wireless EM7455 Qualcomm Snapdragon X7
- do I have to attach it somewhere?
- As I mentioned I can create new broadband connection and even select it from 
applet menu but it keeps connecting(applet shows "circles" as trying connect).
I am trying to make screenshot if it helps

-- 
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/ba7bf835-18f8-43ef-89a7-2868417967ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Mobile broadband-not enabled

2017-10-01 Thread beso
Mobile Broadband is enabled in NetworkManager Applet. I can create new Mobile 
Broadband connection but it keeps connecting and nothing else. 

-- 
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/7c17df5f-449c-4697-94d4-112bd9eeaa22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.