Hi Martin,
I've tested the proposed patch. However, don't know how to 'confirm'
this fix. So I did the same walk through as in the previous comment, and
I've attached the log + screenshot of synaptic, to proof I've used the
proposed repository including the changelog stating this bug.
Test
@Stefano Rivera:
My bad, my sample was in direct reply to the bug creator. I have tested
them both (mercurial PPA repo default Ubuntu oneiric).
My solution sample was meant for the 1.9.1-1-PPA2 version. However, it
is also very much applicable for the default repository of ubuntu
oneiric. (in
Dear Stefano,
First of all, the earlier mentioned line where I change the if
statement, should be line 316, not 318. At 318 the command line spits
out the error, since 'bundlename' is empty.
I've made a storyboard/walkthrough in console to reproduce this. All
information should be there, maybe
Experience EXACTLY the same as Angel Guzman Maeso.
Upgraded to 11.10 today, so I guess this issue sneaked into my system
like that.
I've attached my log/proof to the post.
** Attachment added: Transplant log
As a quick and dirty solution I've changed line 318 of
/usr/lib/pymodules/python2.7/mercurial/bundlerepo.py
-if not incoming:
+if not incoming and bundlename:
basicly checks if bundlename is not empty
I had to do a transplant fast and this solved the issue for the time
being.
--
You
Bug remains in the Beta release of Jaunty too. How can one tell whether
this bug is 'fixed' in a release or not? (without rereading the entire
changelog)
--
jaunty kernel 2.6.28-11 kernel destroy system
https://bugs.launchpad.net/bugs/346691
You received this bug notification because you are a
Yes Graziano, you hit the nail on the spot I'm afraid.
I'm not really familiar how it works with those patches or when to
expect this update/grade available in the Alpha/Beta repo's, so I'll
watch from a distance for the coming week(s).
(Unless someone can guarantee me, the fix is already there,
Same issue over here. Saturday I decided to give Jaunty a try, after a
collegue of mine warned for the issues with ext4.
I looked out that the dist-upgrade wouldn't touch the filesystem NOR
update it. Nevertheless:
* First boot OK, few time crashing nautilus applets in gnome though
* Reboot and
I stumbled upon this problem this morning.
I have 2 systems running, one with 7.10 and the other one with 8.04. Now
I needed to configure evolution on my 8.04 system and had the same
issue, that it was coming back over and over again with the password
prompt. No inbox available either, nothing.
Same problem over here, also joined the #alsa channel for this. Someone
was kind enough to point out to me that the Master/Mixer changes the
wrong device when used.
So in my language, it means that 0x1d is the master/mixer and I'm
changing the 0x13 device id instead with the master/mixer buttons.
10 matches
Mail list logo
