Solution works for me as well. Upgraded from Maverick to Natty at RC1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773285
Title:
nspluginwrapper installation fails during upgrade to Natty
--
ubu
@scottywz
Just saw your second comment. domount is a shell function and has been
included from the /lib/init/mount-functions.sh script on line 28.
Please see if the fix at bug 360160 helps you, which is due to a
modified mountdevusbfs.sh script. In case it works, we might have found
out where th
scottywz's workaround was successful. As per bug 360160, I replaced the
mountdevusbfs.sh with the package maintainers version, and it solved the
problem for me.
After seeing the above comments, I checked my incorrectly functioning
mountdevusbfs.sh script which I had backed up, and I confirm that
@Githlar: If you upgraded from an earlier version of Ubuntu, then there
will be a mountdevusbfs.sh.dpkg-dist file in your /etc/init.d/
directory. Create a backup copy of the existing moundevusbfs.sh, and
then replace it with the dpkg-dist file. If you don't have a dpkg-dist
file due to some reaso
I confirm that replacing mountdevusbfs.sh with mountdevusbfs.sh.dpkg-
dist fixed the issue. This was done along with commenting the line in
/etc/fstab.
A side-by-side diff of the two mountdevusbfs is attached. Line 41 of
the file shows that the options for 'domount devpts' have been changed.
Whi
I do remember modifying the mountdevusbfs.sh in my Intrepid install for
a work around needed in VirtualBox. But I also remember asking the
dist-upgrader to replace mountdevusbfs.sh with the package maintainers
version while upgrading to Jaunty. That must be the reason for this
bug.
I'll try what
I do remember modifying the mountdevusbfs.sh in my Intrepid install for
a work around needed in VirtualBox. But I also remember asking the
dist-upgrader to replace mountdevusbfs.sh with the package maintainers
version while upgrading to Jaunty. That must be the reason for this
bug.
I'll try what
** Attachment added: "udev.devices.txt"
http://launchpadlibrarian.net/25462106/udev.devices.txt
--
gnome-terminal does not launch on upgrade to jaunty
https://bugs.launchpad.net/bugs/360160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "udev.log.txt"
http://launchpadlibrarian.net/25462139/udev.log.txt
--
gnome-terminal does not launch on upgrade to jaunty
https://bugs.launchpad.net/bugs/360160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Here are my outputs of /etc/rcS.d, /etc/init.d, /lib/udev/devices and
/var/log/udev. All these outputs are on a system where the /etc/fstab
has been modified and the ptys are now accessible. If you need the
above with no changes to fstab, let me know, I'll post them as well.
** Attachment added:
** Attachment added: "rcS.d.txt"
http://launchpadlibrarian.net/25462002/rcS.d.txt
--
gnome-terminal does not launch on upgrade to jaunty
https://bugs.launchpad.net/bugs/360160
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
*** This bug is a duplicate of bug 321927 ***
https://bugs.launchpad.net/bugs/321927
@Andreas:
As per comment #62 on bug 321927, this bug is not related to that bug,
and hence should be looked into.
I am new here, so will need help. Please let me know any additional
information that you nee
> The original reporter's problem, and most of the duplicates/commentors,
> is caused by running chkconfig/insserv which re-ordered the directory
> incorrectly. This is assumedly a bug in those tools for not obeying the
> Should-Start: udev directive in mountdevsubfs.sh
>
> If other people have th
I confirm scottywz's workaround of adding a line to fstab. I upgraded
from a clean Intrepid install to a Jaunty install on 12/4/09, done by an
alternate cd and getting the latest packages from the net. I noticed
this error as soon as i rebooted after the upgrade process completed.
Simply mounting
I too confirm this bug in Jaunty (development). This only occurs when script
scanning is enabled, ie then nmap is used with option '-sC', which is included
in the option '-A'.
Please let me know if more information is needed about this. Will be happy to
help.
--
nmap script engine run time e
** Attachment added: "output of apport-cli -fp gnome-terminal"
http://launchpadlibrarian.net/25293016/bugreport.txt
--
gnome-terminal does not launch on upgrade to jaunty
https://bugs.launchpad.net/bugs/360160
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
Binary package hint: gnome-terminal
Package: gnome-terminal ( 2.26.0-0ubuntu2 )
Description: Ubuntu upgraded from Intrepid to Jaunty using alternate iso
and the latest packages over the net. After the upgrade completed ( with
one small error in tzdata-java, which was rectifi
Am really sorry! My mistake... As I said, I'd compiled from source...
Will be more careful next time before I post. Thanx for pointing it
out...
--
PSI can't find GPG key [ERROR: This message is encrypted, and you are unable to
decrypt it.]
https://bugs.launchpad.net/bugs/212813
You received th
I confirm the bug on Kubuntu 8.10, with Psi 0.12 (compiled from source
with check install). I was unable use my gpg key with Psi, which I
could do in earlier versions of Psi and Ubuntu (dont remember which
version of Psi though)
The above solution of installing libqca2-plugin-gnupg worked for me
I forgot to add the following in my earlier post...
uname -a
Linux mustang 2.6.24-21-generic #1 SMP Tue Oct 21 23:43:45 UTC 2008 i686
GNU/Linux
Also attaching my lshw
** Attachment added: "Output of lshw by Ninad Pundalik"
http://launchpadlibrarian.net/19274745/lshw.txt
--
system freeze wh
I tried the steps mentioned in the above post on my current Ubuntu Hardy
installation. However, the upgrade in firmware gave me a respite for
only 2-3 weeks and my system started locking up again, just as it used
to before. I could never get uptimes beyond 2 days due to this, and I
always had to
21 matches
Mail list logo
