I just now noted the remark above suggesting the remedy to programs
which crash abort when having a string parsing error is to not feed it
strings it doesn't like. I suppose, mutatis mutandis, were the string
one 99 of 100 leave defaulted it could be overlooked. However does
anyone really think
If this were a library used in a game or a bug in a screensaver I could
see letting a formatting error in a string crash abort any program using
the library sit for a year. I'm staggered really to experience this for
a package as widely touted as gnutls, contending to be a replacement for
Kindly notice that the fix mentioned above for .40, was dated not quite
a year ago.
I'm not a ubuntu expert, but I think this page:
https://launchpad.net/ubuntu/+source/openldap
explains the fix mentioned above is not available as a backport for trusty, nor
native in utopic, nor even being
Public bug reported:
Using
root@email2:/tmp# dpkg -l | grep ldap
ii ldap-utils 2.4.31-1+nmu2ubuntu8 amd64
OpenLDAP utilities
ii libldap-2.4-2:amd64 2.4.31-1+nmu2ubuntu8 amd64
OpenLDAP libraries
ii
Public bug reported:
This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid
branch.
When upgrading to this version, this is the warning message I get:
Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service
failed to load: No such file or directory.
More info on my setup:
I only use systemd booting with init=/lib/systemd/systemd kernel booting line.
I have upstart, cgmanager and systemd-shim purged.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
An update to this bug.
I haven't seen the hang described here since I upgraded GDM to the version
3.14.0-0ubuntu1.
It may or may not have anything to do with this.
However, this bug report may now be closed.
** Changed in: systemd (Ubuntu)
Status: Incomplete = Invalid
--
You received
Martin,
Well the GenuineIntel.bin may come from intel-microcode package of the Vivid
multiverse repository.
This is installed because of the Intel Core i7 Haswell processor.
My motherboard Asus Sabertooth has UEFI-BIOS and it is using UEFI Secure boot,
which may have something to do with this
Here is the attachment /boot/initrd.img-*
** Attachment added: initrd.img-3.16.0-24-generic
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+attachment/4258396/+files/initrd.img-3.16.0-24-generic
--
You received this bug notification because you are a member of Ubuntu
Touch
Martin,
The command cpio -tv /boot/initrd.img-3.16.0-24-generic did nothing.
Terminal just started a neverending process (but not getting stuck).
I did wait for several minutes.
The size of /boot/intitrd.img-3.16.0-24-generic is 19.2 Mb.
--
You received this bug notification because you are a
Martin,
My setup is fairly new, from September 2014.
I installed Ubuntu-Gnome Trusty then and upraded it first to Utopic and now to
Vivid dev.
I haven't mofified /etc/initramfs-tools/initramfs.conf in any way.
I attach this file here.
The folder /etc/initramfs-tools/conf.d/ is empty.
**
Martin,
I also attach the file /etc/intramfs-tools/update-initramfs-conf here.
** Attachment added: update-initramfs.conf
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+attachment/4257300/+files/update-initramfs.conf
--
You received this bug notification because you are a
Martin,
Here are the results.
1) gzip -cd /boot/initrd.img-3.16.0-24-generic | cpio -t | grep readlink
gzip: /boot/initrd.img-3.16.0-24-generic: not in gzip format
cpio: arkiston ennenaikainen loppu
(arkiston ennenaikainen loppu = the archiv ended prematurely)
2) after running sudo
Here:
file /boot/initrd.img-3.16.0-24-generic
/boot/initrd.img-3.16.0-24-generic: ASCII cpio archive (SVR4 with no CRC)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Martin,
Here are the answers.
1) $ ls -l /sbin/init
Command not found
So, a little different. What is missing here?
2) Initramfs-tools v. 0.103ubuntu8
That is the latest one.
3) /boot/grub/grub.cfg
It is now attached.
** Attachment added: Grub.cfg
SysRQ
My keyboard does not apparently have that button.
http://www.logitech.com/en-gb/product/illuminated-keyboard-k740
So, at least trying Alt+Print Screen R+E+I+S+U+B does nothing, even after a
successful boot.
The hang
Yes, I now have only this in kernel line: quiet init=/lib/systemd/systemd
Hi Martin,
True, I cannot switch between tty's. The whole system is unresponsive to
any keyboard commands.
About SysRQ (reisub): I cannot try it, because in my keyboard (Logitech K740)
there is no SysRQ button.
Usually it is the alt-function of the PrintScreen button, but not here.
About the
Martin,
In addition the previous post #8
I tried again booting without quiet in the kernel line: 10/10 boots were
successful.
Then with quiet: 3 out of 10 did hang.
Hanging (or crash) happens right after the fsck is done.
Mostly after sda1 fsck and before sdb1 fsck.
Sometimes both sda1 and
Hi Martin,
Here is some info.
Well yes -- You have no package which provides /sbin/init then, so you
need to install either upstart or systemd-sysv.
I have had systemd-sysv installed all the time.
Interesting, so mostl likely the fsck succeeded.
Mounts: sda1 is /, sdb1 is /home. They are two
Martin, do you have upstart, systemd-shim, cgmanager and libcdmanager0
purged and are you using kernel line init=/lib/systemd/systemd ?
I cannot boot at all if I remove the kernel booting line.
Then to your questions:
1) I could not get the booting hang when quiet was dropped from the kernel
I downgraded systemd to the version 208 in official Vivid repos.
Now booting works perfectly and fast.
It may be worthwhile to tell that I have purged systemd-shim, cgmanager and
libcgmanager0 from my setup.
So this really is a pure systemd booting setup now.
--
You received this bug
Public bug reported:
I just installed (for testing) the newest systemd from Vivid proposed
repositories.
Yes, that is only a proposed package.
The version is 215-5ubuntu1. Also the new plymouth was needed to do this
(version 0.9.0-0ubuntu8).
After the installation I find that every second boot
Further info:
I use solely systemd booting.
So, I have systemd-sysv installed and upstart, systemd-shim, cgmanager,
libcgmanager0, removed.
I also use the kernel line: init=/lib/systemd/systemd
If I remove that, I get a kernel panic.
--
You received this bug notification because you are a
It's the infinite loop of trapped SIGTERMs that raises this exception,
and can be performed in any way that deliberately infinitely loops a
signal trap.
$ bash -c 'trap kill 0 EXIT SIGTERM'
Segmentation fault (core dumped)
$ bash -c 'trap kill $$ EXIT SIGTERM'
Segmentation fault (core dumped)
$
So, after some browsing, it apears that trap recursion was introduced
intentionally in 4.3-rc2. There is commented code in bash.c that makes
it look like trap recursion was originally intended to be a configurable
build option, but was made default behaviour instead.
One fairly easy fix would be
Re the above: the patch was *not* correctly applied in trusty package
bash_4.3-7ubuntu1.2.
lucid package bash_4.3-7ubuntu1.2 appears to have been upgraded fine,
and handles the test case correctly.
harry@mars:~$ md5sum Downloads/bash_4.3-7ubuntu1.1_amd64/bin/bash
Downloads/bash_4.3
Martin Pitt wrote:
Right, that will switch the default init to systemd. If you want to experiment
with that, you can do either that or boot with init=/bin/systemd (you don't
need both).
Well I did test that with my high-end setup (Intel Core i7 4790 + Asus
Z97 Sabertooth + Samsung 850 Pro SSD)
i686
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: harry 2071 F pulseaudio
CurrentDesktop: Unity
Date: Sun Aug 24 13:05:39 2014
InstallationDate: Installed on 2014-07-11 (43 days ago)
InstallationMedia: Ubuntu
Right,
yesterday when systemd (208-7ubuntu4) and sysvinit (2.88dsf-41ubuntu17) were
published in Utopic pocket release,
I upgraded my setup.
After that I installed systemd-sysv and purged upstart, upstart-bin, ureadahead
and libjson0.
I am using systemd booting and it works just fine (with no
Yes,
I can confirm that the Martin's PPA version of systemd (208-2pitti1) works fine
with the latest cgmanager (0.27-0ubuntu7) and with the package cgmanager and
latest systemd-shim (6-3ubuntu1) installed.
I think we should get the systemd 208 into the Utopic official repos
now.
--
You
** Description changed:
I have a completely upgraded Ubuntu Utopic development branch setup, with
proprietary nvidia drivers installed.
I have set my booting system to boot with systemd instead of the upstart one.
The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager.
-
The new systemd (208-6ubuntu1) works fine on my setup:
fully updated Utopic (amd64) with nvidia proprietary drivers.
I tested this with systemd booting.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Thank you Serge.
I am afraid the building procedure you asked is beyond my skills.
** Tags added: systemd-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1343802
Public bug reported:
I have a completely upgraded Ubuntu Utopic development branch setup, with
proprietary nvidia drivers installed.
I have set my booting system to boot with systemd instead of the upstart one.
The newest systemd-shim (version 6-3ubuntu1) depends on cgmanager.
However,
I noticed that bug LP: #1342586 is solved and fix released, but this new
bug is not solved by that systemd update.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd-shim in Ubuntu.
101 - 135 of 135 matches
Mail list logo
