=== 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 | ||
Skini151 | Hi,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 |
---|---|---|
Skini151 | tested on VM | 19:13 |
Skini151 | both KVM and VirtualBox | 19:13 |
hggdh | Skini151: since we do not know what caused the error, we can go conservative, and assume -- for now -- this is a kernel issue | 19:14 |
Skini151 | can i put the "gnome-power-manager" , "pm-utils" , the kernel logs to this bug on LP, if i am not sure about it | 19:18 |
Skini151 | ? | 19:18 |
hggdh | Skini151: yes, you can. | 19:20 |
Skini151 | you encountered this kind of bug before? | 19:21 |
Skini151 | i found a bug that can be similar to mine can you look at it | 19:27 |
Skini151 | https://bugs.launchpad.net/ubuntu/saucy/+source/linux/+bug/1054732 | 19:28 |
ubot2` | Ubuntu bug 1054732 in linux (Ubuntu Saucy) "[LENOVO 4298R86] suspend/resume failure" [High,Confirmed] | 19:28 |
Skini151 | or this one : https://bugs.launchpad.net/ubuntu/saucy/+source/linux/+bug/1193661 | 19:31 |
ubot2` | Ubuntu bug 1193661 in linux (Ubuntu Saucy) "[Apple Inc. MacBookPro10,1] suspend/resume failure [non-free: wl]" [Medium,Confirmed] | 19:31 |
hggdh | Skini151: do you see a kernel oops? | 19:31 |
Skini151 | nope just black screen and blinking cursor | 19:32 |
hggdh | can you access the system via SSH? | 19:33 |
hggdh | because I do not see, a priori, any of the above bugs as being relevant | 19:34 |
Skini151 | no | 19:35 |
Skini151 | i can't type anything | 19:35 |
hggdh | can you ping the VM from your system? | 19:35 |
hggdh | the reason is if we do not have data on this, it will be very difficult to solve it | 19:36 |
Skini151 | at begin cursor blinks but after he just freeze | 19:37 |
hggdh | yes, I understand. But we need to be able to gather data. | 19:38 |
hggdh | huh | 19:38 |
Skini151 | it seems that i can access the DE but i see black screen | 19:38 |
hggdh | perhaps you will get more help from #ubuntu-quality, the folks there are working continuously on testing Saucy | 19:38 |
hggdh | ah, you are already there | 19:39 |
Skini151 | i will try tomorrow to install on real machine , will that change grub version? | 19:39 |
hggdh | no, 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 data | 19:40 |
Skini151 | and after ok | 19:40 |
Skini151 | oooops | 19:40 |
Skini151 | ok | 19:40 |
Skini151 | just ok | 19:40 |
hggdh | :-) | 19:41 |
hggdh | OK | 19:41 |
Skini151 | thanks | 19:41 |
hggdh | yw | 19:41 |
theghost | Hi, 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 |
hggdh | theghost: that means bzr died with an exception (UnicodeEncodeError). Not good, really. | 19:50 |
hggdh | theghost: what version of Ubuntu are you running? | 19:51 |
theghost | hggdh: I am running Raring / 13.04 | 19:52 |
hggdh | theghost: and is it up-to-date? Spefically, is bzr up-to-date? | 19:52 |
theghost | hggdh: I install bzr with "sudo apt-get install bzr" | 19:53 |
theghost | The 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 |
hggdh | this is a very old bug, I would expect the current bzr to have the fix | 19:55 |
hggdh | theghost: but is the backtrace the same? | 19:55 |
hggdh | theghost: ah, no, there is really no bug, sort of. It has something to do with the simlink and/or locale | 19:57 |
hggdh | theghost: this is actually a good question -- do you have any simlinks/directories in the path of the bzr operation with, say, umlauts? | 19:58 |
theghost | hggdh: yes, looks like an encoding issue. i use utf8 | 19:58 |
theghost | hggdh: the filepath to the directory contains umlauts. will change and retry | 19:59 |
hggdh | (frankly, I would still consider it a bug, bzr should not die because we have localised characters in a path) | 20:00 |
theghost | hggdh: 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 |
hggdh | theghost: please do. Please also add a link to the bug you found, so that we do not lose the history | 20:06 |
theghost | ok, in case someone is interested I filed this bug for the encoding error: https://bugs.launchpad.net/ubuntu/+source/bzr/+bug/1195011 | 20:21 |
ubot2` | Ubuntu bug 1195011 in bzr (Ubuntu) "bzr-buildpackage fails if directory contains umlauts" [Undecided,New] | 20:21 |
theghost | hggh: thanks for your help, hggdh. cya | 20:22 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!