Micah,
While I do not support emarkay's tone and heckling (at Bug #481413), I
can confirm that an Apport crash handler does not appear when Firefox
crashes. I have enabled the single instance through force_start as you
suggested but this also did not help.
In addition, I can now confirm that this
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/36774326/AlsaDevices.txt
** Attachment added: "ArecordDevices.txt"
http://launchpadlibrarian.net/36774327/ArecordDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/36774328/BootDmesg.txt
**
Public bug reported:
I am not sure if this is the same as #466454 as I cannot see the
details. As my Karmic upgrade was giving me problems, I did a clean
install and ever since it has got even worse.
Opinion: Karmic is just not as stable as Jaunty was and I really hope
you guys can get a fix out
Public bug reported:
Binary package hint: firefox
This problem has appeared recently though I cannot guess what might have
triggered it. I have been running Karmic since it's release and did not
encounter this problem with any of the previous incarnations on the same
machine. Briefly:
1. Loading
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35552659/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/35552660/XsessionErrors.txt
** Attachment added: "usr_lib_nautilus.txt"
http://launchpadlibrarian.net/35552661/usr_lib_
Public bug reported:
Binary package hint: nautilus
There are similar bugs to this one but as far as I am aware this has not been
reported - so apologies if I have missed something. Other users have also
reported a similar problem here:
http://ubuntuforums.org/showthread.php?t=1306333&page=1
I
#MxxCon - I was pretty skeptical myself after all it has not been
working for a while and I have not really changed anything much. Except
perhaps for explicitly defining the location of my credentials file (it
was in home but it may be possible it was not picking it up at boot). So
just to be clear
I think I am having a similar problem:
I am trying to mount 3 remote shares via /etc/fstab using:
//server-name/share /smb/somefolder smbfs
auto,credentials=smbcredentials,uid=XXX,gid=XXX,umask=000 0 0
Two of these mount just fine while a 3rd does not, causing nautilus to
hang and an ls on /sm
Seems to be working ok as of today - possibly some updates fixed it,
though I wouldn't know which.
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
@Thierry Carrez:
I do get a DHCP address, but the NFS still does not mount. sudo mount -a still
works of course.
Thanks
--
nfs mounts specified in fstab is not mounted on boot.
https://bugs.launchpad.net/bugs/275451
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Thierry Carrez: Sorry for the disappearing act - have been very busy.
The lines in /etc/network/interfaces used to read:
auto lo
iface lo inet loopback
Following ThomasNovin's suggestion, I backed up the original file and
replaced its contents with:
auto eth0
iface eth0 inet dhcp
Rebooting afte
I can confirm the same problem. Looks somewhat similar to Bug #127445
(https://bugs.launchpad.net/ubuntu/+source/compiz-fusion-plugins-
extra/+bug/127445) but that was fixed a while ago. I am using Jaunty and
unchecking the Show desktop option within Scale will "fix" this - by
which I mean the wind
I can confirm the same problem. Looks somewhat similar to Bug #127445
(https://bugs.launchpad.net/ubuntu/+source/compiz-fusion-plugins-
extra/+bug/127445) but that was fixed a while ago. I am using Jaunty and
unchecking the Show desktop option within Scale will "fix" this - by
which I mean the wind
Forgive my complete ignorance, but I am not sure what you mean by
NetworkManager managed network. The NetworkManager applet has been
operational for as far back as I can remember and as I said, nothing has
changed from my end (from Feisty onwards) except the OS version. In
other words, mounting fro
Same problem. This problem has only emerged since Intrepid as I never
had this problem with the previous versions. Sudo mount -a works after
boot every time, so presumably the network is not available during boot.
I have tried re-installing Intrepid but this has not helped.
--
nfs mounts specifie
Public bug reported:
I am using Ubuntu Ibex on a desktop with Compiz on 'normal' effects.
There are some serious issues with power management and I am not sure if
this is due to my setup or something inherent in Ubuntu. These issues
may be summarized as under:
1. The system hangs if left on witho
16 matches
Mail list logo
