Update: I'm not sure at what version this changed, but now the system
requires acpi=force to shut down as expected even on the 386 kernels.
I Just installed the latest kernel update (it says Sept. 8 in dmesg)...
On this old 500 MHz machine I wondered if I was seeing any benefit from
the 686
Thanks for the follow-up... it will be another few weeks before I have
time to attempt the Dapper upgrade on this system.
(If I have enough time, I might also attempt a separate clean install,
which won't be straightforward because it's an oldworld Mac.)
--
laptop-mode doesn't start
I'll add a me too -- prior to the Dapper release, the changelogs
usually appeared in the update-notifier window. Since the release, the
text area for the changelog refreshes for each package, but the text
area contains nothing (blank). The package description panel, on the
other hand, continues to
Sorry, I must have been posting at the same time. The behavior I am
seeing is different from the links above -- I am NOT seeing the The
list of changes is not available yet. Please try again later. message
in the text area so mine must be a separate bug ?
--
update-manager shows no changelog for
I further suggest it would be helpful if the imagemagick html docs get
registered in scrollkeeper so they appear in the Ubuntu online docs
(though I realize they are not formatted in a way that makes it easy).
--
imagemagick: manpage of convert refers to nonexistent file
I can confirm that with the deb-src lines disabled the correct text
appears in the Changes tab. I'm looking at the gnupg update right now.
--
update-manager shows no changelog for various packages
https://launchpad.net/bugs/40058
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thanks for the timely reminder. I just upgraded my Wallstreet from
Breezy to Dapper (a painfully slow ordeal!), but I can switch among VTs
perfectly now!
So for ME, this works great now.
--
No Virtual Consoles after Upgrade to Breezy
https://launchpad.net/bugs/25701
--
ubuntu-bugs mailing
I just did an upgrade from Breezy to Dapper, and the update-manager
showed me a list of items from universe that are no longer supported and
it removed them for me. However, I DO have universe enabled, so maybe
this is not exactly the same?
--
[dist-upgrader] When doing a dist-upgrade to Dapper
Good news -- I finally went through the (painfully slow) Breezy-Dapper
upgrade on my Wallstreet this past week, and now laptop-mode seems to
work great!
The config is so very different from before I couldn't diff it easily so
I just puzzled through and saw that it's set up just about where I want
I just upgraded to Edgy Eft and the stock 386 kernel can successfully
power the system down using the shut down menu. HOWEVER, pressing the
power button still kills the power (rather than bringing up the
shutdown/logout menu).
When I get a chance, I will burn an Edgy CD and do some more playing
a highly regarded setup guide (includes client side details but server
side is for Debian / Ubuntu):
http://taksuyama.com/?p=13
--
Documentation not Debian-ized / Ubuntu-ized
https://bugs.launchpad.net/bugs/17316
You received this bug notification because you are a member of Ubuntu
Bugs, which
I just tried the Dimension E510 again with an Intrepid desktop 8.10
amd64 beta disk. The first attempt, I couldn't even use the Shift key
workaround, but after a power down and restart, the desktop disk worked
fine with my USB keyboard adapter.
--
USB Keyboard not working
Thank you for passing my concern upstream!
In reading the upstream bug status at
http://www.openoffice.org/issues/show_bug.cgi?id=87445 I was a little
confused. It says:
The document contains page bound frames. This is not supported in mail merge
as
it is not (easily) possible to find the
Public bug reported:
Binary package hint: openoffice.org
Ubuntu 7.10 Gutsy, OpenOffice.org 2.3.0
OpenOffice Writer completely ignores text in tables when comparing
documents. I have several large documents where ALL the text is in
tables, so I cannot search for changes among them. If I convert
I will confirm the usb: setting works very well with jpilot and I just
tried it and it works with gnome-pilot too.
--
Can't sync Treo 650 with Jpilot / Ubuntu
https://bugs.launchpad.net/bugs/116885
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
sorry for the delayed response --
Unfortunately the Dapper system is totally different hardware from the
newer system -- it's Dapper 6.06.1 running on a 266 Mhz PowerBook G3 and
the newer system (since upgraded to Gutsy) is a 550 Mhz Pentium PC.
If anything the Firewire cable may be LONGER on
*** This bug is a duplicate of bug 85291 ***
https://bugs.launchpad.net/bugs/85291
The situation I described is similar to the other bug, HOWEVER what
about NON ext file system troubles? --
I'm using external drives which I have formatted as ext3, but they could
just as easily be formatted
I have a Western Digital MyBook Premium that I bought at Target. The
included cable destroyed the Firewire ports, and they sent me a new
cable in the mail, so I exchanged the original drive at the store and
have used only the cable they mailed me with that drive. My failures
have occurred on OTHER
bug accidentally applied to Gutsy Backports; I chose a more likely linux
package instead
** Also affects: linux-backports-modules-2.6.22 (Ubuntu)
Importance: Undecided
Status: New
--
linux-backports-modules server flavour missing alsa driver
https://bugs.launchpad.net/bugs/193639
You
not a request for inclusion in Gutsy Backports
** Changed in: gutsy-backports
Status: New = Invalid
--
linux-backports-modules server flavour missing alsa driver
https://bugs.launchpad.net/bugs/193639
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes, it still happens. I sanitized (semi-anonymized) the source
document, then created a data file with nine fake addresses, and merged
it, creating the same result. When I merge this document, I see two
copies of each image in the output file, with the duplicate image
floating near the top of
** Attachment added: Tab-delimited text file with addresses
http://launchpadlibrarian.net/10369064/Addresses%20Sanitized.txt
--
Merged document spawns duplicate graphics
https://bugs.launchpad.net/bugs/121611
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: Database document linked to address text document
http://launchpadlibrarian.net/10369078/Addresses%20Sanitized.odb
--
Merged document spawns duplicate graphics
https://bugs.launchpad.net/bugs/121611
You received this bug notification because you are a member of Ubuntu
correction -- there are nine rows in the data document; only eight fake
names and addresses. These names and addresses are fictitious and are
not intended to refer to any person, living or dead. ;-)
--
Merged document spawns duplicate graphics
https://bugs.launchpad.net/bugs/121611
You received
** Attachment added: Spreadsheet containing addresses
http://launchpadlibrarian.net/10369069/Addresses%20Sanitized.ods
--
Merged document spawns duplicate graphics
https://bugs.launchpad.net/bugs/121611
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Better templates (as well as other features in these extensions) are
definitely needed in OpenOffice.
I have been curious regarding the licensing, etc. -- what's keeping them
out of the standard release? The extensions are also listed on the
OpenOffice pages at SUN:
I'm not the original bug reporter, but I stopped using my FireWire
drives under Ubuntu 7.06 because in every case the drive would work at
first and then become unreliable and then become unusable. HOWEVER I
found that I could still access the data from an old machine still
running Ubuntu Dapper
Quixwallah: It sounds like you have one or more automatix repositories
in your sources.list -- if commenting out that line doesn't work, you
may want to try a fresh installation to rule out any problems with non-
official Ubuntu packages. (Makes it much harder to track down when the
software might
In the mean time, is there a noob way for users to patch if they need
this option?
The patch is to format the storage device using a different file
format, such as ext2 or ext3. VFAT cannot handle files larger than 4GB.
The linux and gnome utilities need to handle the situation more
gracefully,
Public bug reported:
Binary package hint: netatalk
I've been running Netatalk on a system since it was running Dapper 6.06
or Edgy 6.10. Now I'm running Gutsy 7.10 and noticed Netatalk doesn't
start at boot, though it starts readily when invoked manually using
sudo /etc/init.d/netatalk start
It seems the powerpc image is not yet available for the Hardy release.
I'll try to update this report when it's ready.
I believe the current daily build is always at this url:
http://cdimage.ubuntu.com/ports/daily/current/
(But this is the alternate CD and maybe you are looking for the live CD
I had a few minutes today to tinker with this ... I added an echo
message to the second line of /etc/init.d/netatalk so I could look for
any sign that the netatalk script is being invoked but dying early. I
never saw it, nor is it logged anywhere. (and yes, there is a link from
OK now I see that the logd isn't working, as described in Bug #98955
--
netatalk silently fails to start at boot, manual start OK
https://bugs.launchpad.net/bugs/176472
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: hwdb-client
I open the Hardware Testing app, and get the opening page with a Next
button. I click the button, and a progress bar appears saying it's
building report. There's a field at the bottom with a place to enter
my launchpad email. It says it's
oops sorry forgot to mention this is Ubuntu 8.04 hardy heron with all
the updates applied.
--
Hardware Testing provides no manual tests or feedback
https://bugs.launchpad.net/bugs/243096
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am not certain I understand... I am not familiar with any packages
that would modify inittab, so if I'm missing something please let me
know.
I just looked and there appear to be no additions to /etc/inittab -- it
seems to contain only the ordinary sections for default, boot-time,
runlevel,
clarification -- apparently I removed all but the first echo message,
and the script is stock except for one line I modified and annotated.
--
netatalk silently fails to start at boot, manual start OK
https://bugs.launchpad.net/bugs/176472
You received this bug notification because you are a
reading back through this bug I noticed that I HAD already found
/usr/share/doc/upstart/README.Debian.gz back in December but obviously I
had forgotten it, and apparently adding --debug to the kernel parameters
didn't make anything any clearer. My current guess is there's something
about the
I am realizing I don't understand at all how upstart knows what to
start and how and when, so I have started by reading
http://upstart.ubuntu.com/wiki/ and while most of the links at the end
are broken, the last link (not broken) is the most useful --
Public bug reported:
Binary package hint: partman-partitioning
(I'm not sure if this is partman or the installer) when doing a new
Hardy 8.04 install from the Desktop CD, on the screen with the default
automatic dual-boot partitioner, it's not immediately obvious you can
drag the partition size
Last night it occurred to me to try installing sysvinit (to replace
upstart) and sure enough, netatalk started at boot when sysvinit is
installed. I then put the system back to its previous state (with
upstart instead of sysvinit), and netatalk no longer started on boot.
When you apt-get install
Last time I tested it the problem still exists using the 686 kernel on
my machine. Using the 386 kernel, it brings up the dialog and shuts the
system down properly. Using the 686 kernel the powerbutton kills the
power.
My workaround for this is to add acpi=force to the boot parameters when
using
Thank you for the feedback... my observation was as stated -- whatever
might have been in /tmp seemed insignificant compared to whatever was
going into /var/backup.
I believe I have several individual files that exceed the free space on
my root volume, so I suspect that the process(es) gzipping
I haven't tested Feisty yet (unfortunately I have been relying on a LiDE
30 scanner) but as I've followed the progress of this bug I wondered if
someone could try rolling the keep the USB port open hacks into the
scan button daemon http://scanbuttond.sourceforge.net/ That way the
hack could be
This happened to me on a system running Ubuntu 6.10 (edgy) -- haven't
tried it yet under 7.04. I am creating the tar file on an external
ieee1394 (firewire) drive with the manufacturer's FAT32 formatting.
Under Edgy, Archive Manager put up a dialog saying an error occurred
while writing the
Sadly, I'm afraid this is a duplicate of Bug 70535 -- you cannot put a
file bigger than 4GB on a FAT32 volume.
--
Tar is crashing on FAT32 writing
https://bugs.launchpad.net/bugs/72756
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
It would be nice if tar didn't crash, but told you the file reached the
filesize limit of FAT32.
--
Tar is crashing on FAT32 writing
https://bugs.launchpad.net/bugs/72756
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
This bug will be affected by the outcome of Bug 75574 -- namely Nautilus
will need to react appropriately when the cp fails due to a filesystem
limit. I don't know how (or whether it's appropriate) to mark it as
dependent upon another bug.
--
nautilus crashes when copying a 4G file on a vfat
I have been using an external drive formatted with ext3 for about a year
through several Ubuntu releases, and because I shut down that system
almost every night, I find that about once a month the drive won't mount
and I have to fsck it before it mounts normally -- you can see the too
many mounts
I noticed this was still open, but the bug was accidentally reported
against RasMol so the original bug is invalid.
** Changed in: rasmol
Status: New = Invalid
--
MOL needs to be nicer under newer kernels
https://bugs.launchpad.net/bugs/4578
You received this bug notification because you
Thanks to everyone who has worked on the update(s) in time for Gutsy!
Getting into the main repository could improve the ongoing status of
GnuCash in Ubuntu. Here's a page describing how to get a package
promoted to the main repository:
https://wiki.ubuntu.com/UbuntuMainInclusionRequirements
--
Public bug reported:
Using an external USB drive with ext3 filesystem. After awhile it won't
mount, so I check dmesg and see that it's complaining of excessive
mounts without a filesystem check. (I already filed Bug #134425 saying I
wish Gnome would report filesystem errors.)
I tried to use
Forgot to mention -- this us Ubuntu 7.10 Gutsy, recently upgraded from
Feisty but all current updates applied.
--
gparted segfaults trying to fsck ext3 external drive
https://bugs.launchpad.net/bugs/159569
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
A discussion in the forums generated a few useful links and a couple of
suggested HOWTOs for installing BackupPC. Some information from these
might be incorporated in improved documentation.
http://ubuntuforums.org/showthread.php?t=80904
--
Documentation not Debian-ized / Ubuntu-ized
This is a very much used application. Why is it not up to date?
I believe it has no official sponsorship in Ubuntu -- which is why it's
in Universe rather than the standard repositories. There may be
technical reasons for this or there may just not be a certified Ubuntu
packager willing/able to
Confirming this behavior on a Compaq Presario 5304. Gigabyte Motherboard
GA-5SMM. Went to http://www.gigabyte.com.tw/ and updated the BIOS to the
latest version, no improvement.
--
PS/2 mouse port not working with SiS chipsets on Feisty
https://bugs.launchpad.net/bugs/108221
You received this
Earlier today I used the flaky firewire drive and it worked fine.
Tonight (hours later) it didn't come up. I logged out and back in but
have NOT rebooted linux.
I am attaching information for the same drive when it's FAILING.
[EMAIL PROTECTED]:~$ id
uid=1000(twt) gid=1000(twt)
** Attachment added: gvm.log from a FAILING feisty test
http://launchpadlibrarian.net/9250592/gvm.log
--
Flaky firewire disks Fail Feisty but Do Dapper
https://bugs.launchpad.net/bugs/134396
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
NOTE I'm following the directions at
https://wiki.ubuntu.com/DebuggingRemovableDevices but for the FAILING
device, the udev log was empty, and there were no /dev/sd* devices, so
I'm not attaching those empty files.
** Attachment added: lshal from a FAILING Feisty test
As I mentioned, the Ubuntu box had been running all day without a
reboot. The Firewire drive has been turned off most of the day. (I used
it earlier, umounted the partitions, and turned it off. When I turned it
on tonight, it would not mount.)
I just rebooted the Ubuntu box (without powering it
** Attachment added: gvm.log from a WORKING feisty test
http://launchpadlibrarian.net/9079205/gvm.log
--
Flaky firewire disks Fail Feisty but Do Dapper
https://bugs.launchpad.net/bugs/134396
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: udev.log for a WORKING Feisty test
http://launchpadlibrarian.net/9079214/udev.log
--
Flaky firewire disks Fail Feisty but Do Dapper
https://bugs.launchpad.net/bugs/134396
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: lshal from a WORKING Feisty test
http://launchpadlibrarian.net/9079202/lshal.txt
--
Flaky firewire disks Fail Feisty but Do Dapper
https://bugs.launchpad.net/bugs/134396
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Attachment added: dmesg from a WORKING test of feisty
http://launchpadlibrarian.net/9079198/dmesg.txt
--
Flaky firewire disks Fail Feisty but Do Dapper
https://bugs.launchpad.net/bugs/134396
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I recently discovered https://wiki.ubuntu.com/DebuggingRemovableDevices
so I figured I would add that information to the bug report.
Strangely, TODAY the firewire drive is working fine in Feisty
But I will add the information as listed with the note
Information from a WORKING test:
[EMAIL
I noticed your bug because I'm having a problem with a Firewire/ieee1394
drive, but I just switched to a new MyBook because I'm hoping it will be
more reliable. So far so good
I'm noticing your dmesg and uname -- are you using a custom kernel?
Does the drive work properly and/or show
I noticed your bug because I'm having a problem with a Firewire/ieee1394
drive, but I just switched to a new MyBook because I'm hoping it will be
more reliable. So far so good
Have you tried the USB port to see if it works?
ALSO, I had a problem with my Western Digital MyBook Premium Edition
Public bug reported:
I have an external Firewire/USB enclosure -- a MacAlly PHR-100AC
enclosure containing a Maxtor DiamondMax Plus 9 200GB ATA/133 HDD. I
have it formatted with three ext3 partitions (two large, and one small).
I copied my working data from my old PowerBook G3 Series
information from Feisty system where firewire drive fails after being
plugged in:
[EMAIL PROTECTED]:~$ uname -a
Linux emonster 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686
GNU/Linux
[EMAIL PROTECTED]:~$ lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host
One additional comment/question -- I don't know how a server
installation of Ubuntu would handle a firewire drive. It might be
relevant because that's actually how I'm using this one, and it's a bit
annoying to have to log in to get whatever process in Gnome kicks off
the removable drive
Public bug reported:
If the OS finds a problem with the filesystem on a removeable drive, it
would be really nice to have a notice that pops up in Gnome to tell you
about it. Actually it might be nice to get a notice about any filesystem
errors, SMART status, or whatever seems to be an important
Here's the information from the PowerBook running Dapper aftern
connecting and mounting the Firewire drive successfully.
[EMAIL PROTECTED]:~ $ uname -a
Linux pbg3 2.6.15-28-powerpc #1 Wed Jul 18 22:51:07 UTC 2007 ppc GNU/Linux
[EMAIL PROTECTED]:~ $ lspci
:00:00.0 Host bridge: Motorola MPC106
While trying to get back up and running using my restored data, the NEW
drive on Feisty started acting flaky. As I was making a copy of the data
(first with cp then with rsync so I could monitor it more easily) the
drive kept seeming slower and slower. I saw no relevant messages on
dmesg or
Another data point -- on June 15, 2007 I had another Firewire drive die
on Feisty (30GB laptop drive in a MacAlly PHR-250CC enclosure), but I
assumed it was just its time to go. It suddenly went from working
perfectly to being totally unresponsive on the same Feisty system, so I
assumed the drive
I just mounted the new drive (Western Digital MyBook Premium) using
the USB port instead of firewire, and it shows no problem. I ran fsck
and it said no errors. So I'm again trying to get back up and running
using my data, this time using USB. I'm copying the files now, and it's
copying MUCH
The problem described in Bug #85488 is due to a change in the USB driver
in the kernel, and that's what the scanbuttonsd fix is about (it keeps
the USB port from sleeping on the job). HOWEVER this effect was not
noticed in Edgy or Dapper, so if you're having the grinding noise in
those releases
Public bug reported:
Binary package hint: openoffice.org
I created a newsletter using OpenOffice Writer in Feisty. On one side of
the page (separate one-page document) I wanted to merge an address
database. (The outside of the mailing.) To spice up the appearance, I
installed the Open Clipart
Public bug reported:
Binary package hint: openoffice.org
Was creating a newsletter in OpenOffice in Feisty. I typed the 154 rows
into a table in Writer for ease of editing, but when it came time for
merging, I needed to convert the data before I could register the data
in the database component
Actually to be slightly clearer -- the nine-digit ZIP codes were NULL
when you looked at them in the Data Sources table from within Writer --
they were gone even before attempting the merge process, but of course
that's when I noticed them missing.
--
ZIP column from spreadsheet wrong database
Also I meant to say the first row contained a FIVE digit zip code -
74133 -- and I presume that's why the column was assigned an INTEGER
data type.
--
ZIP column from spreadsheet wrong database type
https://bugs.launchpad.net/bugs/121615
You received this bug notification because you are a
confirming that Inkscape 0.45.1-1ubuntu3 builds installs and runs on
Feisty i386 using prevu
--
Backport Inkscape to 0.45.1-1ubuntu3 to feisty
https://bugs.launchpad.net/bugs/96586
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
i will confirm the gutsy package builds using prevu in feisty i386 but I
cannot properly test it at the moment.
--
backport gnash 0.8.0~cvs20070611.1016-1ubuntu2
https://bugs.launchpad.net/bugs/120990
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
adding my note of agreement that the current arrangement is a problem --
I have tried using the hwdb several times since the nice GUI was added,
and the vague adminishment that you might have sent a broken file is
very frustrating, especially when submitting data for a malfunctioning
machine.
--
Public bug reported:
Binary package hint: gparted
I wanted to create a FAT-16 partition on a USB stick and pulled up
gparted on this Ubuntu 9.04 Jaunty system. I THOUGHT I had chosen
/dev/sdc or whatever the USB stick had come up with, but apparently I
still had /dev/sda selected.
Being
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37422305/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/37422308/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/37422311/ProcStatus.txt
--
gparted
@jslater: from earlier tests it seemed it did not affect everyone, or at
least not equally. For example, I have an ASUS EeePC 900 (4GB SSD, no
built-in webcam, purchased from Target) and I see the problem very
clearly on my Patriot Lite upgraded SSD but not on the stock ASUS 4GB
SSD. I haven't
and I finally got Debian up and running on an SD card -- no desktop,
just the terminal. What a PAIN. I'm hoping to start testing with
badblocks soon. I just hope I can get the SSD to fail in a way I can
test it.
I suspect this may be the same underlying bug as
I have been using the release for an hour or so daily for several weeks.
I believe this problem is much less noticeable but not completely fixed,
and probably will blow up worse again with time. This past weekend I
noticed Evince wouldn't open. I cannot remember the last time I used
Evince on this
@Diminik: Thanks for the suggestions. I know an expert could learn more
about it with some write and read tests, especially using the earlier
beta releases where the installation failed every time. I don't think I
saw it at any of the links in my comment above, but somewhere I was
reading that
you asked in Bug 445852 if this might be a duplicate of that bug; try
the workaround listed in comment 136
https://bugs.launchpad.net/linux/+bug/445852/comments/136 (though
there's a typo) -- here it is, corrected:
1) Run the following command. It renames the existing file to devkit-
I suspect base is intentionally left out of the dependencies because it
would make Ooo too big to fit on the standard CD. Given that situation,
Ooo Writer should inform the user of the need for base and/or queue the
package(s) for retrieval in the installer.
SO it's probably much more complicated
Public bug reported:
Binary package hint: mozplugger
After upgrading my ASUS Netbook to Ubuntu Karmic 9.10 and installing
mozplugger version 1.12.1-1ubuntu1 I noticed that the pdf documents I
open from the web nol onger get embedded into the browser window. Under
Ubuntu Jaunty 9.04, installing
I forgot to add that laptop is running Ubuntu 9.10 NBR (Netbook Remix),
in case that makes a difference.
--
mozplugger needs addition to embed pdfs into Firefox using Evince in Karmic 9.10
https://bugs.launchpad.net/bugs/499227
You received this bug notification because you are a member of
also I wrote upgraded but this is a clean install.
P.S.: Since adding this I have had a few instances of Evince complaining
it had crashed and offering to rescue the documents where I had only
closed the browser window.
I am wondering if the new evince command in mozpluggerrc needs an
additional
I just completed a fresh install using Ubuntu Karmic 9.10 NBR release
version, except I chose to format the root partition as ext3 instead of
ext4. On reboot, I get the rescue:grub prompt.
I imagine the filesystem is as hosed as before, but I'll leave it a
couple of days in case someone wants to
@Dominik: If you have a recommended distro that is known to work well on
an ASUS netbook, I can certainly try it. All the ones I have tried on it
so far (other than its stock Xandros) have been Ubuntu-based. (I started
with the one now called Easy-Peasy, and also Eeebuntu, and maybe one
other I'm
@Dominik: OH and I don't know what Default BIOS options you are
suggesting -- there aren't many I have changed on this unit. It has been
a few weeks since I have reverted to Ubuntu Karmic 9.04 NBR, but I fully
expect it to work as it did before. (Boots quickly; No noticeable
corruption; Most
I just replaced the 32gig upgrade SSD with the original 4gig SSD and ...
WOW. It works great (so far)
Much faster boot. No noticeable corruption. No long pauses with the disk
activity light on. Given the good performance I don't anticipate finding
any corruption, but I will try a few things
@shadowblast101: As per the eeeuser thread mentioned above, have you
tried zeroing out the SSD?
Boot from a Live distro on a USB key or SD card and issue the following
command at a terminal prompt:
dd if=/dev/zero of=/dev/sda bs=1M
(Oh, and it might make sense to be absolutely sure your SSD is
My comment to shadowblast101 was so he might rescue his drive by
writing zeroes to it (so the regular utilities won't barf when they look
at it)...
I looked into how to use dd to write different patterns -- the trick is
to pipe the output of /dev/zero through /usr/bin/tr to convert to
whatever
1 - 100 of 492 matches
Mail list logo
