The current default discovery method is SLP.
On Friday, June 16, 2017 4:27:01 PM EDT Till Kamppeter wrote:
> It seems that mDNS/Bonjour (aka DNS-SD) is more reliable than the method
> which HPLIP uses by default (SNMP? HP guys, am I correct?). DNS-SD is
> the more modern way to discover devices
A workaround seems to be to click the "Show Advanced Options" button in
the Device Discovery window and change the Network Discovery Method to
mDNS/Bonjour. It will successfully detect the printer with that method.
--
You received this bug notification because you are a member of Desktop
Public bug reported:
On a fresh install of Kubuntu 17.04 I cannot add a network printer though the
HPLIP Toolbox. I get an error message that says "HPLIP cannot detect printers
in your network.
This may be due to existing firewall settings blocking the required ports. When
you are in a trusted
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 Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1534958
Title:
Cups
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
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 Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
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 to be working with 15.04
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 installed
When can we expect a fix? My scanner is useless without the plugin.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1422004
Title:
pkservice.py crashed with AttributeError in
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
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
** Bug watch added: Debian Bug tracker #767361
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767361
** Also affects: hplip (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767361
Importance: Unknown
Status: Unknown
--
You received this bug notification because
I do not have wine installed either. I'm not sure how wine would cause this
anyway.
On Tuesday, February 03, 2015 01:51:13 PM Zero wrote:
I have recently been having trouble with getting Wine1.7 to coexist with
driver 331.113-updates, forced to regress to the non-updates tested
version. I
From what I can tell this is an Ubuntu issue. There's no reason to bug Nvidia
about it since they don't do any work with the Ubuntu packages
On Thursday, January 15, 2015 04:36:13 PM snurfle wrote:
OK... I was using the nvidia-current drivers in xubuntu 14.10 with no
issues whatsoever. The
The Ubuntu packages are not just a drop-in. They hook into DKMS which the
Nvidia drivers themselves do not do. There's also a lot of other Ubuntu
specific things that the package does. Looking at all these bugs they all have
to do with the module failing to build with the Ubuntu package. I
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
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
Same here. I saw the error that the DKMS module failed to build however the
Nvidia driver is still working fine.
On Wednesday, November 26, 2014 11:06:37 AM Bart Willemsen wrote:
Even though the problem reported is of a DKMS module failing to build,
my output with 'dkms status' shows that
I wrote about this 4 years ago.
http://linuxtechie.wordpress.com/2010/01/05/file-roller-is-terribly-
inefficient/ You hit the exact same points I did. I no longer use Gnome
anymore but it's sad to see this stupidity still hasn't been fixed.
--
You received this bug notification because you are a
** Also affects: easytag
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to emacs23 in Ubuntu.
https://bugs.launchpad.net/bugs/1142213
Title:
emacs23/24 and other GTK applications do not start
AFAIK you do not need the driver on the client. See comment #3 for details.
you will only get asked for a queue name, not for a driver. I can confirm
that if done correctly you do not get asked for a driver.
On Wednesday, October 03, 2012 04:51:23 PM Kevin Keijzer wrote:
I guess this was to be
Public bug reported:
The version of CUPS in 12.10 introduced a new autodetection for IPP
printers via Avahi. I am unable to print anything to the printer until I
log into the server the printer is connected to and run cupsctl
--share-printers. I need to do that every time I try to print something
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1059908
Title:
Cannot print to IPP network printer with 12.10 client
Status in “cups” package in Ubuntu:
New
Bug description:
The
Sorry, this ended up being an issue with my iptables rules.
** Changed in: cups (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1059908
Title:
Same problem except with Writer and Impress
** Attachment added: missing icons.png
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/990647/+attachment/3113582/+files/missing%20icons.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
This bug is still present in Oneiric with LibreOffice and the Polyester
theme. LibreOffice opens then closes immediately. Only happens with the
Polyester theme.
** Also affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/903013
Title:
libreoffice crashes on start with polyester theme
Status in “libreoffice” package in Ubuntu:
New
Bug description:
I have opened a new bug here
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/903013 as
apport would rather have me open a new bug then modify an existing one I
didn't submit.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
LibreOffice opens then closes immediately with the Polyester theme in
use. It does not happen with other themes.
Steps to reproduce:
1. Install Polyester theme
2. Change the theme to Polyester
3. Start LibreOffice Writer
4. It opens but crashes immediately
What should
Running 11.10. There still is no way to specify a custom port.
On 10/20/2011 09:18 AM, Pedro Villavicencio wrote:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the
31 matches
Mail list logo
