Public bug reported:
Automated upgrade failed
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apache2 2.4.7-1ubuntu4.1
Uname: Linux 2.6.32-042stab092.3 i686
Apache2ConfdDirListing: ['zz010_psa_httpd.conf', 'php_cgi_wrapper.conf']
Apache2Modules:
Error: command ['/usr/sbin/apachectl',
Public bug reported:
newest release - I can update anything !
gnome, because of slow graphic
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: exim4-config 4.76-3ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/997553
Title:
package exim4-config 4.76-3ubuntu3 failed to install/upgrade:
subprocess installed post-installation script returned
Public bug reported:
(German)
Neuinstallation, weil viele Pakete nicht mehr aktualisiert werden konnten.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: exim4-daemon-light 4.76-3ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-19.33-generic 3.0.27
Uname: Linux 3.0.0-19-generic x86_64
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/994981
Title:
package exim4-daemon-light 4.76-3ubuntu3 failed to install/upgrade:
ErrorMessage: dependency problems - leaving
I can reproduce it on Lucid and Maverick under the following conditions:
- the network is a WLAN
- the connection is made by Network Manager or WICD
I don't know what the condition net-device-up IFACE!=lo in
/etc/init/nmbd.conf is really needed for. Can it be recommended to leave
it out and to
I had already mentioned above: It's not only a network-manager problem
because it is exactly the same with WICD.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you
I absolutely do agree with Tom and varanasi. This is a serious usability
problem that should be fixed as soon as possible!
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification
** Attachment added: .etc.apparmor.d.usr.sbin.mysqld.txt
http://launchpadlibrarian.net/39090679/.etc.apparmor.d.usr.sbin.mysqld.txt
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/39090680/AptOrdering.txt
** Attachment added: Dependencies.txt
Public bug reported:
/var/cache/apt/archives/mysql-server-5.1_5.1.37-1ubuntu5.1_i386.deb:
Unterprozess neues pre-removal-Skript gab den Fehlerwert 1 zurück
Error 1 from pre-removal-script
ProblemType: Package
Architecture: i386
Date: Fri Feb 12 09:07:14 2010
DistroRelease: Ubuntu 9.10
Not fixed for wireless network with WICD too !
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
An other important reason is that gvfs does not support cifs UNIX
Extensions yet.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server
sorry, i completely forgot about this bug...
so my initial bug report was in march now its october, the bug is long
gone and i run karmic now. this bug occured in the develelopment of
jaunty...
please feel free to clos this bug!
--
php5 crashed with SIGSEGV in start_thread()
Thanks for this status update.
As Thuerry Carrez proposed, I tried to avoid system wide CIFS mounts via
fstab by monting my cifs shares manually with mount.cifs ... in my
home folder. The shutdown problem is still the same.
Using GNOME vfs pseudomounts is not a solution for me because the cifs
I have the same problem, but I had never used Network Manager. I always
use WICD.
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba
Public bug reported:
Using Intrepid's OpenSSH, I cannot connect to my 3Com network devices;
the connection simply fails after login.
I have done some research, and it seems that I'm hit by the same bug as
described in Debian #495917. I patched ssh 1:5.1p1-3ubuntu1 with the
patch from
I was not at home last week. Sorry for not answering sooner.
Thierry Carrez is right; the bug seemes to be fixed now. I have done
nothing else but installing the usual updates, and public shares now do
work in Hardy as well as in Intrepid.
Thanks, Max
--
Public shares not possible in home
I am sorry. I never wanted to speak for others. It is my opinion, but it
would be better if I had said nothing at all.
considering scripts existed already and were simply executed at the
wrong stage of the shutdown sequence
Do these scripts really fix the problem? Please read the posting of
I am afraid the problem is that in this case nobody really feels
responsible. Is it a problem of the shutdown sequence (Ubuntu problem),
of the cifs Kernel module (Linux general) or a Samba bug? Who has got to
fix it?
As long as nobody feels responsible there is not much hope indeed.
--
@ luchio
We are already waiting for years, and nothing did really happen. It is a
shame.
Even if it is far from being a perfect solution, it is better to propose
a workaround like the script of Scott Severance than to do just nothing.
--
CIFS/SMBFS shares not unmounted before network is shut
@ Mathias Gug
Is that what you did need?
Perhaps that can help you: Public shares inside a directory (in this
case it is /home/farber/) are possible only if the access to the
*whole* directory is allowed for everyone. This is not normal. It should
be enough to allow access to the share. It had
What do you actually mean by configuration section? The few lines for
the share only or the [global] part also?
[Gemeinsam]
path = /home/farber/Gemeinsam
available = yes
browsable = yes
public = yes
writable = yes
The share is not accessible at all even if /home/farber/Gemeinsam is
set to mode
mv /etc/rc0.d/S31umountnfs.sh /etc/rc0.d/S14umountnfs.sh
mv /etc/rc6.d/S31umountnfs.sh /etc/rc6.d/S14umountnfs.sh
This fix is a rather old thing; it had been published more than two
years ago.
I had asked here if this solution was correct and really safe, but I did
not get any answer yet!
This annoying bug is known for a very long time now. I wonder why
nothing has been done yet!
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I agree with flaccid: This perpetuating and ennoying bug should be fixed
as soon as possible!
That has even become more important with Hardy, since smbfs does not
exist as a workaround any more, smbmount being nothing more than a
wrapper for mount.cifs.
The simple solution proposed in the link
This is a very old and well known problem. See also
http://ubuntuforums.org/showthread.php?t=772774 and
http://ubuntuforums.org/showthread.php?t=293513highlight=cifs+vfs
I wonder why this bug is not fixed yet!
It has been proposed to change S31umountnfs.sh to K14umountnfs.sh in
/etc/rc0.d and
26 matches
Mail list logo
