I got tired of waiting for this to be fixed, so I implemented a
workaround.
I moved the gedit binary to gedit.bin, then I created a shell-script
named gedit that calls gedit.bin with the --standalone option:
% mv /usr/bin/gedit /usr/bin/gedit.bin
% vi /usr/bin/gedit
#!/bin/sh
/usr/bin/gedit.bin
I got tired of waiting for this to be fixed, so I implemented a
workaround.
I moved the gedit binary to gedit.bin, then I created a shell-script
named gedit that calls gedit.bin with the --standalone option:
% mv /usr/bin/gedit /usr/bin/gedit.bin
% vi /usr/bin/gedit
#!/bin/sh
/usr/bin/gedit.bin
Very nice! Since Scott Remnant has not been responding to bugs with
mountall (eg. Bug #571444) I hope that your solution is used in a future
Ubuntu release.
--
A better mountall
https://bugs.launchpad.net/bugs/614662
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
** This bug is no longer a duplicate of bug 576672
keypress prompt on server bootup
** This bug has been marked a duplicate of bug 571444
Boot hangs and unable to continue when automount disk in fstab
*** This bug is a duplicate of bug 571444 ***
https://bugs.launchpad.net/bugs/571444
** This bug has been marked a duplicate of bug 571444
Boot hangs and unable to continue when automount disk in fstab is not
available (Off or Disconnected)
--
keypress prompt on server bootup
I sent a message to Scott Remnant a couple weeks ago, referencing this
bug. It does not seem to have gotten any attention.
I'm not sure what Ubuntu is coming to when an important bug like this
seems to be ignored by the developers.
--
Boot hangs and unable to continue when automount disk in
It seems to me that mountall must be modified to timeout after X number
of seconds, where timeout means the equivalent of pressing 'S' for
skipping the unmountable volume.
The man page for mountall gives the author as Scott James Remnant
sc...@netsplit.com.
Scott appears to be an employee of
A related bug is #571444.
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/571444
I agree that it is totally unacceptable that a server distribution
should stop with an invisible prompt just because an entry in /etc/fstab
is not able to be mounted.
After a couple months, I do not
This bug bit me also. I had a line in /etc/fstab for an iscsi volume
that was not available at boot time, and the system just hangs during
boot.
Workaround was to put the noauto option on the volume in /etc/fstab.
But I think this is a serious bug. I suspect most Ubuntu users would be
very
Version 3.0.3 is in testing. If you cannot use the 3.1.1 in unstable,
can't Ubuntu at least use the 3.0.3 in testing? Ubuntu is the only major
linux distribution that is shipping with such an outdated version of
mdadm.
--
Please upgrade to 3.1.x for lucid
https://bugs.launchpad.net/bugs/495370
Public bug reported:
Binary package hint: mdadm
Looking at upstream versions
http://www.kernel.org/pub/linux/utils/raid/mdadm/
you can see that the 2.6.7 version that ships with Ubuntu is from mid-2008. The
latest version of mdadm is
3.1.2, and it has many bug fixes and additional features
With karmic, has anyone tried opening sftp:// Open Office documents ?
When I double-click on .xls files on an sftp:// volume, I get:
Could not display sftp://remote/file.xls;.
There is no application installed for Excel spreadsheet files
But the Properties / Open With for the file
I should have mentioned that I am using Free-NX. I think this is
relevant, since I just noticed that there is no file system mounted in
~/.gvfs/ when I access an sftp:// volume with Free-NX.
I tried opening an sftp://.xls file in karmic without Free-NX (just a
local Gnome desktop) and that did
** Changed in: libxrandr (Ubuntu)
Status: New = Confirmed
** Changed in: gnome-settings-daemon
Status: New = Confirmed
** Changed in: freenx-server
Status: New = Confirmed
--
The program 'gnome-settings-daemon' received an X Window System error. During
on a FreeNX server
I can confirm this behavior. I just upgraded my system from jaunty to
karmic, and I found that gnome-settings-daemon would not start when
running a free-nx session. However, g-s-d started properly when I
started a normal gnome session (no free-nx). Then I disabled the xrandr
plug-in, and g-s-d was
I switched my D-Link DIR-655 wireless router from WPA2 authentication to
WEP authentication. I believe this also disabled wireless N protocol
since I don't think N supports WEP (how can I check in Ubuntu what
wireless protocol I am using, n, g, or b?). Since I made the switch, I
have had no
Is anyone looking into this bug? What information does the bug team need
that has not been provided?
I have a Dell Inspiron 1720 with an Intel 4965 AG wireless card
0c:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or
AGN [Kedron] Network Connection (rev 61)
*-network
Here is someone else who appears to experience the same bug:
http://ubuntuforums.org/showpost.php?p=6362798postcount=1
--
Intel Pro/Wireless 4965 AG stops transferring data within a few minutes
https://bugs.launchpad.net/bugs/277634
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 282939 ***
https://bugs.launchpad.net/bugs/282939
** This bug has been marked a duplicate of bug 282939
gnusound crash in Intrepid Ibex Beta
--
GNUSound crashes immediatly when executed.
https://bugs.launchpad.net/bugs/303226
You received this bug
*** This bug is a duplicate of bug 282939 ***
https://bugs.launchpad.net/bugs/282939
** This bug has been marked a duplicate of bug 282939
gnusound crash in Intrepid Ibex Beta
--
X (nvidia) crashes when starting GNUsound
https://bugs.launchpad.net/bugs/300148
You received this bug
I am also experiencing identical crashes to greyor. I just installed
gnusound and have never successfully run it before.
--
gnusound crash in Intrepid Ibex Beta
https://bugs.launchpad.net/bugs/282939
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I experienced this bug installing 8.10 server amd64 release from CD.
Judging from Tim Gardner's fix, the problem is that igb module is
missing.
Is there a workaround that I can specify during the install to get it to
work, until Tim's fix is available? When will Tim's fix make it into the
CD
After the recent pulseaudio update, my snd_hda_intel sound also stopped
working -- just a low crackling sound.
I tried the alsamixer -Dhw trick, and sure enough, PCM volume was at 0.
I turned PCM volume up to max and now my sound plays normally again.
However, I think the PCM volume 0 is just
Also see these similar bugs:
#288652
#288093
#288039
#286966
#286430
#285965
--
no sound HDA-intel AD1984
https://bugs.launchpad.net/bugs/288861
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I had a similar problem. There was a partial workaround to get sound working
again here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288861
where alsamixer -Dhw revealed that the PCM volume was at zero, and turning it
up restored
sound operation. I still have the problem that my
I had a similar problem. There was a partial workaround to get sound working
again here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288861
where alsamixer -Dhw revealed that the PCM volume was at zero, and turning it
up restored
sound operation. I still have the problem that my
There was a partial workaround to get sound working again here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288861
where alsamixer -Dhw revealed that the PCM volume was at zero, and turning it
up restored
sound operation. I still have the problem that my system hangs during
I had a similar problem that may be related. I first noticed that my sound was
not working
after a pulseaudio update. There was a partial workaround to get sound working
again here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288861
where alsamixer -Dhw revealed that the PCM
I had a similar problem. There was a partial workaround to get sound working
again here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288861
where alsamixer -Dhw revealed that the PCM volume was at zero, and turning it
up restored
sound operation. I still have the problem that my
I had a similar problem. There was a partial workaround to get sound working
again here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/288861
where alsamixer -Dhw revealed that the PCM volume was at zero, and turning it
up restored
sound operation. I still have the problem that my
I have the exact same problem as Reece Dunn, on a Dell inspiron 1720.
After the update today, the speaker was muted. Now when I unmute it, the
only noise that can be played is a crackling sound -- nothing
intelligible.
--
[intrepid] alsa is broken
https://bugs.launchpad.net/bugs/280534
You
Another symptom of the recent broken ALSA sound is that when I shut
down, the system hangs while trying to shut down ALSA.
I tried Yuval Tal's suggestion and edited
/etc/X11/Xsession.d/70pulseaudio
to comment out the code that loads pulseaudio. Then I rebooted, and ALSA
sound is working
I have the same problem. After the upgrade and reboot, sound was muted.
When I unmuted it, then the only sound that could play was a low
crackling sound. Also, when I shutdown, the shutdown process hangs while
trying to halt ALSA.
I was able to get my sound playing again by commenting out the
33 matches
Mail list logo
