This was caused by an incorrectly configured client.
** Changed in: cups (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1534958
Title:
Public bug reported:
I'm trying to print a PDF file to a shared Cups network printer (HP
LaserJet P1505 using the foo2xqx driver) and it fails because it is
expecting a Postscript file but the job is in a different format. Either
Cups should accept other formats or the client may be sending the wr
What is your test case? Are you sure this is the same bug?
On Friday, August 28, 2015 01:21:14 AM Aaahh Ahh wrote:
> Back at it in Ubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.
Nevermind. It does work. That was a problem with kwallet.
On Friday, May 01, 2015 06:07:27 AM Nick B. wrote:
> I take that back. Woke my laptop up today and it didn't automatically
> connect.
>
> On Monday, April 27, 2015 04:13:13 PM Nick Bryda wrote:
> > Yep, seems t
I take that back. Woke my laptop up today and it didn't automatically
connect.
On Monday, April 27, 2015 04:13:13 PM Nick Bryda wrote:
> Yep, seems to be working with 15.04
>
> On Monday, April 27, 2015 06:59:35 PM Torbjörn Moa wrote:
> > The problem seems to have gone away in vivid. I just insta
Yep, seems to be working with 15.04
On Monday, April 27, 2015 06:59:35 PM Torbjörn Moa wrote:
> The problem seems to have gone away in vivid. I just installed Kubuntu
> 15.04, and the issue is not there anymore. The WIFI reconnects nicely
> after sleep/resume without any tricks. I haven't tested v
I'm starting to think this is related to hidden SSIDs. I can't seem to
reproduce this problem on non-hidden networks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1
I tried that and it didn't work. This machine was upgraded and it only started
after upgrading to 14.10 with no changes made to the network settings. Prior
it was working as expected.
On Wednesday, January 14, 2015 06:24:34 PM Søren Holm wrote:
> As state in a previous post: You can change whate
I've got this same problem too. After doing a fresh boot and logging in,
the wireless will not connect but it is listed in the plasma-nm
connection list. I've found that if I delete it and re-add the
connection it will automatically reconnect after suspend/hibernate until
the next reboot or login.
Public bug reported:
After resuming from hibernate I have no network connection. This doesn't
happen with suspend, only hibernate. I'm guessing this is something with
network-manager as doing 'sudo service network-manager restart' fixes
the problem. ifconfig shows no eth0 interface but doing 'ifco
10 matches
Mail list logo
