I am now using Jaunty, so can't comment on anything Intrepid any more.
Sorry.
Network Manager has been a real pain generally disrupting all DHCP, NIS,
DNS, etc. Having changed Network Managers' start number to something
big most of the problems go away, which is why I haven't been hassling
--
The workaround for this is well known but is not really explained
anywhere in any one place; there are comments on all the bugs related to
this one (especially 354588) and also in the Ubuntu forums. What is
comes down to is the ordering of startup of NIS and NetworkManager. If
NetworkManager is
I am an Ubuntu fan but this bug in the dapper - edgy distribution
upgrade really, really, really annoyed me. If upgrade-manager -c
depends on python-vte then it should test for the presence of this
package before starting -- and tell people to install it if it is not
there.
installing python-vte
Maybe I am just seriously irritated presently having been hit by this
problem but I recollect there was a message saying there was going to be
an issue with courier-authdaemon during the early stages of the upgrade
so why couldn't there have been a message telling me how to get round
the problem.
Public bug reported:
Binary package hint: ant
If you only install the ant package and not the ant-optional package
then the xslt taks fails:
[xslt] DEPRECATED - xalan processor is deprecated. Use trax instead.
[xslt] DEPRECATED - xslp processor is deprecated. Use trax instead.
It seems that using the keys to set the brightness leads to a temporary
change of brightness. There is some time out that then resets the
brightness to the level determined by the applet on the panel. I would
suggest this is an error not a feature. Is it deserving a new bug
number or does this
As noted in my duplicate report #156157, I encountered this problem when
upgrading a server not a workstation -- I upgraded the workstations with
upgrade-manager as is recommended and had no problem. The server I
upgraded with do-release-upgrade which is the recommended mechanism for
upgrading a
Public bug reported:
I have just tried to install Gutsy from the standard Live CD on a Sony
Vaio OCG-SRX51P/B. The Live CD fails to boot into a sensible state --
blank screen. I tried the safe mode and it did boot to a usable state
(though the screen is 640x480 so most of the controls are not
I recently tried to install Gutsy on this machine and that was
essentailly a disaster -- Gutsy appears unable to boot from the install
CD-ROM (cf. Bug #141646) and if an installation is forced via doing a
safe boot, it only works in 800x600 mode. I therefore reinstalled
Feisty from my original
Is this the same problem as Bug #141646 ?
--
Gutsy fails to work properly on Sony Vaio PCG-SRX51P/B
https://bugs.launchpad.net/bugs/157077
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I would like to add my voice to this. I have a SRX51P/B and the
downloaded Gutsy install CD-ROM (the standard one) refuses to boot
sensibly -- it appears to boot fine but as soon as anything associated
with the display and Xorg is supposed to happen I just get a black
screen. I forced a boot in
I have a PCG SRX51P/B. I tried installing Gutsy on it a few days ago
and that was a disaster -- it booted and worked except that the Xorg
system refused to work in any thing other than 800x600 mode (cf.
Bug#141646 and Bug #157077). I therefore reinstalled Feisty from my
original install discs
I probably ought to report that there is still a problem with Feisty --
there is no longer the nasty flashing but just a black screen. I have
removed quiet and splash from the boot options as the only sane solution
to the problem. It doens't look nice when booting but it is very
effective.
I
I only have the Ubuntu OpenOffice.org. What do you need me to do to try
the alternative?
Getting an instance of a font of this sorts costs about $25, is there no
expenses fund that could buy this for you? I would have thought
Canonical should have a fund to enable maintainers to undertake tests
Public bug reported:
Searching package.ubuntu.com indicates that there are no packages of
Python 2.6 associated with Ubuntu. There are none in Debian either.
Python 2.6 has some very significant changes relating to parallelism and
working on multicore and cluster machines, so it is important
I am not convinced this issue should be brushed aside like this. In the
past Ubuntu had Python 2.4 and 2.5 available -- 2.4 was the default
version but 2.5 was provided for cutting edge users. This worked very
well and allowed people to use both 2.4 and 2.5.
I see the current situation as
So if xmlto is no longer the way of converting DocBook/XML to PDF
because PassiveTeX is gone, what is the way of doing the conversion?
(The answer is probably obvious, I just missed the memo.)
--
passivetex missing in feisty
https://bugs.launchpad.net/bugs/121464
You received this bug
Daniel, Thanks for chipping in on this one. Yesterday I discovered
dblatex and it seems to be the good choice.
--
passivetex missing in feisty
https://bugs.launchpad.net/bugs/121464
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
We are now at Gutsy but very soon Hardy. I think it would be best to
wait till after the upgrade to Hardy to try the experiment to determine
if there is still a problem.
Currently with Gutsy, I have the splash screen switched off, so I have
no data about the flashing. As with Feisty, the screen
I am running fully up to date Gutsy server and am getting what I think
is the same problem as is reported here. After an indeterminate amount
of time and/or activity, the [lockd] process on the server goes from S
state to D state and all queries from clients result in messages such
as:
Feb 28
I would have thought that the Ubuntu Kernel Team would have looked at
this problem -- especially as there is a putative fix. However, it
seems it may not yet have even been triaged by them. The problem, at
least as I see it, is that there is no regularity to the failure. This
must make it hard
** Attachment added: version.log
http://launchpadlibrarian.net/11846353/version.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: uname-a.log
http://launchpadlibrarian.net/11846347/uname-a.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: dmesg.log
http://launchpadlibrarian.net/11846358/dmesg.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/11846362/lspci-vvnn.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: dmidecode.log
http://launchpadlibrarian.net/11846368/dmidecode.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Above the files as requested.
It just struck me that these are taken form a boot of Gutsy Gibbon and
not Hardy Heron. If it is important to get the information froma Hardy
Heron boot let me know.
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You
Above the versions of the files from a Hardy Heron boot of the Live CD
using acpi=off as a boot option.
Apologies for not using the latest kernel -- I just used the Live CD I
downloaded and burnt for the last experiment. I hope this is OK.
--
Hardy Heron Live CD fails to boot on AJP M3000N
** Attachment added: dmidecode.log
http://launchpadlibrarian.net/11888272/dmidecode.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/11888262/lspci-vvnn.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: dmesg.log
http://launchpadlibrarian.net/11888258/dmesg.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: uname-a.log
http://launchpadlibrarian.net/11888238/uname-a.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: version.log
http://launchpadlibrarian.net/11888252/version.log
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: xorg.conf
http://launchpadlibrarian.net/12161568/xorg.conf
--
[gutsy tribe 4] brightness keys no longer work but system automagically updates
to full brightness after 60 seconds
https://bugs.launchpad.net/bugs/131338
You received this bug notification because you are a
On my AJP M3000N I still have the problem. The brightness applet sets
the brightness permanently whereas using the keys causes the brightness
to change and then about 60s later to revert to the setting of the
applet. When the keys are being used a brightness indicator appears on
the screen.
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/12161569/Xorg.0.log
--
[gutsy tribe 4] brightness keys no longer work but system automagically updates
to full brightness after 60 seconds
https://bugs.launchpad.net/bugs/131338
You received this bug notification because you are
** Attachment added: lspci-vvnn
http://launchpadlibrarian.net/12161575/lspci-vvnn
--
[gutsy tribe 4] brightness keys no longer work but system automagically updates
to full brightness after 60 seconds
https://bugs.launchpad.net/bugs/131338
You received this bug notification because you are
The above files are from the AJP M3000N. I hope they are what was asked
for.
--
[gutsy tribe 4] brightness keys no longer work but system automagically updates
to full brightness after 60 seconds
https://bugs.launchpad.net/bugs/131338
You received this bug notification because you are a member
** Attachment added: lspci-nn_grep_VGA
http://launchpadlibrarian.net/12161580/lspci-nn_grep_VGA
--
[gutsy tribe 4] brightness keys no longer work but system automagically updates
to full brightness after 60 seconds
https://bugs.launchpad.net/bugs/131338
You received this bug notification
No problem, sorry for the delay in trying this. That certainly worked.
I just checked and this boot option is set in the Grub menu so I should
have realized. Sorry about. I guess though the moral of this story is
that the Live CD has to know when to set this option and when not to in
order for
I had reason to tinker further with this and have ascertained that the
problem was associated with a faulty CDROM rewriter. Kernels prior to
2.6.20 and 2.6.20-16.28 we able to boot even though there were issues
with the ata driver. All other post 2.6.20 kernels fail to deal with
the delay in
The Gutsy Live CD does indeed now boot on this machine now that the part
faulty CDROM rewriter has been taken out.
So although the CDROM rewriter was functioning correctly as a reader, it
failed to communicate in some way with the ata driver, and the ata
driver did not do the right thing which is
As I normally now have the ant-optional installed, I wouldn't have seen
any change.
I just tried the experiment of removing the ant-optional package and
running an Ant build that uses xslt and it seems to work fine. I am
using Ubuntu 7.10 Gutsy Gibbon. So I guess the problem is fixed and
this
I just tried this on Feisty and there is no problem there either.
It may be that I am not trying the correct experiment, but as they say
it works for me. If the problem is actually still there someone can
reopen the bug.
Thanks.
--
xslt core task fails to work
Manually creating a symlink may be the wrong approach but it is
currently the only really successful approach. Clearly it makes sense
to have a system that allows 4.1 and 4.2 to be installed at the same
time, however there is a blocking problem here:
gcc . -lgfortran
fails. I have
The lack of this file or some installed way round it should be
considered a blocker. I cannot link fortran code without manually
adding the symlink. It may be the wrong thing to do but it is the only
simple way of getting a link to work.
I assume this and Bug # 158673 are effectively the same.
Public bug reported:
I just downloaded the Hardy Heron iso image (alpha 3, 2008-01-09) and
burned it.
This CD fails to boot at all on an AJP M3000N (which is a rebadged Asus
M3000N). In fact nothing loads at all from the CD after selecting the
boot option. The fan goes to high speed after a
OK, let's close this one, I will open new reports for each of the
machines that the Hardy Heron alpha 3 does the wrong thing on.
Thanks.
--
Gutsy LiveCD won't start on Vaio SRX51 SRX41
https://bugs.launchpad.net/bugs/141646
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I just downloaded the Hardy Heron alpha 3 (dated (2008-01-09) iso image
and burned it.
The Live CD boots fine but the X mode is 800x600 instead of 1024x768.
xrandr -q reports that 800x600 is the maximum resolution which is
clearly wrong. I assume the wrong graphics driver
This attachment is from the boot fromt he Live CD for Hardy Heron. In a
few minutes I will attach the file from a boot of Gutsy Gibbon for
comparison.
** Attachment added: Hardy Heron file
http://launchpadlibrarian.net/11416355/Xorg.0.log
--
Hardy Heron Live CD boots but with incorrect
This is the file from a Gutsy boot. This uses the intel experimental
driver but the i810 driver worked as well.
** Attachment added: Gutsy Gibbon file
http://launchpadlibrarian.net/11416383/Xorg.0.log
--
Hardy Heron Live CD boots but with incorrect graphics mode on Vaio PCG-SRX51P/B
*** This bug is a duplicate of bug 141646 ***
https://bugs.launchpad.net/bugs/141646
Just to note that I retried the upgrade from Feisty - Gutsy yesterday
and this time it worked fine. I have no idea what the difference is
between now and then, but the machine is now happily running Gutsy.
I just thought I would report that although the Feisty - Gusty upgrade
failed on my PCG-SRX51P/B last November, I tried it again yesterday and
it worked fine. I have no idea what change has made the difference, but
it did. So I am now happily running Gutsy on this machine. Hopefully
the upgrade
Duly done.
** Attachment added: ajp_m3000n_hardyLiveCD.jpg
http://launchpadlibrarian.net/11440218/ajp_m3000n_hardyLiveCD.jpg
--
Hardy Heron Live CD fails to boot on AJP M3000N
https://bugs.launchpad.net/bugs/183748
You received this bug notification because you are a member of Ubuntu
Bugs,
On Gutsy 4.1 is the standard for gcc and g++ whereas the standard for
gfortran and gij is 4.2, so the linking is probably as it should be --
except that I am not sure why the alternatives system is not used to
handle the linking to versions, instead hardwired symbolic lionks are
used.
The upshot
I downloaded and burned a CD of Hardy Heron as at 2007-12-30 12:00 then
tried booting from it on the Sony PCG-SRX51P/B. The boot appeared to go
fine, but X failed to start:
/etc/gdm/failsafeXServer : line 47: [: too many arguments
Warning: Could not retrieve EDID because get-edid is not
The CD boots perfectly on my workstation so there are still problems
with booting on a Sony PCG-SRX51P/B and there are new very severe
problems on AJP M3000N (on which the Gutsy CD boots fine. I guess I
need to start a new separate issue?
--
Gutsy LiveCD won't start on Vaio SRX51 SRX41
Public bug reported:
Using OpenOffice.org with Hardy, after having manually introduced the
symbolic link:
lrwxrwxrwx 1 root root 19 2008-05-03 10:27 java-6-sun-1.6.0.03 -
java-6-sun-1.6.0.06/
in /usr/lib/jvm so that writing Flat ODT and DoccBook/XML actually
works, I have found that the
Note though the subte error o1.6.0.03 vs 1.6.0.06, it seems
OpenOffice.org is hardwired to look for the Gutsy version of the JVM
whereas Hardy has a more recent version of the JVM.
--
OpenOffice can not find JRE (sun 1.6)
https://bugs.launchpad.net/bugs/96875
You received this bug notification
I have just upgraded to Hardy and am trying to use OpenOffice.org 2.4 to
write fodt or DocBook/XML files. This failes with the error message:
[Java framework]sunjavaplugin.so could not load Java runtime library:
file:///usr/lib/jvm/java-6-sun-1.6.0.03/jre/lib/i386/client/libjvm.so.
However the
OpenOffice.org as distributed with Gutsy did the right thing: the save
icon was greyed out on opening a document and after every commit,
becoming lit on the first amending action. OpenOffice.org as
distributed with Hardy always has the save icon lit. It seems rather
bizarre that this error
The problem turned out to be a broken DVD rewriter, I took the rewriter
out and the problem went away. However, there was no indication that
this was the problem, it was a pure fluke that I discovered it. So
although the bug has been marked invalid, there is in fact still a bug:
the kernel
This is a breaking change that should be unbroken so I would have
thought that an update was entirely in order -- especially as the
current behaviour is so damn annoying :-)
--
[Upstream] [hardy] openoffice.org no longer greys out save button after saving
as it should
Don't think so, my systems all have openoffice.org-java-common
installed.
--
OpenOffice can not find JRE (sun 1.6)
https://bugs.launchpad.net/bugs/96875
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Gossip on Gutsy was excellent. Upgrading to Hardy has been problematic.
Not only is there a problem with lost account information -- reported
elsewhere -- I find that Gossip now disconnects after a period of time.
This never used to happen on Gutsy and it is very annoying to
Public bug reported:
I created a new shared repository and then tried checkout out a
subversion repository into it, but it failed. Posting a bug report as
requested.
| bzr co svn+https://svn.codehaus.org/gant/gant/trunk Trunk
Initialising Subversion metadata cache in
Public bug reported:
From a gnome-terminal logged in as russel I did:
sudo su - bazaarbook
in order to have a login as bazaarbook
I then went through a Bazaar branch start sequence:
| bzr init MyNewWebsite
| bzr status
bzr: ERROR: Not a branch: /home/users/bazaarbook/book/.
| cd
Public bug reported:
In the suituation where the initiator of olive-gtk is not the owner of
the X server then the error message leaves a lot to be desired -- not to
mention the seg fault:
| olive-gtk
/var/lib/python-support/python2.5/gtk-2.0/gtk/__init__.py:72: GtkWarning: could
not open
I should have said this is on Ubuntu Hardy with
| dpkg -l *bzr*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name
Public bug reported:
Olive-GTK provides a menu item for creating a new directory in a branch,
but does not provide a menu entry for creating a new file. There should
be a menu item for create new file which has a dialog to get the name
and then starts the users preferred editor with that
I log in as russel then in a gnome-terminal do sudo su - bazaarbook to
switch to being user bazaarbook in that terminal. It is not at all
surprising that olive-gtk fails, but I think the error message and the
seg fault need a wee bit of attention. As it happens the DISPLAY
variable is not set,
Public bug reported:
I created a new branch using the Olive-GTK create a new named directory
branch menu item. I then create a new file externally from Olive-GTK.
I then used the per entry context menu and selected add to add the new
file to the branch, but I get the dialogue Unknown error:
Public bug reported:
Binary package hint: bzr-gtk
This may be the same error as Bug 244025 or it may not.
The context is the same: Newly created branch using Olive-GTK, newly
created file created outside of Olive-GTK. Then select the new file and
go to the main File|Add file(s). This puts up
It appears that this is the same as Bug 244025 since on the console I
get:
Traceback (most recent call last):
File /usr/lib/python2.5/site-packages/olive/add.py, line 74, in add
bzrlib.add.smart_add([fullpath])
AttributeError: 'module' object has no attribute 'smart_add'
--
Cannot add
Public bug reported:
Binary package hint: bzr-gtk
Double clicking on a file in the working tree display uses the default
application. So for example an html file is started with a browser.
There appears to be no way of selecting any of the alternate
applications. The application selection menu
Public bug reported:
Binary package hint: bzr-gtk
This may just be a version problem, but when I ran bzr visualize from a
Bazaar branch directory I got:
| bzr visualize
Traceback (most recent call last):
File /usr/lib/python2.5/site-packages/bzrlib/plugins/gtk/viz/treeview.py,
line 234, in
OK, so this implies I should take a branch of a more uptodate version
and put it in ~/.bazaar/plugins. Is there a best URL?
Thanks.
--
bzr visualize fails on Hardy
https://bugs.launchpad.net/bugs/244178
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK, that worked.
gtk 0.95.0dev1
Graphical support for Bazaar using GTK.
Now I just have to remember to use ~/.bazaar/plugins/gtk/olive-gtk all
the time. :-)
Thanks.
--
bzr visualize fails on Hardy
https://bugs.launchpad.net/bugs/244178
You received this bug notification because you are a
Public bug reported:
Binary package hint: bzr-gtk
Using the bzr-gtk from https://code.edge.launchpad.net/~bzr-gtk/bzr-
gtk/trunk installed as ~/.bazaar/plugins/gtk, when I try to start olive-
gtk in a Bazaar branch then thigns are fine. If I try to start it in a
directory that is not a branch I
Public bug reported:
Binary package hint: bzr-gtk
Using the latest version og bzr-gtk from
https://code.edge.launchpad.net/~bzr-gtk/bzr-gtk/trunk, then when
pressing the log button whilst in a Bazaar branch, I get:
| $HOME/.bazaar/plugins/gtk/olive-gtk
Traceback (most recent call last):
File
OK, I will check my set up, but I thought I was using bzr.dev. I have
just pulled revision 3514 and will try again.
--
olive-gtk fails with inappropriate error message when started in a location
that is not a Bazaar branch
https://bugs.launchpad.net/bugs/244199
You received this bug
I am not sure how the 1.5.0 version of bzr can be being used.
| which bzr
/home/users/russel/bin/bzr
| ll `!!`
ll `which bzr`
lrwxrwxrwx 1 russel russel 42 2008-06-30 14:01 /home/users/russel/bin/bzr -
/home/Checkouts/Bazaar/Bazaar_Mainline/bzr*
| bzr --version
Bazaar (bzr) 1.6b3
from bzr
Hummm... I can feel a request for a document of instruction. I bet
there is one, I have just failed to know where it is.
| python -c 'import bzrlib; print bzrlib.__file__'
/usr/lib/python2.5/site-packages/bzrlib/__init__.pyc
| PYTHONPATH=/home/Checkouts/Bazaar/Bazaar_Mainline python -c 'import
Is there a quick and easy way of me trying the fixes prior to formal
release or is it best to wait for a formal release?
--
Add of new file from context menu fails
https://bugs.launchpad.net/bugs/244025
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is there a quick and easy way of me trying the fixes prior to formal
release or is it best to wait for a formal release?
--
Cannot add from main menu item
https://bugs.launchpad.net/bugs/244027
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Being under development is not a problem. What I am suggesting is
something to think about for features to add. Is there a roadmap for
olive-gtk?
Is there a plan to provide Nautilus integration so that Nautilus can be
used as the Bazaar client?
My feeling is that most people will see Olive-GTK
I have just had an issue with a broken SSL certificate that I needed to
accept as a one-off and found Epiphany to be significantly inferior to
Galeon in the way the browser interacts with the user. Can I propose
that following the Galeon way of doing things would improve Epiphany --
i.e. put up
Public bug reported:
Where a parent-branch has changeset to be pulled, but the branch has no
changesets that will be rebased then an error ensues.
| bzr rebase
Rebasing on svn+https://svn.codehaus.org/groovy/trunk/groovy/groovy-core
bzr: ERROR: exceptions.IndexError: list index out of range
Just to confirm that Hardy has a gimp with the -c option.
(Everyone already knows this but it seems like a good way of saying we
can close this bug.)
Thanks.
--
-c option in manual but not recognized since updated Feisty - Gutsy
https://bugs.launchpad.net/bugs/156232
You received this bug
Public bug reported:
Binary package hint: scons
The SCons package listed for Intrepid (as indeed for Hardy) is very much
out of date. Lenny and Sid both have 0.98.4 whereas Intrepid is still
stuck back in the dark ages of 0.97. SCons 0.98.5 is about to be
released leading soon to 1.0. Please
*** This bug is a duplicate of bug 226783 ***
https://bugs.launchpad.net/bugs/226783
Apologies for submitting a duplicate.
--
SCons package not up to date
https://bugs.launchpad.net/bugs/238289
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I think bzr-svn 0.4.10 cures this bug. Certainly I have been able to
successfully checkout the Subversion repository into a Bazaar shared
repository without error. The problem with 0.4.9 remains reproducible
though, however as this is a consequence of deleting the SVK annotations
from a
Public bug reported:
I just ran a bzr pull and got the error below. This morning it all
worked, then I got this failure, but it is not reproducible, i.e. I
tried it again and it just worked fine. I am reporting this to show
that there seems to be some occasional instability somewhere associated
From the logs provided by Ben Walding of Codehaus, the erroneous pull
gave:
2008-06-23-10-codehaus01.managed.contegix.com:213.165.225.90 - -
[23/Jun/2008:10:53:40 -0500] PROPFIND /gradle/gradle-core/trunk HTTP/1.1 207
706 - SVN/1.4.6 (r28521) neon/0.27.2 svn.codehaus.org 0
I'm afraid it was all Ben could send me easily.
Maybe we just ignore this one for now and see if anything similar ever
happens again.
--
Error whilst pulling
https://bugs.launchpad.net/bugs/242391
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think this problem may now be just past history. As far as I can tell
Hardy is working entirely fine on this machine. (Well there is a
problem with the splash screen on booting, but apart from that it all
works entirely fine and at 1024x768 :-)
I am still using the i810 driver but am thinking
*** This bug is a duplicate of bug 141646 ***
https://bugs.launchpad.net/bugs/141646
I have now upgraded this machien to Hardy which appears to be working
fine -- I haven't actually tried the Live CD, I just upgraded and
everything worked as required. I wonder if time has passed this bug by
Though I should point out that booting from the Hardy Live CD does cause
the system to work in 800x600 mode. So there is a problem there, but not
in the disc boot I have.
--
[Hardy] doesn't recognize native resolution on Vaio PCG-SRX51P/B (i815m)
https://bugs.launchpad.net/bugs/183746
You
I upgraded to Hardy and there seems to be no trouble at all (well apart
from not removing various packages but that seems to be a general
problem). I just tried the Hardy Live CD and it booted fine -- except
that it came up ion 800x600 mode and not 1024x768. So it seems as
though time might have
Hardy boots fine, but the splash screen never shows. If I boot without
splash everything goes as expected, with splash I just get a blank
screen during the boot. So all the irritation during boot has gone but
. . . so has the Ubuntu logo.
In other news, it seems that there are no problems with
1 - 100 of 415 matches
Mail list logo
