Chrome/Chromium should probably not wait that long if keyring is not
available. If it is not running, then it is not running, end of story.
Chromium should just proceed launching instead of bothering user with
behavior like this.
--
You received this bug notification because you are a member of
Here's the relevant journalctl log on VirtualBox. It complains something
about colord. "Laitetta tai osoitetta ei ole" means "No such device or
address".
elo 09 20:32:09 il-VirtualBox colord[1431]: (colord:1431): Cd-WARNING **:
failed to get session [pid 3130]: Laitetta tai osoitetta ei ole
elo
After talking with slashd, I did my own experiment in the same way I did
with virtualbox, but this time I used virt-manager and KVM instead.
Cannot reproduce. Maybe this has something to do with VirtualBox.
--
You received this bug notification because you are a member of Desktop
Packages, which
Here are log entries that result from the "sudo apt -t xenial-proposed
install cups-daemon"
Preparing to unpack .../libcupsppdc1_2.1.3-4ubuntu0.2_amd64.deb ...
Unpacking libcupsppdc1:amd64 (2.1.3-4ubuntu0.2) over (2.1.3-4) ...
Preparing to unpack .../libcupsmime1_2.1.3-4ubuntu0.2_amd64.deb ...
The last step in #109 is important. When doing the upgrade of cups-
daemon, it may look like it succeeded but with warnings. However, the
packaging system does break down and will became unable to successfully
do "apt upgrade".
--
You received this bug notification because you are a member of
Nope, the problem is still present in -proposed. Here's a more detailed
procedure of reproducing the bug:
- Do a clean Ubuntu install. I installed Ubuntu from the 16.04.3 desktop media
to a VirtualBox VM.
- Do a "apt update && apt upgrade" as usual
- Per the instructions from
@slashd, Maybe something has changed in systemd or something? I'll check
it out sometime when I have time.
Did you make a clean install? How did you ensure that the job was stuck
in the queue? I remember that adding a socket:// printer with an invalid
address did the trick.
--
You received this
The root cause of this problem is probably that the "invoke-rc.d cups
stop" command fails on Xenial if there are jobs in queue. The dpkg
preremoval script runs that command and thus the upgrade procedure
fails. In the newer Ubuntu versions the command executes flawlessly.
Until that problem is
Sorry, the "Make sure that cupsd is running" part should apparently be
"Make sure there is a stuck job in cups"
--
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/1642966
Title:
package
I have concluded that this problem only appears if the -proposed package
has never been installed AND cupsd is running.
So, the way to reproduce this is:
- Do a clean Ubuntu install
- Install updates
- Enable -proposed
- Make sure that cupsd is running
- Update cups-daemon.
When I do this, the
till-kamppeter, what do you mean by "restarting systemd"? Does it mean
that we could try adding something like this to the postinstall script:
"if dpkg --compare-versions "$2" lt-nl "2.1.3-4ubuntu0.2"; then
systemctl daemon-reexec
fi"?
Does it belong inside of the "if [ "$1" = configure ]"
So, what would be a reliable way to reproduce the problem?
Should the following sequence always trigger this issue:
- Do a clean Ubuntu install
- Install updates
- Enable -proposed
- Update cups-daemon?
--
You received this bug notification because you are a member of Desktop
Packages, which
Also, the test case in the bug report seems to return 0 unless there is
a job in queue. That job does not however affect the update process, so
I'll put verification-done to this.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because
I ran this test. The machine was a 64-bit Ubuntu 16.04.2 on a VirtualBox
VM. Before running the command I enabled -proposed and ensured that CUPS
will not shut down by having a stuck job in the queue. The upgrade
completed correctly.
Console output of the "apt update && apt install cups-daemon"
Public bug reported:
The StartupWMClass gets ignored for .desktop files that are launched by
Nautilus from outside the "~/.local/share/applications" or
"/usr/share/applications" directories
Steps to reproduce:
1) Download Tor Browser from the developer website
2) Unpack and execute it
Result:
@blacksheep001: Sorry, but this is a bug tracker, not a support forum.
Please take your question about lost Internet connectivity for example
to the Ubuntu forums (http://ubuntuforums.org/), maybe they can help
there.
--
You received this bug notification because you are a member of Desktop
Added patch tag because there is a patched PPA linked in comment #61.
** Tags added: patch
--
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/1642966
Title:
package cups-daemon 2.1.3-4
The change is already done since the package was updated to the lastest
upstream version.
** Changed in: cups (Ubuntu Zesty)
Status: Triaged => Fix Released
** Changed in: cups (Ubuntu Zesty)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification
launchpad-groovix: I meant it's too late to do anything about that this
bug slipped into xenial in first place. Fixing the problem afterwards
however should be possible, if little more complicated, sorry for being
unclear. The #1642966 probably is fixable and there has been effort to
do that to
launchpad-groovix: Weird. This "feature" shouldn't be active at all when
printer sharing is enabled. Did you look the cups log to make sure that
it really is the same problem?
And yes, this is a serious issue, but if you read the earlier messages,
you see that the fix will cause the bug 1642966
** Tags added: xenial
** Description changed:
Binary package hint: unity
This bug is about problems using the system bell in Unity or another
Compiz-based environment. For problems using the system bell in Ubuntu
Classic/Metacity or another Metacity-based environment, please see bug
** Summary changed:
- System bell broken in Natty/Unity (despite heroic...)
+ System bell completely silent because PulseAudio sample file undefined by
default
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-media in Ubuntu.
Present in 16.04.
Is the silence of the X11 bell intentional behavior? This is a really
weird case. I mean, the bug has been open for longer than half a decade
and triaged for a couple of years as well. The fix also is very simple
and there are proposed patches.
--
You received this bug
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
Public bug reported:
If I run bluetooth-sendto from command line and try to send the file, it
quits after selecting the target device with following command line
output:
"Acquiring proxy failed: Error calling StartServiceByName for
org.bluez.obex: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit:
** Tags added: regression-release
--
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/1598300
Title:
CUPS web interface stops responding after a while
Status in cups package in Ubuntu:
** Summary changed:
- cups hang after a while
+ CUPS web interface stops responding after a while
** Tags added: xenial
--
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/1598300
Title:
The package needs to be made to not to preserve the
/usr/lib/systemd/user/gvfs-daemon.service file?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1633162
Title:
Files application
Public bug reported:
Please backport the fix of this Debian bug to Xenial.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832637
To quote from there:
"The problem is most probably caused by inconsistency in how cups-browsed
accesses the local CUPS daemon, for some accesses it uses the
To add to the earlier comment, "brcmsmac" is the module name on my
system when using the open source driver. It can also be b44, b43,
b43legacy, ssb, brcmsmac or bcma, or with proprietary driver, wl.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I discussed this thing on #ubuntu-devel. Apparently it has something to
do with Broadcom WLAN chips or drivers as it seems to be unreproducible
on Intel chips. Would it be possible to make Broadcom drivers unload
before going to hibernate as it will help to avoid many problems?
User workaround:
Happens sometimes, but not after every suspend, with BCM4313. It's sad
to see this bug to be unfixed for so long.
--
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/1439771
Title:
*** This bug is a duplicate of bug 1439771 ***
https://bugs.launchpad.net/bugs/1439771
** This bug has been marked a duplicate of bug 1439771
wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
--
You received this bug notification because you are a member of Desktop
** Description changed:
On Latitude E6320, there are some weird wifi connectivity issues that
appear some times on resume. I haven't found any common factor that
would unify those incidents. I am currently running the brcmsmac open
source driver, but have encountered the issue with the
Public bug reported:
On Latitude E6320, there are some weird wifi connectivity issues that
appear some times on resume. I haven't found any common factor that
would unify those incidents. I am currently running the brcmsmac open
source driver, but have encountered the issue with the Broadcom STA
** 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/1622707
Title:
CUPS Web UI stops responding after a while
Status in cups
This seems to be a some kind of desktop/laptop power/resource saving
feature that does not take Web UI to the account. CUPS will immediately
start up again if I open the printing dialog or something.
When I read Stephan's error log as well as my own, it reads:
"I [30/Aug/2016:08:42:33 +0200]
Sorry for this comment flood.
Now I think I have finally solved it out:
If I run cupsd -l in console, it just quits with exit status 0 after a
while. If I run it as a service, it exits but goes back on-line
immediately after I do something that needs printing service.
It almost looks like there
It does not seem to affect lighttpd.
Journalctl did output following when it happened last time:
syys 12 22:03:41 sipuli dhclient[3111]: PRC: Renewing lease on wlp2s0b1.
syys 12 22:03:41 sipuli dhclient[3111]: XMT: Renew on wlp2s0b1, interval 9430ms.
syys 12 22:03:41 sipuli dhclient[3111]: RCV:
It seems to start responding again if I restart the CUPS service but it
seems to clear out after a while anyway. Now I proceed to test if it is
CUPS or the networking of the operating system by installing lighttpd
and trying if it has the same problem.
--
You received this bug notification
Public bug reported:
CUPS Web administration UI available at localhost:631 stops responding
after a while. Initially it works fine, but after it has been running
for a moment it just shows the "Connection refused" message of the
browser. The printing system keeps running otherwise. This is a
This bug seems to have resurfaced on xenial.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1306928
Title:
Broadcom STA driver gets autoinstalled on BCM4313, where it's
42 matches
Mail list logo
