Public bug reported:
Binary package hint: usb-creator
I'm trying to use usb-creator from a karmic daily-live CD (dating July
10, 2009) to create a USB thumdrive with karmic.
While trying to debug why it didn't attempt to create the casper-rw
file for holding the data for the persistent feature,
I confirm this bug to still be present in Karmic (daily-live from 10th
of July).
As an aside: this daily-live also reports conflicting versions about
usb-creator. See also bug #398124 :
* dpkg -l usb-creator:
reports 0.1.16
* usb-creator --version:
reports 0.0.11
** Summary changed:
-
*** This bug is a duplicate of bug 316077 ***
https://bugs.launchpad.net/bugs/316077
This bug is still in Kubuntu 9.10 (beta) as tested with a daily-live CD
image.
** Summary changed:
- Missing dependencies in Kubuntu 9.04
+ usb-creator cannot be installed in Kubuntu 9.04 (and 9.10
This bug is also in Kubuntu 9.10 (beta) as tested with a daily-live CD
image.
--
usb creator missing python-gnome2 dependency
https://bugs.launchpad.net/bugs/316077
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Same here.
I downloaded daily Live CD iso image (dated 20090301), did apt-get
install usb-creator and experienced same problem.
--
usb-creator crashed with ImportError in module()
https://bugs.launchpad.net/bugs/327081
You received this bug notification because you are a member of Ubuntu
Bugs,
Moreover, I cannot identify any package (apt-cache search gnomevfs)
that could solve the missing dependency. (I installed everything apt-
cache search offered...).
Still the same error message.
--
usb-creator crashed with ImportError in module()
https://bugs.launchpad.net/bugs/327081
You
Hmm... why is it that I can't see bug # 331327? (I only get Not allowed
here. Sorry, you don't have permission to access this page.)
--
stupid illegible Installation Failed dialog box
https://bugs.launchpad.net/bugs/333110
You received this bug notification because you are a member of Ubuntu
This looks to me like a duplicate of bug #332960 (I was getting the same
illegible dialog box at the end of my usb-creating exercise).
--
stupid illegible Installation Failed dialog box
https://bugs.launchpad.net/bugs/333110
You received this bug notification because you are a member of Ubuntu
cupsaddsmb is mean to install a PostScript driver (the Adobe/Microsoft
one, with or without a CUPS-specific extension). It explicitely supports
Windows 2000 or higher (optionally with the CUPS extension), or Windows
95/98/ME (no CUPS extension available).
This gives:
W32X86 -- the directory
It is true to the letter, in the way I described it. Look more closely
at the pure luck sentence, consider again more Mike's statement, read
again what I gave as my advice above, please. You'll then notice,...
...that the pure luck sentence is refering to this file (i.e. the
unchanged one),
Re. CUPS.org STR #1717:
CUPS 1.2.2 has been released today, which seems to include a fix for
that bug
--
cupsys prints empty pages
https://launchpad.net/bugs/51432
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Further above, I wrote:
The Listen directive *always* needs a colon,...
Actually, that is no longer true. (Dunno when the change was
introduced). The syntax checking for Listen is now more liberal, and
both forms
Listen *:631
Listen 631
are possible (the latter one is not
Is your LDAP authentication working alright for other services?
IMHO, your bug report should be renamed to a line like the heading of my
own comment.
Ubuntu cupsys 1.2.x packages are patched to retain the RunAsUser
feature (which is now deprecated and removed -- for good reasons! --
by the
Ante Karamatić wrote:
'Mike knows that RunAsUser and helper functions for init scripts (i.e.
start-stop-daemon) are two totally different things.'
I'm sure he knows that. What he meant to say was that a start-stop daemon
solution should then also use a port above 1024 (instead of
Oh, I forgot a very prominent and important service that does not comply
with your principles for security, Ante: Samba.
I just checked with the box of a friend who runs Dapper: it has the
original Dapper packages of Samba, and all smbd and nmbd processes do
run as root
--
dapper cupsys can
Please report this bug at CUPS.org (http://www.cups.org/str.php).
For now, to print it use one of 2 options:
a) print with the -o raw option (if you have a PostScript printer!)
lp -d printername -o raw xfig.ps
b) change the first line of the xfig.ps file to either read %! or %!PS
Manu,
your advice to use
Listen 631
is completely wrong, because of a wrong syntax you use. The Listen
directive *always* needs a colon, with something before and a port
number after the colon. You can take any combination of these syntax
examples (multiple declarations in one cupsd.conf):
CUPS printer and class names may contain any printable character, except
space, tab, /, or #. (See man lpadmin)
Also important to note: printer and class names are *not* case-
sensitive. myprinter and mYpRiNtEr are exactly the same printer for
CUPS!
A different kind of fish is what an
The sanitization of the device URI (not showing username and/or password
in log files or other places where device URIs show up for mortal users
to see) is in fact a *feature* that was introduced some time ago (it was
different before), in order to increase security.
Chances are pretty low that
Your original bug report (haven't read the postings below that) looks
like your original print file is content with some issue, so that what
CUPS' pstops filter sees coming along has a problem (like not being
compliant as DSC PostScript) it cannot process correctly.
It could also be a problem of
So why is this bug still in status needs info?
--
dapper cupsys can not print to rfc compliant lpd server, i.e. can not run as
root
https://launchpad.net/bugs/47773
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
General comments about /etc/cups/client.conf:
---
By default, CUPS.org ships its source code with a client.conf file that
is not active, and we also do not recommend that you use it by default
for standard workstations that are part of a
Hmm... let me put in a few more things.
The patched web page also says:
/usr/share/doc/cupsys/README.Debian.gz describes the details
and how to reenable it again.
Here is a list of all usability problems with this:
1. Kubuntu does not have the Gnome CUPS Manager installed.
Public bug reported:
Binary package hint: cupsys
Ubuntu Dapper (dunno about Breezy) cripples the CUPS web interface by
disallowing access to administrative functions (this is worth a bug
report with change request in itself). Thankfully, the entry web page
http://localhost:631/ is even patched
24 matches
Mail list logo
