*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
Bug still there as of 8-21-9 for Jaunty 9.04. Using the IP of the
shared machine would not work for me.
ANOTHER WORKAROUND: Ubuntu Main Menu Places
-Find the PC with the shared printer, and go into the
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
Bug still there as of 8-21-9 for Jaunty 9.04. Using the IP of the
shared machine would not work for me.
ANOTHER WORKAROUND: Ubuntu Main Menu Places
-Find the PC with the shared printer, and go into the
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
I think the problem is solved: I updated the system with third party
canonical repositories on, and the bug disappeared. Now I can see the
windows printers.
--
Jaunty 9.04 Blind to XP's Shared Network
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
I don't even have the printing selection anymore!! And I never had the
windows printer via Samba.. I am going to reload 9.04 completely and wait..
I have spent much too much time on this already. Ubuntu is
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
I do not know where to post this so forgive me if it is in the wrong place. I
had a almost perfect printer system on a winxp machine accessed by my Ubuntu
8.4 when i upgraded to 9.04 I can not print. I can
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
The Motorman - see post above - should cure your problem: Workaround found,
but bug remains:
I used my Windows box IP address instead of Browsing for the printer. This
permitted me to go to the next steps
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
Thanks, I tried the IP address did not make any difference cannot find
printer..The browse doesn't help either, it doesn't browse it seems to
want me to enter the location.
My printer selection doesn't show
*** This bug is a duplicate of bug 329974 ***
https://bugs.launchpad.net/bugs/329974
** This bug has been marked a duplicate of bug 329974
system-config-printer.py SIGSEGV in _nss_dns_gethostbyname2_r(), adding a
printer, i386 only
--
Jaunty 9.04 Blind to XP's Shared Network Printer
Thanks @Ed Comer in comment 10 - the workaround works for me!
@Thierry Carrez:
Does adding name resolve order = bcast host lmhosts wins to your
/etc/samba/smb.conf file change anything to the issue ?
No, unfortunately.
--
Jaunty 9.04 Blind to XP's Shared Network Printer
I will be unable to report further on the bug as I replaced 32-bit
Ubuntu 9.04 with the 64-bit Ubuntu 9.04 on the exact same hardware, in
the exact same environment and the bug is NOT present. With 64-bit
Ubuntu 9.04 I easily created a networked shared printer resident on a
Windows XP machine
Apport grabbed the crash and I reported it, linking it to existing bug
report 361629. Related bugs are 329974, 344218, 359088, 360524 and
361629. Of interest, I had successfully built a windows shared printer
using the workaround that I described in this bug report, 368273, but
attempted adding a
the dialog crash is certainly a system-config-printer issue.
It is libsmb that segfaults. If system-config-printer is using the
libsmb API correctly, this is a libsmb bug.
--
Jaunty 9.04 Blind to XP's Shared Network Printer
https://bugs.launchpad.net/bugs/368273
You received this bug
Crash happens in libsmb, closing system-config-printer task and leaving
samba (source of libsmb) task open.
** Changed in: system-config-printer (Ubuntu)
Status: New = Invalid
--
Jaunty 9.04 Blind to XP's Shared Network Printer
https://bugs.launchpad.net/bugs/368273
You received this bug
OK, would someone have evidence of that libsmb crash/segfault ? I could
use a stack trace, crash dump or logged segfault... I don't have XP
shared network printers to reproduce.
--
Jaunty 9.04 Blind to XP's Shared Network Printer
https://bugs.launchpad.net/bugs/368273
You received this bug
Well - if you'll give me a clue as to how to obtain that I will try. I
understand how to do that using gdb on a program that I invoke but what
process for libsmb ?
--
Jaunty 9.04 Blind to XP's Shared Network Printer
https://bugs.launchpad.net/bugs/368273
You received this bug notification
Even if the root cause might be in samba, the dialog crash is certainly
a system-config-printer issue.
** Also affects: system-config-printer (Ubuntu)
Importance: Undecided
Status: New
--
Jaunty 9.04 Blind to XP's Shared Network Printer
https://bugs.launchpad.net/bugs/368273
You
@Jakob, Ed:
Does adding name resolve order = bcast host lmhosts wins to your
/etc/samba/smb.conf file change anything to the issue ?
** Changed in: samba (Ubuntu)
Status: New = Incomplete
--
Jaunty 9.04 Blind to XP's Shared Network Printer
https://bugs.launchpad.net/bugs/368273
You
I have changed the name resolve order in the past to resolve a total
inability to browse Windows shares, but that is not the issue in this
bug, consequentially, I have not changed the resolve order in smb.conf.
I can access Windows shares without problem, transfer files, etc. This
bug deals solely
Workaround found, but bug remains:
I used my Windows box IP address instead of Browsing for the printer. This
permitted me to go to the next steps and created a printer, although it didn't
work, i.e. the test page didn't print. However, I then clicked a change URI
button and it presented
I ran the Live-CD version of the 64 bit version of Ubuntu 9.04 as an
experiment to see if the problem existed there also. This bug is NOT
present in the 64-bit version. I can easily create a networked printer
resident on a Windows XP machine on amb64 Ubunto 9.04.
--
Jaunty 9.04 Blind to XP's
I have the same bug on jaunty-armel... I have a printer connected to my
other Jaunty linux box(Jauntyx86) and I try to print to that printer
from Jaunty-armel. Whenever I go to System-Administration-Printing,
New-Network Printer-Windows Printer via SAMBA, Browse - I get right up
to where clicking
Sorry for the double post, launchpad gabe me an error on the first try.
Here is the screenshot of the dialog i was capturing the network traffic
for.
The popup just says something like no printers found.
** Attachment added: no-printers.png
I am coming from a related discussion on UbuntuForums that concerns
similar behaviour (although related to folders)
Having upgraded 3 systems from 8.10 to 9.04 (2 physical, 1 virtual) I
have been seeing the exact same behaviour on them all. The SMBClient
set up that was working perfectly on 8.10
I'm curious about the actual version of smbclient in question here.
I have TWO 8.04 LTS one server, one desktop both are running
$ smbclient --version
version 3.0.28a
--
Jaunty 9.04 Blind to XP's Shared Network Printer
https://bugs.launchpad.net/bugs/368273
You received this bug notification
Here is my Ubuntu 9.04 Jaunty version output, collected two different ways:
eco...@lsquirrel:~$ apt-cache policy smbclient
smbclient:
Installed: 2:3.3.2-1ubuntu3
Candidate: 2:3.3.2-1ubuntu3
Version table:
*** 2:3.3.2-1ubuntu3 0
500 http://us.archive.ubuntu.com jaunty/main Packages
25 matches
Mail list logo
