I located the /tmp subdirectory in which hardy's upgrade lies. I did the
following
$ gksudo python -dv hardy 2[name of debug file]
I then added a few short headers/footers to the debug file to indicate its
contents. I did my best to make it very clear where the headers end and the
debug
When running gksudo python hardy, I get the same behavior I would have
gotten had I done it the traditional, GUI way. On the other hand,
running just gksudo hardy exits almost immediately. On the gripping
hand, when done the traditional way, it appears to be executed (by root)
simply as hardy.
Regarding my most recent attachment (hardy stderr contents):
$ md5sum hardy_err_unedited
7d9a82770bc35ae071d85b16320c8037 hardy_err_unedited
where hardy_err_unedited is the name of the file sans headers. Can
anyone else confirm the same contents (using an md5sum and the
appropriate commands to
So are we going to wait until Gusty is no longer supported and they're
no longer supplied?
--
Upgrade from gutsy to hardy-beta hangs
https://bugs.launchpad.net/bugs/205225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Known vulnerabilities are fixed in gutsy too so not being able to
upgrade to hardy is not a security problem.
** This bug is no longer flagged as a security issue
--
Upgrade from gutsy to hardy-beta hangs
https://bugs.launchpad.net/bugs/205225
You received this bug notification because you are
I have gone ahead and marked it, much later than I thought I would.
** This bug has been flagged as a security issue
--
Upgrade from gutsy to hardy-beta hangs
https://bugs.launchpad.net/bugs/205225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm considering marking this as a security vulnerability per the following
reasoning:
1) There are probably security vulnerabilities in Gusty that are fixed in Hardy.
2) This bug is barring fixes of those /known/ security vulnerabilities.
3) This bug is a security vulnerability, or directly
Just installed an update to update-manager and update-manager-core. It
didn't help
--
Upgrade from gutsy to hardy-beta hangs
https://bugs.launchpad.net/bugs/205225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
my video is now of the correct MIME type. Unfortunately, mozplugger needs to
be modified to work it properly (for some bizarre reason, it didn't support
video/x-theora+ogg). If you have it, try
~$ man mozplugger
to see how to modify it. Obviously, this is quite offtopic and is not a
I made a rather choppy video with Istanbul Desktop Session Recorder.
** Attachment added: Video of the crash
http://launchpadlibrarian.net/13974816/short-upgrade-attempt
--
Upgrade from gutsy to hardy-beta hangs
https://bugs.launchpad.net/bugs/205225
You received this bug notification
Not that anyone cares, but I can vouch that the above screenshot is
real, it has happened to me. Of course, I'm not exactly an established
member of the community, so no one cares about my vouching. Force quit
on the window works, but leaves a background process. End process on
the process,
The real problem is that this is still happening even though it's not
beta anymore!
--
Upgrade from gutsy to hardy-beta hangs
https://bugs.launchpad.net/bugs/205225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I tried
$ gksudo update-manager --dist-upgrade
see screenshot for quite interesting results
** Attachment added: screenshot2.png
http://launchpadlibrarian.net/13917335/screenshot2.png
--
Upgrade from gutsy to hardy-beta hangs
https://bugs.launchpad.net/bugs/205225
You received this bug
I get the exact same behaviour:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 7.10
Release:7.10
Codename: gutsy
$ cat /var/log/dist-upgrade/main.log
2008-04-18 08:20:23,904 INFO release-upgrader version '0.87.18' started
2008-04-18
14 matches
Mail list logo
