Package: pex
Version: 1.1.14-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after installing pex, simply running in the shell lead to the following stack
trace:
$ pex
Traceback (most recent call last):
File "/usr/bin/pex", line 11, in
Seems to do the trick. And after reading the manpage I am tempted to say that
is THE right fix here.
Am Samstag, 14. Mai 2011 schrieb Marco d'Itri:
On May 13, Marco d'Itri m...@linux.it wrote:
I have a better idea: can you try replacing the kill loop with just
udevadm control --exit?
--
notfound 622309 168-1
notfound 622309 168-2
thanks
You are right, I'm sorry.
It looks more like #624469 now. I will present my findings there.
Am Mittwoch, 11. Mai 2011 schrieb Marco d'Itri:
So it obviously cannot be the same bug.
--
To UNSUBSCRIBE, email to
Hi, I have this problem as well, and it seems to be some Heisenbug. When I
boot up the computer normaly, udev fails with the already bound socket and I
get no input devices. When I put debug on the kernel command line the problem
seems to get a statistical component, and whenever I put
found 622309 168-1
found 622309 168-2
thanks
I have the same problem again with both versions 168-1 and 168-2. And I double
checked there is no /run. There must be yet another trigger.
Downgrading to 167-3 from snapshot ensures a working computer again.
Regards, Matthias
--
To UNSUBSCRIBE,
since grub-mkrelpath works correct on files (they cannot be mountpoints,
right?) I would sugest to try the following patch. Sadly I cannot test it until
this evening.
--- 10_linux2009-11-25 19:41:40.0 +0100
+++ 09_linux2009-11-27 14:03:04.0 +0100
@@ -87,7 +87,9 @@ while
The following hot fix patch seems to work. And it also kills the doubled
slashes (They must have been around with the old method, too.).
Greetings, Matthias
--- 10_linux.OLD2009-11-27 18:17:52.0 +0100
+++ 10_linux2009-11-27 18:18:18.0 +0100
@@ -87,7 +87,9 @@ while [
7 matches
Mail list logo
