On Wed, 2013-09-18 at 11:34 -0500, Richard Shaw wrote:
> Ok, not complaining to anyone on this thread, but I would love to see
> the rational for per application printer discovery! That makes
> absolutely no sense to me.
It's not that it's per-application -- rather, it's done in the client
libra
On Thu, Sep 19, 2013 at 6:06 AM, Tim Waugh wrote:
> On Wed, 2013-09-18 at 11:34 -0500, Richard Shaw wrote:
> > Ok, not complaining to anyone on this thread, but I would love to see
> > the rational for per application printer discovery! That makes
> > absolutely no sense to me.
>
> It's not that
I posted an issue I was having booting a new install of F19 on my Samsung
netbook. It seems that my system cannot find the disks by UUID for some
reason. The way I fixed this before was to edit grub to use the device name
/dev/sda5 (which is /boot) instead of UUID. Some people replied that I
I have a HDHomeRun (network based TV tuner) on my home network. In order to
get it to work I had to add the following to my iptables config:
-A INPUT -m state --state NEW -m udp -p udp --sport 5002 -j ACCEPT
-A INPUT -m state --state NEW -m udp -p udp --sport 5004 -j ACCEPT
-A INPUT -m state --sta
I believe the syntax is: firewall-cmd --permanent --add-port 5002/udp
From: users-boun...@lists.fedoraproject.org
[users-boun...@lists.fedoraproject.org] On Behalf Of Richard Shaw
[hobbes1...@gmail.com]
Sent: Thursday, September 19, 2013 7:40 AM
To: Comm
I have installed a F19 on an old laptop with Nvidia G72M (Quadro NVS
110M/ Geforce Go 7300).
Installed Gnome 3 but when I want to see all application instead of more
frequent, nothing appears.I noticed also some artifacts on some windows.
No problem when user starts LXDE instead of Gnome 3.
Tnx
On Thu, Sep 19, 2013 at 9:46 AM, Shelby, James wrote:
> I believe the syntax is: firewall-cmd --permanent --add-port 5002/udp
>From what I can tell that's the equivalent of --dport, not --sport...
Otherwise it would work from firewall-config.
Thanks,
Richard
--
users mailing list
users@lists.
I hate top posting, but I have more information that Ihope might help. I tried
the steps in:
https://fedoraproject.org/wiki/GRUB_2#Encountering_the_dreaded_GRUB_2_boot_prompt
and maybe got closer to a good boot, but I'm still seeing that at some step in
the boot process, it wants to find the pa
On 09/19/2013 06:30 AM, Mark Haney issued this missive:
I posted an issue I was having booting a new install of F19 on my
Samsung netbook. It seems that my system cannot find the disks by UUID
for some reason. The way I fixed this before was to edit grub to use
the device name /dev/sda5 (which
I hate top posting, but I have more information that Ihope might help. I tried
the steps in:
https://fedoraproject.org/wiki/GRUB_2#Encountering_the_dreaded_GRUB_2_boot_prompt
and maybe got closer to a good boot, but I'm still seeing that at some step in
the boot process, it wants to find the
antonio montagnani ha scritto / said the followingil giorno/on
19/09/2013 17:16:
I have installed a F19 on an old laptop with Nvidia G72M (Quadro NVS
110M/ Geforce Go 7300).
Installed Gnome 3 but when I want to see all application instead of more
frequent, nothing appears.I noticed also some
Hi Christophe,
If someone provides newer windows binaries -- which aren't missing
dlls, like the ones at http://teuf.fedorapeople.org/virt-viewer-msi/
-- I will test then.
I gave you links to RPMs containing the missing dlls (rpm2cpio foo.dll
| cpio -id will unpack them on linux) in
https://ww
Hi,
My first tests using virsh from
http://teuf.fedorapeople.org/virt-viewer-msi/ were based on the 64-bit
(x86_64) binaries. I'll try the 32-bit binaries and report on the results.
After having success with a few comands using virsh, I decided to try
virt-viewer.
It reported missing libss
Hi Marc,
C:\Program Files\VirtViewer\bin>virsh -c qemu+tcp://kvmhost/system
error: failed to connect to the hypervisor
error: authentication failed: unsupported authentication type 1
It looks like the windows port can't do SASL auth over TCP. So I changed
libvirtd.conf to allow unauthenticated c
Hi,
My first tests using virsh from
http://teuf.fedorapeople.org/virt-viewer-msi/ were based on the 64-bit
(x86_64) binaries. I'll try the 32-bit binaries and report on the
results.
The 32-bit binaries needed the same DLLs (of course the 32-bit ones) and
gave the same results: virsh works with
Allegedly, on or about 19 September 2013, Mark Haney sent:
> Does this trigger a thought with anyone on what the problem could be?
"failed... queued... timed out..." sounds like hardware trouble... But
it would have been better if you'd not edited the log.
> I know the drive is good since I can
16 matches
Mail list logo