Still have not recreated the crash, I have my latest valgrind log, both logs
show
that a memory error exists. I am continuing to run evince, with no flaws up to
now.
** Attachment added: "latest valgrind log"
http://launchpadlibrarian.net/26455668/valgrind.log
--
evince crashed with SIGSEGV
There have been no subsequent crashes since the initial report. I have
recreated the circumstances of the event several times
with valgrind running, but with no resulting crash. Since I have not been able
to recreate the crash, I cannot attach a log which
contains crash data. I will attach no mor
fire fox browser open to win4lin.com home page
win4lin iso file resident on linux accessable drive with linux file system
viewer open to the folder containing the file.
win4lin pro user's manual downloaded from site and opened in evince
additional tabs opened in firefox browser for google gmail, n
** Description changed:
Binary package hint: evince
I'm sorry this is my first bug report, and my first use of LiveCD ubuntu
9.04. It may not be a valid bug, but I am incompetent to determine
validity. I was reading the installation documentation for win4lin pro
and scrolling with the
Apologies for altering original description.
I still have not recreated the crash.
I will attach the existing valgrind log file for your inspection.
** Attachment added: "log from valgring running evince on suspect machine bug #
367138"
http://launchpadlibrarian.net/26379291/valgrind.log
--
I apologize, I left out some of the kernel description id.s in the above post.
I was trying to update to 9.10 from 9.04.2.6.28-16-generic I had 4 previous
kernels remaining in
the grub menu but .12 did not exist. I tried to load them all in turn,
but none would launch.
I tried to restore ea
Public bug reported:
Binary package hint: update-manager
The error report instructed me to report this bug in update manager. I
am now running on LiveCD 9.04 to make report. Installed version no
longer loads / boots. The system is corrupted, I could not report the
bug before reboot, then reboot f
** Attachment added: "upgradefailure.log"
http://launchpadlibrarian.net/35656338/upgradefailure.log
--
Update failure from Ubuntu 9.04 to 9.10
https://bugs.launchpad.net/bugs/482184
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I did try to boot into the other kernels remaining on my machine. The latest
revision was 9.04.16.
I tried .15, .14. .13.and .11 before I tried any of the recovery modes. I only
used the .16 recovery kernel when
attempting to resolve the issue to allow a successful boot. (I would have tried
gene
Public bug reported:
installation attempt from USB of 11.04 onto a machine running WIN7.
Installer reported existence of 9.04 on system and asked whether I
wanted to upgrade to 11.04, install a clean OS with reformat and one
other option I forgot. I chose to upgrade 9.04 to 11.04. Installation
app
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807815
Title:
installer crashed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/807815/+subscripti
Although upgrade log was not present, that was the option I selected
when I attempted the installation. Crash may have occurred too early to
create upgrade log. I had no idea what the progress of the installation
was. The drive on which the earlier installation was discovered was
added to this mach
I'm sorry, this error may have been caused by trying to write to a
partition that was too small for the installation. It appears that the
9.04 installation crashed a few years ago when I improperly partitioned
the drive. I didn't want to try to repartition & reformat because I had
a working copy of
13 matches
Mail list logo
