Public bug reported:
When running backup with duplicity, it cannot handle sparse files
efficiently.
I have a virtual machine image on my home dir,
26G -rw-r--r-- 1 libvirt-qemu kvm 33G huhti 28 08:59 dev02.img
And duplicity is backing it up 33G, when it should only back up 26G.
Steps to reprod
After much experimenting, the problem seems to be with the nvidia
driver. Updating it to nvidia-361 made *this* problem go away, except it
renamed all outputs, refused to show anything on eDP-1 and made the
whole thing hung in 5 minutes after reboot. Reverted to 15.10 which has
less difficulties.
Clarification on last comment, it did show black screen on eDP-1, which
changed to having image if one logged out. After logging in, it turned
into black screen with garbled 2mm band at top of the screen. Mouse was
displayed on the screen if moved there, but as I said, the entire
machine tended to
Public bug reported:
When trying to extend desktop to third display, following error is
given. It can be configured as mirror of DP-1-2 but not as extended
display.
# xrandr --verbose --output eDP1 --primary --output DP-1-2 --right-of eDP1
--output DP-1-4 --right-of DP-1-2 --mode 1920x1080
scree
I think I'm happy that it's been fixed. I was able to figure out the
"root cause" for the troubles, so I don't need aa-genprof and aa-
logprof at all for this. It is bit bad though that there is no tool that
would just show you the rules it would generate instead of updating
profile directory.
--
The version is, as provided in the initial message,
apparmor version 2.8.95~2430-0ubuntu5.3
Dec 11 10:24:07 gw-dc01 kernel: [2214272.912766] type=1400
audit(1449822247.549:21251): apparmor="ALLOWED" operation="file_inherit"
profile="/usr/sbin/sssd//null-45" name="/var/log/sssd/ldap_child.log"
pid
Public bug reported:
I am trying to write apparmor profile to match my sssd usage,
unfortunately it seems I cannot tell sssd to permit things it needs.
apparmor version 2.8.95~2430-0ubuntu5.3
Description:Ubuntu 14.04.3 LTS
Release:14.04
The complaints in log:
Dec 11 10:24:07 gw-dc01
Steps to reprocude:
1. samba-tool domain provision --use-rfc2307 --interactive
2. Choose BIND9_DLZ
3. Include the generated file in bind9 configuration
4. Try restart bind
Expected result:
Bind works as expected
Real result:
Bind refuses to start because the version number in the .so file
Public bug reported:
The dlz driver provided in samba package for trusty (14.04 LTS) has
wrong headers for bind 9.9.5 distributed with Trusty (14.04 LTS),
preventing the DLZ from being loaded in Bind9. This is definately a bug.
** Affects: samba (Ubuntu)
Importance: Undecided
Status
I'll see if I can find something. Is it possible to have a look at this
bug nevertheless, should it turn out to be a very simple bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1274122
Title:
php
~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 12.04.4 LTS
Release:12.04
Codename: precise
~$ php --version
PHP 5.3.10-1ubuntu3.9 with Suhosin-Patch (cli) (built: Dec 12 2013 04:27:25)
Copyright (c) 1997-2012 The PHP Group
Zend Engine v2
Public bug reported:
Please see the crash file attached. We do not know exactly why this site
crashes, but below is stack trace from crash file.
#0 0x00681a6d in do_bind_function (opline=0x7f2ecf4c3918,
function_table=0x25d0c40, compile_time=0 '\000') at
/build/buildd/php5-5.3.10/Zend/
Public bug reported:
When opening a folder in mutt, it sometimes crashes. After starting mutt
again, it works for the folder.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: mutt 1.5.21-5ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
App
*sigh*. After checking this out really carefully I found out that you
can disable this message with dontLogTCPWrappersConnects. Too bad that
no amount of googling came up with this bit of information. You can
close this ticket.
** Changed in: net-snmp (Ubuntu)
Status: Incomplete => Invalid
I was sure I saw a patch for this, but now that I tried to find it, I
couldn't. It is easy to fix however, by changing allow_severity to
LOG_DEBUG. The log entry is useless imho.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/696753
Title:
Cannot disable connection logging
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
Public bug reported:
snmp daemon keeps spamming logs with
Jan 3 13:09:06 mordor snmpd[2961]: Connection from UDP:
[x.x.x.x]:y->[x.x.x.x]
And there is no way to disable this. There is a patch for this, but it
is not applied to the lucid version apparently.
# lsb_release -rd
Description:Ubun
Public bug reported:
Binary package hint: fail2ban
I cannot find any method for unbanning IP manually with the fail2ban
client. Could you please add this method?
ProblemType: Bug
Architecture: amd64
Date: Sun Sep 26 16:35:34 2010
Dependencies:
coreutils 7.4-2ubuntu2
debconf 1.5.28ubuntu4
debc
** Attachment added: "Xorg configuration file"
http://launchpadlibrarian.net/14035875/xorg.conf
** Description changed:
When connecting with RealVNC or TightVNC client to X server with VNC
extension loaded, the X server crashes. Sometimes directly at
connection, sometimes when you press
Public bug reported:
When connecting with RealVNC or TightVNC client to X server with VNC
extension loaded, the X server crashes. Sometimes directly at
connection, sometimes when you press a key. No log file contain anything
useful. This bug came existence after upgrading to Hardy. See below for
X
20 matches
Mail list logo
