Public bug reported:
The call to ptrace(PTRACE_TRACEME) fails in gdbserver in spite of
ptrace_scope being 0. As a result gdbserver hangs and is impossible to
use. When run with sudo it works fine. This seems to be a kernel bug.
# which gdbserver
/usr/bin/gdbserver
# cat
Public bug reported:
Ubuntu 16.04.1 LTS
MediaTomb version: 0.12.1-47-g7ab7616-1ubuntu2
The contents of /etc/default/mediatomb are used by 3 start-up scripts,
but the usage is inconsistent.
/etc/init/mediatomb.conf expects variables NOT to be prefixed with "MT_"
(ex: INTERFACE vs MT_INTERFACE).
Public bug reported:
Whenever I reboot the system, it seems to hang for a long time towards
the end of the shutdown. I found out it's because of the
/etc/init.d/sendsigs script's do_stop() function where it waits up to 5
minutes for $(upstart_killed_jobs) to report that all the jobs have been
The latest version is now at: https://github.com/gburca/rofs-filtered
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787764
Title:
[needs-packaging] rofs-filtered
To manage notifications about this
I no longer have the relevant logs. If I remember correctly the problem
was that either the host name or the domain name was not configured the
way roundcube expected it. The hostname --fqdn was not returning the
proper FQDN (or was failing) and that's what caused the roundcube
scripts to fail as
Public bug reported:
Binary package hint: roundcube
I tried uninstalling (it fails). I tried upgrading (it fails). Can't
seem to fix this problem, but I haven't really put my mind to it either.
It's annoying, but not the end of the world.
ProblemType: Package
DistroRelease: Ubuntu 10.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753194
Title:
package roundcube-core 0.3.1-3 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
error
I've noticed similar behavior. In my case, pressing any key on the
keyboard (ex. Shift) causes the boot sequence to continue. You can see
the system hang below between timestamps 4.274018 and 250.427922.
[3.470626] usb 2-2.1.1: configuration #1 chosen from 1 choice
[3.474531] Initializing
