Confirmed with 14.04 (x86) and latest updates.
Fresh install with minimal iso; afterwards in tasksel selected Basic Ubuntu
Server, OpenSSH server, Mail-Server and Samba file server.
When sudo-ing the first time after running tasksel, the error occured.
Fix:
run pam-auth-update and remove SMB
Launchpad has imported 4 comments from the remote bug at
http://bugs.squid-cache.org/show_bug.cgi?id=2741.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Confirmed with 14.04 x64, every time i run the sudo command :
quentin@asus-N56VZ:~$ sudo su
[sudo] password for quentin:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
root@asus-N56VZ:/home/quentin#
--
You received this bug notification because you are a member of
Public bug reported:
Description:Ubuntu 14.04 LTS
GNU bash, version 4.3.8(1)-release (x86_64-pc-linux-gnu)
Screen version 4.01.00devel (GNU) 2-May-06
Screen changes terminal width on launch. I was using default
configurations of screen. (no .screenrc in home directory)
steps
1. Change the
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1294958
Title:
php5 assert failure: libgcc_s.so.1 must be installed for
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding php5. This problem was most recently seen with version
5.5.4+dfsg-1+debphp.org~precise+1+a22+3, the problem page at
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding php5. This problem was most recently seen with version
5.5.4+dfsg-1+debphp.org~precise+1+a22+3, the problem page at
https://errors.ubuntu.com/problem/57e4749ce1a6da0ff464c3e2c649682d929e848e
Public bug reported:
After upgrading to 14.04 I created an unprivileged lxc container
following https://www.stgraber.org/2014/01/17/lxc-1-0-unprivileged-
containers/
Unlike root containers they fail to start. With logging level strace I
get this output:
lxc-start 1397905196.384 INFO
Public bug reported:
Thinkpad S230U resumes immediately after suspend. Can test with: sudo
pm-suspend.
Updated Bios to 1.63 (latest bios version has a bad bug that disables USB /
trackpad), same behavior.
Not sure if should be reported against pm-utils or kernel - apologies if I got
it wrong.
It looks like your system was configured to mount the cgroup hierarchy
on /var/local/cgroup which must be interfering with cgmanager and
causing the problem you are seeing.
Can you make sure you don't have any cgroup mounts done from your
/etc/fstab ?
--
You received this bug notification
Indeed, there was a line
cgroup /var/local/cgroup cgroup defaults 0 0
after commenting it out and a reboot (umount was not enough) it works as
expected. Thank you Stéphane!
** Changed in: lxc (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a
Confirmed, solution of Thomas works for me, thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1257186
Title:
memory leakage messages
To manage notifications about this bug go
This bug seems to be back in trusty x32.
get_extension_funcs ('Zlib') shows gztell64, gzseek64, gzopen64.
php -i | grep ZLib:
ZLib Version = 1.2.8
php5-common=5.5.9+dfsg-1ubuntu4
zlib1g:i386=1:1.2.8.dfsg-1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
I have had the same issue since upgrading 13.10 to 14.04. Thomas
solution did not work for me.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1257186
Title:
memory leakage messages
** Changed in: powernap (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to powernap in Ubuntu.
https://bugs.launchpad.net/bugs/1266057
Title:
powerwaked: Typo in package description:
** Attachment added: failed_to_bring_up_br0.png
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1310076/+attachment/4089342/+files/failed_to_bring_up_br0.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
Public bug reported:
After setting up hwe-s for precise along with the doc below, `juju add-machine`
fails with Failed to bring up br0. Then lost connectivity to a node.
http://maas.ubuntu.com/docs1.5/hardware-enablement-kernels.html
I'm using fastpath-installer, d-i is not tested yet.
The kernel was still 3.2 not hwe-s though.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using fastpath-installer with
precise+hwe-s
After changing /etc/maas/preseeds/curtin_userdata to use default
archive not ports.ubuntu.com for hwe-s, `juju add-machine` succeeded.
=== modified file 'maas/preseeds/curtin_userdata'
--- maas/preseeds/curtin_userdata 2014-04-19 18:37:53 +
+++ maas/preseeds/curtin_userdata
d-i case was filed as Bug #1310082.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using fastpath-installer with
precise+hwe-s
To
** Attachment added: architecture_not_supported.png
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1310082/+attachment/4089354/+files/architecture_not_supported.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
Public bug reported:
After setting up hwe-s for precise along with the doc below, `juju add-machine`
fails with Architecture not supported in d-i.
http://maas.ubuntu.com/docs1.5/hardware-enablement-kernels.html
From squid-deb-proxy log, d-i is trying to connect to:
** Branch linked: lp:~timo-
jyrinki/ubuntu/trusty/libsdl1.2/fix_backingstore_tearing
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libsdl1.2 in Ubuntu.
https://bugs.launchpad.net/bugs/1280665
Title:
libsdl1.2 always uses
After changing /etc/maas/preseeds/curtin_userdata to use default
archive not ports.ubuntu.com for hwe-s, `juju add-machine` succeeded.
However the kernel after reboot was 3.2 not hwe-s. Am I misunderstanding
this hwe feature?
=== modified file 'maas/preseeds/generic'
--- maas/preseeds/generic
I've the same with xbmc on 14.04 on intel (haswell). The upstream bug
report has more background on the issue.
I've verified the patch works and it alone fixes the tearing issue, so I
proposed it for merging. The u-series is not open yet during this
weekend it seems, but probably next week
From the log of d-i, the node booted up with 3.11(lts-saucy) then install 3.2
in in-target. 3.2 seems defined in /etc/maas/preseeds/preseed_master.
d-i base-installer/kernel/image string linux-server
** Attachment added: d-i.tar.gz
After changing linux-server to linux-generic-lts-saucy, 3.11(lts-saucy)
was installed. base-installer/kernel/image needs to be set corresponding
to the hwe value set by user, IMHO.
=== modified file 'maas/preseeds/preseed_master'
--- maas/preseeds/preseed_master2014-04-19 18:37:53 +
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1310076
Title:
lost connectivity to a node when using
I had tearing in Teeworlds with vsync enabled after upgrading from 13.10 to
14.04.
I confirm that the patch sdl-check-for-SDL_VIDEO_X11_BACKINGSTORE.patch fixes
the issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libsdl1.2 in
It should be noted that upstream is not planning on making another SDL
1.2 release. They are building a compatibility API for SDL 2.0 instead.
We should apply this patch until that compatibility API is ready.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
From the log of curtin manually kicked inside maas node, curtin is trying to
install lts-saucy but fails.
Tried to install kernel linux-generic-lts-saucy but package not found.
If I manually put the content below in /etc/maas/preseeds/curtin_userdata,
curtin installs lts-saucy kernel.
Public bug reported:
the squid lens (squid.aug) contains
let filter = incl /etc/squid/squid.conf
but trusty's squid.conf path is /etc/squid3/squid.conf
augtool can't read /etc/squid3/squid.conf and that seems to be the reason.
regards
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Public bug reported:
Just installed puppet from Ubuntu repos and it is showing this error:
Debug: Puppet::Type::Alternatives::ProviderDpkg: file
/usr/sbin/update-alternatives does not exist
Error: Could not find a suitable provider for alternatives
Debug: Finishing transaction 27518840
Debug:
Upgraded 13.10 x64 server to 14.04. Consistently seeing this message
whenever running sudo. For example,
xxx@xxx:/$ sudo -e testfile
[sudo] password for xxx:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
--
You received this bug notification because you are a member
Public bug reported:
samba from nautilus can't connect to windows resources
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: samba-libs (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
35 matches
Mail list logo