*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 799452
package man-db 2.5.9-4 failed to install/upgrade: subprocess installed
post-installation script was killed by signal (Broken pipe)
** This bug has been
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 799452
package man-db 2.5.9-4 failed to install/upgrade: subprocess installed
post-installation script was killed by signal (Broken pipe)
** This bug has been
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
I tried to burn a bluray BD-R on my Kubuntu 14.04 LTS laptop using k3b.
This did not work. (files from the resulting disc can not be read).
After some research I got here.
Since I could not find the cdrtools source mentioned in the messages above
using the URLs
on berlios I tried to find cdrt
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 795979
package man-db 2.5.9-4 failed to install/upgrade: el subproceso instalado el
script post-installation devolvió el código de salida de error 255
** This
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 796178
package man-db 2.5.9-4 failed to install/upgrade: subprocess installed
post-installation script was killed by signal (Broken pipe)
** This bug has been
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 786065
package man-db 2.5.7-2ubuntu1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 9
** This bug has been
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 795979
package man-db 2.5.9-4 failed to install/upgrade: el subproceso instalado el
script post-installation devolvió el código de salida de error 255
** This
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 819571
segfault during man-db trigger
** This bug has been marked a duplicate of bug 1372673
excessive debconf use when triggered
--
You received this bug
Same user verified as had the initial issue.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1280370
Title:
high latency between
** Tags added: design-sync
** Also affects: ubuntu-ui-toolkit
Importance: Undecided
Status: New
** Changed in: ubuntu-ui-toolkit
Status: New => Confirmed
** Changed in: ubuntu-ui-toolkit
Importance: Undecided => Medium
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 796178
package man-db 2.5.9-4 failed to install/upgrade: subprocess installed
post-installation script was killed by signal (Broken pipe)
** This bug has been
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 774102
package man-db 2.5.9-4 failed to install/upgrade: subprocess installed
post-installation script was killed by signal (Broken pipe)
** This bug has been
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
Hi,
I have been following this bug since I got the same issues. As of now, I
have blocked the updates on driver-common as suggested here et dowgraded
it. It solved the problem.
A new patch have been released, does this mean I can update the package
normally ?
--
You received this bug notificati
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Status: New => In Progress
** Changed in: linux (Ubuntu Trusty)
Assignee: (
This got fixed in gnome-calculator 3.10.3 based on my testing. Can
somebody look at whether it's feasible to package this for 14.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311920
Title:
gno
Public bug reported:
When booting the system image, nothing generates ssh host keys.
Normally I think these are created on installation, but for good reason they're
not included in the image.
In cloud imags, cloud-init does this. In other systemd boot scenarios, they're
generated by another ss
** Changed in: ubuntu-ui-toolkit
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370417
Title:
Header - section, highlight area too high
To manage notifications about t
FWIW This has now been merged upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371472
Title:
Fix crash in QNetworkAccessCacheBackend::closeDownstreamChannel
To manage notifications about thi
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
Does anyone know what can be done to get this sorted? Can I help anyhow?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276811
Title:
14e4:1570 [MacBookPro11,1] iSight webcam changed from USB to PCI
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 774077
package man-db 2.5.9-4 failed to install/upgrade: subprocess installed
post-installation script was killed by signal (Broken pipe)
** This bug has been
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
Hi Colin!
Does this fix cover bug #1364642 and its duplicates too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372673
Title:
excessive debconf use when triggered
To manage notifications about t
There was one patch to the CIFS driver between Ubuntu-3.13.0-35.62 and
Ubuntu-3.13.0-36.63, commit e42d08d467e1ca772eeb8cb5694920c287a4b1f0
(cifs: sanity check length of data to send before sending) which appears
to be responsible for this warning in dmesg:
[ 10.621812] WARNING: CPU: 0 PID: 2040
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
For the record, while this helped a bit it's still not fully functional.
See bug 1372873.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161989
Title:
read: Value too large for defined data type
To
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 774077
package man-db 2.5.9-4 failed to install/upgrade: subprocess installed
post-installation script was killed by signal (Broken pipe)
** This bug has been
Public bug reported:
I'm downloading an image, and booting it in kvm via
lp:~ubuntu-foundations-team/create-ubuntu-core-image .
The result is a image that requires graphics to log into. Ie, I'd much rather
use either '-nographic' or '-curses' flags to kvm.
This is much easier to work with remot
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
This still seems to be the case... On Krillin #56, the DTMF tones are
still very loud. Dialing a number in public caused people staring at me
several times already :)
** Changed in: tone-generator (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
Apps should use echoMode: TextInput.Password to take advantage of this
fix
** Summary changed:
- [sdk] Implement PasswordEchoOnEdit for the wifi passphrase textfield
+ [sdk] echo last character entered in password fields
--
You received this bug notification because you are a member of Ubuntu
B
Without more details it's impossible to track this down further, and I
don't think there's much value in leaving the man-db task on this bug
open at this point. My guess is that this is either an automatically-
misfiled consequence of some other bug, or a duplicate of bug 1372673
(for which I'm cu
** Also affects: ubuntu-ux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372923
Title:
On dual SIM devices, explain in the wizard which slot supports dat
*** This bug is a duplicate of bug 981631 ***
https://bugs.launchpad.net/bugs/981631
** This bug has been marked a duplicate of bug 981631
No progress indication when resizing partitions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 945028 ***
https://bugs.launchpad.net/bugs/945028
@Till
Your solution worked, thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992468
Title:
network p
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/981631
Title:
No
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 981631 ***
https://bugs.launchpad.net/bugs/981631
** This bug has been marked a duplicate of bug 981631
No progress indication when resizing partitions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
** Also affects: linux-meta-lts-backport-quantal (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
nfs4 daemon crashes, eventually PC
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
** Changed in: unity8-desktop-session
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365537
Title:
Incorrect env var used in lightdm-unity8-session
To ma
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 594858
package man-db 2.5.7-2 failed to install/upgrade: Can't locate
auto/POSIX/load_import.al
** This bug has been marked a duplicate of bug 1372673
exces
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 594858
package man-db 2.5.7-2 failed to install/upgrade: Can't locate
auto/POSIX/load_import.al
** This bug has been marked a duplicate of bug 1372673
exces
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
** This bug is no longer a duplicate of bug 594858
package man-db 2.5.7-2 failed to install/upgrade: Can't locate
auto/POSIX/load_import.al
** This bug has been marked a duplicate of bug 1372673
exces
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
** Changed in: ubuntu-ux
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371655
Title:
[system settings] allows to change lock security without asking for
passcode
I do not have bind mounts, but the exported filesystem is however stored
on a software raid1 block device
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353730
Title:
nfs4 daemon crashes, eventually
*** This bug is a duplicate of bug 1372673 ***
https://bugs.launchpad.net/bugs/1372673
Thanks for your report. The basic problem here is that man-db's trigger
uses debconf to decide whether to update the manual page database, but
debconf is not always reliably usable in triggers. I finally f
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372924
Title:
package fp-utils-2.6.4 (not installed) failed to install/upgrade:
trying to overwrite
'/usr/lib
** Branch linked: lp:~stolowski/unity-scopes-api/user-agent
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1372834
Title:
SmartScopesProxy needs to send version numbers to the server
To manage notif
I have found a workaround to this bug. In other words, suspend now works
in MaxBookPro 11,1 if you do:
1. Push e.g. control+alt+fn+F1 to go to a tty.
2. Close the laptop lid.
After about 3 seconds, the laptop sleeps. Hurray!
Upon resume, the tty had this message, which is also present in dmesg:
901 - 1000 of 1286 matches
Mail list logo
