Created attachment 4982 [details]
Picture from Mageia 3 showing "Browse servers" list

Created attachment 4983 [details]
Picture from Mageia 4 showing missing "Browse servers" list

(In reply to Jeff Robins from comment #0)
> Description of problem:
> The "Browse serevers" list doesn't show in system-config-printer 1.4.3 in
> It looks like it may be there and the "Server Settings" window
> just doesn't expand far enough to see it. I have attached screen shots from
> Mageia 3 and 4 to show the difference.

Did you try to resize the window?  
The printer icon at upper left is Window Menu, go to More Actions > Special Window Settings.  There you can go to the Size & Position tab, select Size, select Apply Now in the drop down, make the second, vertical dimension larger, and OK that, for example.  I say "for example" as this makes a change for one instance of the window, only, to test.  I find the Window Menu to be ungainly and making any changes permanent is always a trial and error headache, for me.

CC: (none) => rolfpedersen

(In reply to Rolf Pedersen from comment #3)
> (In reply to Jeff Robins from comment #0)
> > Description of problem:
> > The "Browse serevers" list doesn't show in system-config-printer 1.4.3 in
> > It looks like it may be there and the "Server Settings" window
> > just doesn't expand far enough to see it. I have attached screen shots from
> > Mageia 3 and 4 to show the difference.
> 
> Did you try to resize the window?  
> The printer icon at upper left is Window Menu, go to More Actions > Special
> Window Settings.  There you can go to the Size & Position tab, select Size,
> select Apply Now in the drop down, make the second, vertical dimension
> larger, and OK that, for example.  I say "for example" as this makes a
> change for one instance of the window, only, to test.  I find the Window
> Menu to be ungainly and making any changes permanent is always a trial and
> error headache, for me.

Rolf,

I increased the size of the window as you specified**, but the list does not appear.  The bottom portion of the window is grey with nothing in it.  Probably most revealing though is that the border below the "Preserve job files" option is still missing.  I'm not familiar with how the windows are drawn in this case, but, to me, it looks like the problem isn't the window size.  I think the problem is that the size of the area expanded when one clicks on "Advanced Server Settings" has been set too small.  

I will try and find the appropriate files tonight and see if I can alter the code to fix the issue, but it would help if someone could tell me where to start looking.

Thank you,

Jeff

**Why is the Window Menu hidden in the printer icon?  I would have never thought to check there if you hadn't pointed it out.  Is this the same for the other windows?It does seem very useful though.

Okay.  This is what I have tracked down so far:

1) The problem is the following snippet starting at line 227 from "usr/share/system-config-printer/serversettings.py", which evaluates to False and hides the menu.
         if self.server_settings.has_key(cups.CUPS_SERVER_REMOTE_PRINTERS):
             self.frameBrowseServers.show()
         else:
             self.frameBrowseServers.hide()

2) If we override this and set it to true, then we can see the menu, but the bottom border is still screwed up

3) If we add a printer using the menu, then it adds the line "BrowsePoll <IP or name>" to cupsd.conf, which prints out a very ugly cupsd.conf compared to the one that was there before

4) It should be adding the line to cups-browsed.conf, which is read by a second cups service "cups-browsed.service"

5) Restarting "cups-browsed.service" via systemctl and "restart" doesn't work.  It must be stopped and started ("stop", "start")

A little more information:

1) Kubuntu 13.10 acts the same way.  

2) I had to download the driver for my Epson WF-3540 from Epson's website and it works just fine.

3) Kubunu 13.10 comes with a driver for the WF-3540 and it has the problem.

So, I guess this is an upstream bug.

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

This is still valid in MGA5.

Version: 4 => 5
Whiteboard: (none) => MGA4TOO

On the 25th of July, Phillipem uploaded the following packages to 
Cauldron's core/updates_testing:

    system-config-printer-1.5.7-5.mga6.i586
    system-config-printer-applet-1.5.7-5.mga6.i586
    system-config-printer-udev-1.5.7-5.mga6.i586

    system-config-printer-libs-1.5.7-5.mga6.noarch

    system-config-printer-1.5.7-5.mga6.x86_64
    system-config-printer-applet-1.5.7-5.mga6.x86_64
    system-config-printer-udev-1.5.7-5.mga6.x86_64


@ Anyone reading this:

* If this bug is valid for you in cauldron, then please test whether updating your system-config-printer packages to version 1.5.7-5.mga6 fixes the problem and report back in this bug report.

* If you do not have this bug in cauldron, but you do run cauldron, then please update those packages, too, and report in bug 18367 whether they work as expected.

CC: (none) => makowski.mageia

I was hoping the package would be updated to 1.5.7 in Mageia 5.1, but it hasn't been updated yet.  I have reconfirmed the issue in 1.5.5.

I don't have a Cauldron image.

Hi Jeff,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

It's still missing in MGA6, but the box that made it seem like it should have been there is missing too.  It looks like it has been permanently removed, so I guess one has to use manually edit the "cups-browsed.conf" file to set this up now.  The CUPS web interface didn't have a place to set the browsed servers and only edits "cupsd.conf".

There is a menu item "View"->"Discovered Printers", but I see no place to configure which servers are browsed.

Created attachment 10092 [details]
MGA6 version of the menu

(In reply to Jeff Robins from comment #12)
> It's still missing in MGA6, but the box that made it seem like it should
> have been there is missing too.  It looks like it has been permanently
> removed

You already said in comment 3 that this is likely an upstream bug. 

Now this sounds like they decided to not fix it (or that they consider this to be a feature instead of a bug).

We don't override upstream decisions, so closing as WONTFIX

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED
Keywords: NEEDINFO => UPSTREAM