Re: More UUID madness
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 boot to Windows. That's no guarantee. Windows will quite happily use broken hard drives, and the royally screw up when it hits a faulty part of the drive, then (often) not give any real clue as to why. Years ago, it was only with Linux that I found out I had a faulty drive, and why a Windows PC was inexplicably crashing. Swapping that drive, nothing else, and running with the same drive contents, and it became more reliable than I generally expected from Windows. Even new hard drives die, so newness is no guarantee. They can get zapped by static during handling. And bumping 5 inch drives while they're running, by moving the PC around, easily damages them. The smaller laptop drives seem better at protecting themselves when they're moved about. -- [tim@localhost ~]$ uname -rsvp Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: progress on virt-viewer for windows
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 TLS and TCP (noauth), virt-viewer locks up. Remote-viewer was woking before and continues working. I have not tried alternative authentications schemes for spice, just TLS and the fixed (shared) password. []s, Fernando Lozano -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: [Spice-devel] progress on virt-viewer for windows
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 connections over TCP. It worked! Some time ago, I tried to port cyrus-sasl to mingw (mostly for fun), I remember I was very sadden by their build-sys which would really need some serious love. There are some binary distribution for Windows around, so it must be doable, but not so easily imho. What mechanism would you rely on? Testing all of them can be tedious too. I tried only digest-md5. I guess most people would use either that or Kerberos. Is the "authentication type 1" from the error message a libvirtd authentication type or a SASL one? I was not able to setup "polkit" on the host. It complains about a missing agent. For libvirtd, the auth options are "none", "sasl" and "polkit". When I manage to get "polkit" working for a linux client, I'll try on the windows port. []s, Fernando Lozano -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: progress on virt-viewer for windows
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 libssp-0.dll, so I copied as per previous intructions by Christophe. Now when I try: C:\Program Files\VirtViewer\bin>virt-viewer -c qemu+tls://kvmhost/system guest1 It locks up. No output, no error, no remote-viewer window. :-( As both virsh and remote-viewer were woking now, I kinda expected virt-viewer should work, or at least give an error we could debug. Changing the connection URL to: C:\Program Files\VirtViewer\bin>virt-viewer -c qemu+tcp://kvmhost/system guest1 Which would give an "unsupported authentication type 1" on virsh, but locks up virt-viewer the same way as using TLS. It looks like virt-viewer is locking up *before* connecting to libvirtd to find the remote display config for "guest1". Adding --debug to virt-viewer with tls shows: (virt-viewer.exe:23376): virt-viewer-DEBUG: Insert window 0 00A240A0 (virt-viewer.exe:23376): virt-viewer-DEBUG: fullscreen display 0: 0 (virt-viewer.exe:23376): virt-viewer-DEBUG: connecting ... (virt-viewer.exe:23376): virt-viewer-DEBUG: Opening connection to libvirt with U RI qemu+tls://kvmhost/system (virt-viewer.exe:23376): virt-viewer-DEBUG: Add handle 3 1 03684A90 If I try --debug but using a qemu+tcp URL, I get the same output (with different memory addresses, of course) Attached is another virt-maanger try (using qemu+tls, which should work for libvirt) but with LIBVIRT_DEBUG=debug. This log shows that libvirt has connected and was authenticated (the RPC_TLS_CONTEXT_SESSION_ALLOW entry means that, right?). How strange. So I also attached also a debug log for the qemu+tcp url. Hope this helps making virt-viewer work on windows. []s, Fernando Lozano []s, Fernando Lozano C:\Program Files\VirtViewer\bin>virt-viewer --debug -c qemu+tcp://kvmhost/sys tem guest1 2013-09-19 19:23:09.589+: 22716: info : libvirt version: 1.1.2 2013-09-19 19:23:09.589+: 22716: debug : virLogParseOutputs:1336 : outputs=" 1:file:virt-viewer.log" 2013-09-19 19:23:09.590+: 22716: warning : virLogParseOutputs:1401 : Ignorin g invalid log output setting. 2013-09-19 19:23:09.599+: 22716: debug : virGlobalInit:438 : register driver s 2013-09-19 19:23:09.599+: 22716: debug : virRegisterDriver:764 : driver= 6CDBAA60 name=Test 2013-09-19 19:23:09.600+: 22716: debug : virRegisterDriver:776 : registering Test as driver 0 2013-09-19 19:23:09.600+: 22716: debug : virRegisterNetworkDriver:611 : regi stering Test as network driver 0 2013-09-19 19:23:09.600+: 22716: debug : virRegisterInterfaceDriver:638 : re gistering Test as interface driver 0 2013-09-19 19:23:09.600+: 22716: debug : virRegisterStorageDriver:665 : regi stering Test as storage driver 0 2013-09-19 19:23:09.601+: 22716: debug : virRegisterNodeDeviceDriver:692 : r egistering Test as device driver 0 2013-09-19 19:23:09.601+: 22716: debug : virRegisterSecretDriver:719 : regis tering Test as secret driver 0 2013-09-19 19:23:09.601+: 22716: debug : virRegisterNWFilterDriver:746 : reg istering Test as network filter driver 0 2013-09-19 19:23:09.601+: 22716: debug : virRegisterDriver:764 : driver= 6CDBBF20 name=PHYP 2013-09-19 19:23:09.601+: 22716: debug : virRegisterDriver:776 : registering PHYP as driver 1 2013-09-19 19:23:09.601+: 22716: debug : virRegisterStorageDriver:665 : regi stering PHYP as storage driver 1 2013-09-19 19:23:09.601+: 22716: debug : virRegisterInterfaceDriver:638 : re gistering PHYP as interface driver 1 2013-09-19 19:23:09.602+: 22716: debug : virRegisterDriver:764 : driver= 6CDBC540 name=ESX 2013-09-19 19:23:09.602+: 22716: debug : virRegisterDriver:776 : registering ESX as driver 2 2013-09-19 19:23:09.602+: 22716: debug : virRegisterInterfaceDriver:638 : re gistering ESX as interface driver 2 2013-09-19 19:23:09.602+: 22716: debug : virRegisterNetworkDriver:611 : regi stering ESX as network driver 1 2013-09-19 19:23:09.602+: 22716: debug : virRegisterStorageDriver:665 : regi stering ESX as storage driver 2 2013-09-19 19:23:09.602+: 22716: debug : virRegisterNodeDeviceDriver:692 : r egistering ESX as device driver 1 2013-09-19 19:23:09.602+: 22716: debug : virRegisterSecretDriver:719 : regis tering ESX as secret driver 1 2013-09-19 19:23:09.603+: 22716: debug : virRegisterNWFilterDriver:746 : reg istering ESX as network filter driver 1 2013-09-19 19:23:09.603+: 22716: debug : virRegisterDriver:764 : driver= 6CDBB4A0 name=remote 2013-09-19 19:23:09.603+: 22716: debug : virRegisterDriver:776 : registering remote as driver 3 2013-09-19 19:23:09.603+: 22716: debug : virRegisterNetworkDriver:611 : regi stering remote as network driver 2
progress on virt-viewer for windows
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://www.redhat.com/archives/virt-tools-list/2013-September/msg00037.html, did you try adding these dlls in the place the installer put the other ones to see if this helps? The first missing DLL was libvirt-lxc-0.dll. After I put it on the virt-viewer install dir, I got the error: 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 Nice, there wan't other missing DLLs. :-) It looks like the windows port can't do SASL auth over TCP. So I changed libvirtd.conf to allow unauthenticated connections over TCP. It worked! Quickly changed libvirtd.conf to allow only TLS connections, not to let my host insecure. Then tried again: C:\Program Files\VirtViewer\bin>virsh -c qemu+tls://kvmhost/system It worked!!! Thanks a lot for your help, and I'm eager to try the next release you are about to build. PS: Would it be hard to add SASL support to the windows port? It's much easier to setup than TLS. []s, Fernando Lozano -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: More UUID madness
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 partitions using UUID in
/dev/disk-by-uuid/ or something similar.
Okay, here's something interesting. I think the problem isn't with the boot
process but possibly with the kernel (or kernel module), here's what I'm seeing
when trying to boot either normally or with setting up GRUB2 manually from the
link above:
localhost systemd[1]: Reached Target Basic System
localhost kernel: ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6
frozen
localhost kernel: ata1.00: failed command: READ FPDMA QUEUED
localhost kernel: [135B blob data]
localhost kernel: ata1.00: status: { DRDY }
... filter out what appears to be non-essential messages
localhost systemd-udevd[78]: worker [81]
/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/block/sda timeout; kill
it
... the above line is repeated for each partition on /dev/sda (1 through 7)
localhost systemd[1]: job dev-sda6.start timed out.
localhost systemd[1]: Timed out waiting for device dev-sda6.device.
localhost systemd[1]: Dependency failed for /sysroot.
localhost systemd[1]: Dependency failed for Initrd Root File System.
localhost systemd[1]: Dependency failed for Reload Configuration from the Real
Root.
Does this trigger a thought with anyone on what the problem could be? I know
the drive is good since I can boot to Windows. It seems only GRUB2 is bombing
on that drive for some reason.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Re: F19: Gnome 3 doesn't show full list of activities
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 artifacts on some windows. No problem when user starts LXDE instead of Gnome 3. Tnx forgot to say that laptop is running on nouveau -- Antonio M Skype: amontag52 Linux Fedora F19(Schroedinger's cat) on Acer 5720 http://lugsaronno.altervista.org http://www.campingmonterosa.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: More UUID madness
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 is /boot) instead of UUID.
Uh, you want the UUID of the root filesystem ("/") instead of "/boot".
Some people
replied that I needed to make sure that my system UUID matched what grub
was trying to use. I've attached a copy of the UUIDs (from blkid) and
from /boot/grub2/grub.cfg. I did another fresh install of F19,
reformatted the partitions again and still had the same problem. So I
booted back into my LiveUSB image and pulled the data from blkid and and
grub.cfg. So, what do I do now?
I noticed in the boot params there's a '--fs-uuid' switch, can I remove
that and specify /dev/sda5 instead? I know so little about the newest
boot process that I'm flailing here. Help!
The best tool is "lsblk -f". You should see output like:
NAME FSTYPE LABEL UUID
MOUNTPOINT
sda
├─sda1 ext3 /boot 86f2589e-b5d5-464a-a19f-7a26cec2a6cc /boot
└─sda2 LVM2_mem Z7Lynq-GOOr-GAdZ-yeSt-AleG-2WiQ-T5JBIm
├─VolGroup00-LogVol00
ext3 f07b9552-a738-4e07-9319-150939a5cd42 /
└─VolGroup00-LogVol01
swap e7dbb97c-bc3e-405b-8a3d-31a2edda2a42 [SWAP]
sdb
└─sdb1 ext3 CD-DVD-Images d137c115-1add-45e4-8210-08beca7ab8a5
/media/CD-D
sdc
└─sdc1 ext3 500GB-Drive e88e6570-2f82-495f-9b01-4e19616f8ef2
/media/500G
sr0
Again, you want the UUID of the root filesystem (in my case,
f07b9552-a738-4e07-9319-150939a5cd42).
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
- "OK, so you're a Ph.D. Just don't TOUCH anything!" -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
RE: More UUID madness
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 partitions using UUID in /dev/disk-by-uuid/ or something similar. Why on earth was this even screwed with? It's a joke in every way. In all my research I'm seeing a half dozen ways to either edit files or re-install grub2. I'm not sure trying to boot my system by labels would even work if the UUID is correct and it can't even find that. I mean if it can't find the UUID, how the hell will it find the label? Is there /any/ way at all to just change Grub2 to boot from /dev/sdaX? Or do I just say screw it and stick with Windows only on this netbook? 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 needed to make sure that my system UUID matched what grub was trying to use. I've attached a copy of the UUIDs (from blkid) and from /boot/grub2/grub.cfg. I did another fresh install of F19, reformatted the partitions again and still had the same problem. So I booted back into my LiveUSB image and pulled the data from blkid and and grub.cfg. So, what do I do now? I noticed in the boot params there's a '--fs-uuid' switch, can I remove that and specify /dev/sda5 instead? I know so little about the newest boot process that I'm flailing here. Help! Thanks. Mark -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: firewalld equivalent of iptabled --sport?
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.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
F19: Gnome 3 doesn't show full list of activities
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 -- Antonio M Skype: amontag52 Linux Fedora F19(Schroedinger's cat) on Acer 5720 http://lugsaronno.altervista.org http://www.campingmonterosa.com -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
RE: firewalld equivalent of iptabled --sport?
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: Community support for Fedora users Subject: firewalld equivalent of iptabled --sport? 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 --state NEW -m udp -p udp --sport 65001 -j ACCEPT Which from my limited knowledge of how iptables work, is the opposite of what you usually do for most services (--dport) because in this case the the return port is random. I have not been able to find any setting in firewall-config or in the documentation that mentions source ports, only destination ports. If this is not possible it would appear to be a fairly large flaw in firewalld in general. Thanks, Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
firewalld equivalent of iptabled --sport?
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 --state NEW -m udp -p udp --sport 65001 -j ACCEPT Which from my limited knowledge of how iptables work, is the opposite of what you usually do for most services (--dport) because in this case the the return port is random. I have not been able to find any setting in firewall-config or in the documentation that mentions source ports, only destination ports. If this is not possible it would appear to be a fairly large flaw in firewalld in general. Thanks, Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
More UUID madness
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 needed
to make sure that my system UUID matched what grub was trying to use. I've
attached a copy of the UUIDs (from blkid) and from /boot/grub2/grub.cfg. I did
another fresh install of F19, reformatted the partitions again and still had
the same problem. So I booted back into my LiveUSB image and pulled the data
from blkid and and grub.cfg. So, what do I do now?
I noticed in the boot params there's a '--fs-uuid' switch, can I remove that
and specify /dev/sda5 instead? I know so little about the newest boot process
that I'm flailing here. Help!
Thanks.
Mark
/dev/sda5: LABEL="boot" UUID="f8239c70-5d18-4855-9dfb-b1ccae27fc7a" TYPE="ext4"
/dev/sda6: UUID="f45bec4e-c351-4256-a551-8936bb047856" TYPE="swap"
/dev/sda7: LABEL="root" UUID="6da2b4d5-7278-45f2-add1-06372595f6a9" TYPE="ext4"
/boot/grub2/grub.cfg
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora, with Linux 3.9.5-301.fc19.x86_64' --class fedora --class
gnu-linux --class gnu --class os $menuentry_id_option
'gnulinux-3.9.5-301.fc19.x86_64-advanced-6da2b4d5-7278-45f2-add1-06372595f6a9' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5
--hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 --hint='hd0,msdos5'
f8239c70-5d18-4855-9dfb-b1ccae27fc7a
else
search --no-floppy --fs-uuid --set=root
f8239c70-5d18-4855-9dfb-b1ccae27fc7a
fi
linux /vmlinuz-3.9.5-301.fc19.x86_64
root=UUID=6da2b4d5-7278-45f2-add1-06372595f6a9 ro rd.md=0 rd.lvm=0 rd.dm=0
vconsole.keymap=us rd.luks=0 vconsole.font=latarcyrheb-sun16 rhgb quiet
initrd /initramfs-3.9.5-301.fc19.x86_64.img
}
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Re: Printer discovery broken after "server" upgraded to Fedora 19
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 it's per-application -- rather, it's done in the client > libraries of CUPS (libcups) rather than in the server. > > One reason to do it this way is to avoid needing to run a CUPS server on > the client at all, while still retaining automatic discovery. > Ok, I think I was confusing the gtk3/gtk2 talk in the bug report > > If it's per-application I'm guessing I'll have to do the latter > > because cups-browsed doesn't appear to be available on F18... > > If you're using F-18 clients and want things to work "as before", use > CUPS Browsing. For that you'll need to enable cups-browsed on the server > and configure it to announce printers using the "CUPS" protocol rather > than DNS-SD. That's what's weird... I tried that (as far as I could tell) and it didn't work, but when I restored my conf file and stopped cups-browsed then it started working! I did a diff between the F19 defail cupsd.conf and the existing one from F18 biggest difference seems to be: Browsing On BrowseOrder allow,deny BrowseAllow all BrowseRemoteProtocols CUPS BrowseAddress @LOCAL BrowseLocalProtocols CUPS dnssd But one side effect is when I try to go into the printer properties on the client, there's almost nothing there (in the gnome3 one). I'm also having problems with system-config-printer similar to the "can't add printers" BZ. I was trying to do all this remotely from work yesterday to get my wife printing but I'm home today so if you want to try anything or get information today is the day to do it! Thanks, Richard -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Printer discovery broken after "server" upgraded to Fedora 19
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 libraries of CUPS (libcups) rather than in the server. One reason to do it this way is to avoid needing to run a CUPS server on the client at all, while still retaining automatic discovery. > Is there a way to get dns-sd to work on a system wide basis? Or is it > per application only? I'm not sure what you mean here. > If it's per-application I'm guessing I'll have to do the latter > because cups-browsed doesn't appear to be available on F18... If you're using F-18 clients and want things to work "as before", use CUPS Browsing. For that you'll need to enable cups-browsed on the server and configure it to announce printers using the "CUPS" protocol rather than DNS-SD. Tim. */ signature.asc Description: This is a digitally signed message part -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
