/srv/irclogs.ubuntu.com/2013/06/26/#ubuntu-bugs.txt

=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== cprofitt_ is now known as cprofitt
=== deegee__ is now known as drussell
=== pedro_ is now known as Guest26722
Skini151Hi,today i tested "saucy daily image" and encountered a problem , after suspend Ubuntu i can't return to DE, see only black screen/// what package is responsible for this "gnome-power-manager" , "pm-utils" , or the kernel himself.19:11
Skini151tested on VM19:13
Skini151both KVM and VirtualBox19:13
hggdhSkini151: since we do not know what caused the error, we can go conservative, and assume -- for now -- this is a kernel issue19:14
Skini151can i put the "gnome-power-manager" , "pm-utils" , the kernel logs to this bug on LP, if i am not sure about it19:18
Skini151?19:18
hggdhSkini151: yes, you can.19:20
Skini151you encountered this kind of bug before?19:21
Skini151i found a bug that can be similar to mine can you look at it19:27
Skini151https://bugs.launchpad.net/ubuntu/saucy/+source/linux/+bug/105473219:28
ubot2`Ubuntu bug 1054732 in linux (Ubuntu Saucy) "[LENOVO 4298R86] suspend/resume failure" [High,Confirmed]19:28
Skini151or this one : https://bugs.launchpad.net/ubuntu/saucy/+source/linux/+bug/119366119:31
ubot2`Ubuntu bug 1193661 in linux (Ubuntu Saucy) "[Apple Inc. MacBookPro10,1] suspend/resume failure [non-free: wl]" [Medium,Confirmed]19:31
hggdhSkini151: do you see a kernel oops?19:31
Skini151nope just black screen and blinking cursor19:32
hggdhcan you access the system via SSH?19:33
hggdhbecause I do not see, a priori, any of the above bugs as being relevant19:34
Skini151no19:35
Skini151i can't type anything19:35
hggdhcan you ping the VM from your system?19:35
hggdhthe reason is if we do not have data on this, it will be very difficult to solve it19:36
Skini151at begin cursor blinks but after he just freeze19:37
hggdhyes, I understand. But we need to be able to gather data.19:38
hggdhhuh19:38
Skini151it seems that i can access the DE but i see black screen19:38
hggdhperhaps you will get more help from #ubuntu-quality, the folks there are working continuously on testing Saucy19:38
hggdhah, you are already there19:39
Skini151i will try tomorrow to install on real machine , will that change grub version?19:39
hggdhno, it will not. But please consider installing *also* SSH. if this is a bug on the DE, you would be able to SSH in, and gather data19:40
Skini151and after ok19:40
Skini151oooops19:40
Skini151ok19:40
Skini151just ok19:40
hggdh:-)19:41
hggdhOK19:41
Skini151thanks19:41
hggdhyw19:41
theghostHi, I wanted to fix my first ubuntu bug with the help of https://wiki.ubuntu.com/Bugs/HowToFix. But when I tried to build a dep from my fixed package (according to https://wiki.ubuntu.com/Bugs/HowToFix#Testing_the_fix)) a got the following error: "bzr: ERROR: exceptions.UnicodeEncodeError: 'ascii' codec can't encode character u'\xe4' in position 40: ordinal not in range(128)". Anyone knows what that means ?19:48
hggdhtheghost: that means bzr died with an exception (UnicodeEncodeError). Not good, really.19:50
hggdhtheghost: what version of Ubuntu are you running?19:51
theghosthggdh: I am running Raring / 13.0419:52
hggdhtheghost: and is it up-to-date? Spefically, is bzr up-to-date?19:52
theghosthggdh: I install bzr with "sudo apt-get install bzr"19:53
theghostThe error looks somehow similar to this: "https://bugs.launchpad.net/bzr/+bug/871386"19:54
ubot2`Ubuntu bug 871386 in Bazaar "recipe fails to build" [Undecided,Fix released]19:54
hggdhthis is a very old bug, I would expect the current bzr to have the fix19:55
hggdhtheghost: but is the backtrace the same?19:55
hggdhtheghost: ah, no, there is really no bug, sort of. It has something to do with the simlink and/or locale19:57
hggdhtheghost: this is actually a good question -- do you have any simlinks/directories in the path of the bzr operation with, say, umlauts?19:58
theghosthggdh: yes, looks like an encoding issue. i use utf819:58
theghosthggdh: the filepath to the directory contains umlauts. will change and retry19:59
hggdh(frankly, I would still consider it a bug, bzr should not die because we have localised characters in a path)20:00
theghosthggdh: ok, now the bzr error is gone. definetely was the umlauts in filepath. thanks. i think too that a version system should not break because of this. I will file a bug for "bzr"20:05
hggdhtheghost: please do. Please also add a link to the bug you found, so that we do not lose the  history20:06
theghostok, in case someone is interested I filed this bug for the encoding error:  https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/119501120:21
ubot2`Ubuntu bug 1195011 in bzr (Ubuntu) "bzr-buildpackage fails if directory contains umlauts" [Undecided,New]20:21
theghosthggh: thanks for your help, hggdh. cya20:22

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!