[Bug 2023424] Re: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere
It's pretty strange, but the upstream fix does not seem to work on Ubuntu, at least not on 24.04. I tried Debian Sid, and there the regular gcc-13 package (13.2.0-24) has no trouble at all with the test case: no alignment issue, no segfaults. Whereas on Ubuntu 24.04, anything after upstream's https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=28219f7f99a80519d1c6ab5e5dc83b4c7f8d7251 (libsanitizer: merge from upstream) and https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=aaf0f12175bfc0a7bdc6c80b8d481fb09ae44e25 (libsanitizer: Apply local patches) just segfaults, e.g.: Program received signal SIGSEGV, Segmentation fault. 0x7f5b91d9ba44 in __interception::InterceptFunction (name=0x7f5b91dc5717 "strcat", ptr_to_real=0x7f5b91d44128 <__interception::real_strcat>, func=140031265358128, trampoline=140031265358128) at /home/ubuntu/src/gcc/master/libsanitizer/interception/interception_linux.cpp:62 warning: Source file is more recent than executable. 62*ptr_to_real = (uptr)addr; (gdb) bt #0 0x7f5b91d9ba44 in __interception::InterceptFunction (name=0x7f5b91dc5717 "strcat", ptr_to_real=0x7f5b91d44128 <__interception::real_strcat>, func=140031265358128, trampoline=140031265358128) at /home/ubuntu/src/gcc/master/libsanitizer/interception/interception_linux.cpp:62 #1 0x7f5b91d477d4 in __asan::InitializeAsanInterceptors () at /home/ubuntu/src/gcc/master/libsanitizer/asan/asan_interceptors.cpp:759 #2 0x7f5b91d5c2b1 in __asan::AsanInitInternal () at /home/ubuntu/src/gcc/master/libsanitizer/asan/asan_rtl.cpp:446 #3 0x7f5b91d5c819 in __asan_init () at /home/ubuntu/src/gcc/master/libsanitizer/asan/asan_rtl.cpp:626 #4 0x7f5b92345873 in _dl_init (main_map=0x7f5b923792e0, argc=1, argv=0x7fffed4940b8, env=0x7fffed4940c8) at ./elf/dl-init.c:106 #5 0x7f5b9235f5a0 in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 #6 0x0001 in ?? () #7 0x7fffed495667 in ?? () #8 0x in ?? () -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023424 Title: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2023424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023424] Re: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere
Ok, I found https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110027 : "[11/12 regression] Stack objects with extended alignments (vectors etc) misaligned on detect_stack_use_after_return". As described in that bug, turning _off_ the ASAN_OPTION detect_stack_use_after_return makes the misalignment go away: $ ~/ins/gcc-13-103-gf732bf6a603/bin/gcc -fsanitize=address -fstack- protector asan-align.c -o asan-align $ LD_LIBRARY_PATH=/home/ubuntu/ins/gcc-13-103-gf732bf6a603/lib64 ./asan-align explicitly aligned variable: 0x7f6c6f100020 asan-align: asan-align.c:11: main: Assertion `addr % 64 == 0' failed. Aborted $ LD_LIBRARY_PATH=/home/ubuntu/ins/gcc-13-103-gf732bf6a603/lib64 ASAN_OPTIONS="detect_stack_use_after_return=false" ./asan-align explicitly aligned variable: 0x7ffe189ec4c0 The fix for master (14.x) is in https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=467898d513e602f5b5fc4183052217d7e6d6e8ab, while it was merged to 13.x in https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=a16d90ec302e588dab5d7d31ccdd7b3fd5c6214e . I think it should be relatively safe to apply this patch to Ubuntu's gcc packages? ** Bug watch added: GCC Bugzilla #110027 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110027 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023424 Title: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2023424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023424] Re: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere
I bisected, and it seems to have regressed with https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=f732bf6a603721f61102a08ad2d023c7c2670870 ["libsanitizer: merge from upstream (0a1bcab9f3bf75c4c5d3e53bafb3eeb80320af46]. Unfortunately, that is a fairly large merge from the upstream sanitizer libraries, so it is not that easy to pinpoint where the culprit is. I tried very recent gcc master, and there the test with -fsanitize=address -fstack-protector even segfaults! So I guess an upstream gcc bug report is probably the best way forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023424 Title: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2023424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023424] Re: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere
FWIW I've built stock releases/gcc-13.2.0 locally on a Ubuntu 24.04 box (configured with --disable-multilib --disable-bootstrap --enable- languages=c,c++ --enable-libsanitizer --disable-libquadmath --disable- libgomp --disable-libvtv --disable-werror --disable-nls), and indeed it also reproduces with that. And you need both -fsanitize=address and -fstack-protector: $ ~/ins/gcc-13.2.0-0-gc891d8dc23e/bin/gcc -fsanitize=address asan- align.c -o asan-align $ ./asan-align explicitly aligned variable: 0x7f1241c00040 $ ~/ins/gcc-13.2.0-0-gc891d8dc23e/bin/gcc -fsanitize=address -fstack- protector asan-align.c -o asan-align $ ./asan-align explicitly aligned variable: 0x7f869ea00020 asan-align: asan-align.c:11: main: Assertion `addr % 64 == 0' failed. Aborted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023424 Title: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2023424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023424] Re: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere
Eh sorry, I meant in the example that asserts, that I compiled and ran it on Ubuntu 24.04 first! And the same binary does run fine on Ubuntu 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023424 Title: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2023424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023424] Re: GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer bug that doesn't manifest elsewhere
There is something weird going on here. I'm seeing the same thing with
Ubuntu 24.04's gcc 13.2.0-23ubuntu4, after hitting some issues with x264
(which declared a local variable with __attribute__((aligned(64))) but
then it actually wasn't aligned as such, and some AVX512 function then
segfaults due to unaligned access).
In my case I can compile the following example on Ubuntu 22.04, and the
resulting binary asserts:
#undef NDEBUG
#include
#include
#include
int main(void)
{
char c __attribute__((__aligned__(64)));
uintptr_t addr = (uintptr_t)
printf("explicitly aligned char: %#lx\n", addr);
assert(addr % 64 == 0);
return 0;
}
$ gcc -fsanitize=address asan-align.c -o asan-align
$ ./asan-align
explicitly aligned char: 0x7f6e1920
asan-align: asan-align.c:11: main: Assertion `addr % 64 == 0' failed.
Aborted
However, running _exactly_ the same binary on Ubuntu 22.04 does not
assert. E.g.:
$ ./asan-align
explicitly aligned char: 0x7ffd1fea4e40
So it looks like there is something that causes main()'s stack to be
differently aligned. Whether that is due to Ubuntu 22.04 and 24.04
having different crt*.o files, or due to some AddressSanitizer
difference, is not clear to me yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2023424
Title:
GCC 13 on Lunar exhibits AddressSanitizer/UndefinedBehaviorSanitizer
bug that doesn't manifest elsewhere
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-13/+bug/2023424/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
https://github.com/google/sanitizers/issues/1716#issuecomment-2010399341 Summarizing: newer ThreadSanitizer has been updated to be able to work with vm.mmap_rnd_bits = 30, but not higher than that. For other cases, it will now re-execute the binary with ASLR disabled, if possible. For most people the quick workaround of setting vm.mmap_rnd_bits to 28 might work, but of course you won't get the benefits intended with #1983357 either. So at some point, it would be nice to have the upstream ThreadSanitizer fixes backported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056762 Title: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
It's indeed the bump of vm.mmap_rnd_bits from 28 to 32, which is part of
the changelog in https://launchpad.net/ubuntu/+source/linux/6.5.0-25.25
:
* test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 /
J-OEM-6.1 / J-6.2 AMD64 (LP: #1983357)
- [Config]: set ARCH_MMAP_RND_{COMPAT_, }BITS to the maximum
On my amd64 6.5.0-21-generic machines, the default value is:
vm.mmap_rnd_bits = 28
while on 6.5.0-25-generic, it is:
vm.mmap_rnd_bits = 32
Forcing vm.mmap_rnd_bits back to 28 on 6.5.0-25-generic makes
ThreadSanitizer work again.
I'm unsure if this bug should be kept open now, since it is maybe
expected that some user space programs break due to the changed
randomization settings?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056762
Title:
ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056762/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
This could be the same thing reported in
https://github.com/google/sanitizers/issues/1716 ("Thread Sanitizer
FATAL error on kernel version 6.6.6-x").
** Bug watch added: github.com/google/sanitizers/issues #1716
https://github.com/google/sanitizers/issues/1716
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056762
Title:
ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056762/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
One other note, I only get the "unexpected memory mapping" error on amd64. On arm64 machines with 6.5.0-25.25~22.04.1, ThreadSanitizer works without issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056762 Title: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2056762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056762] [NEW] ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Public bug reported:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an error
similar to:
FATAL: ThreadSanitizer: unexpected memory mapping
0x5c4dc2bcd000-0x5c4dc2bed000
Reverting the kernel back to 6.5.0-21.21~22.04.1 and rebooting makes the
same executables work again.
There are a few older bugs including
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67308 and
https://github.com/google/sanitizers/issues/503 but these are from
~2015, and about gcc 7 and linux 4.1 so it does not seem to be the same
problem.
A very small program, lifted from
https://github.com/google/sanitizers/wiki/ThreadSanitizerCppManual can
be used to show the problem:
$ cat simple-race.c
#include
#include
int Global;
void *Thread1(void *x) {
Global++;
return NULL;
}
void *Thread2(void *x) {
Global--;
return NULL;
}
int main() {
pthread_t t[2];
pthread_create([0], NULL, Thread1, NULL);
pthread_create([1], NULL, Thread2, NULL);
pthread_join(t[0], NULL);
pthread_join(t[1], NULL);
}
$ cc -fsanitize=thread -fPIE -pie -g simple-race.c -o simple-race
$ ./simple-race
FATAL: ThreadSanitizer: unexpected memory mapping 0x5d161227c000-0x5d161227d000
$ uname -a
Linux buildhost 6.5.0-25-generic #25~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb
20 16:09:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
When running that exact same binary, on the same machine, but with linux
6.5.0-21:
$ ./simple-race
==
WARNING: ThreadSanitizer: data race (pid=19373)
Read of size 4 at 0x560964a2d014 by thread T2:
#0 Thread2 /home/lxc-unpriv/simple-race.c:12 (simple-race+0x12d1)
Previous write of size 4 at 0x560964a2d014 by thread T1:
#0 Thread1 /home/lxc-unpriv/simple-race.c:7 (simple-race+0x128c)
Location is global 'Global' of size 4 at 0x560964a2d014 (simple-
race+0x4014)
Thread T2 (tid=19376, running) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:19 (simple-race+0x1368)
Thread T1 (tid=19375, finished) created by main thread at:
#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:969
(libtsan.so.0+0x605b8)
#1 main /home/lxc-unpriv/simple-race.c:18 (simple-race+0x1347)
SUMMARY: ThreadSanitizer: data race /home/lxc-unpriv/simple-race.c:12 in Thread2
==
ThreadSanitizer: reported 1 warnings
$ uname -a
Linux buildhost 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb
9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
** Affects: linux-signed-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056762
Title:
ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2056762/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056762] Re: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1
Note that similar to the older gcc and upstream sanitizer bugs, this problem may be caused by some kernel API now returning a slightly different result, so it could be debatable whether the issue should be fixed in ThreadSanitizer, or in the kernel itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056762 Title: ThreadSanitizer: unexpected memory mapping with 6.5.0-25.25~22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2056762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055280] Re: openjdk-17-jre-headless 17.0.10+7-1~22.04.1: segfault in jspawnhelper
Okay, I think the mystery might be solved.
The root cause is that unattended-upgrades (or some other apt upgrade)
does a openjdk-17 package update, while at the same time a java process
is running. After this minor upgrade, the protocol between the JRE's
forkAndExec JNI function and the jspawnhelper tool is changed! The
jspawnhelper tool now expects argv[0] to be the executable name of
itself, argv[1] to be a "%d:%d" format string with two file descriptors,
and argv[2] to be NULL.
However, the any already-running java process will still use the old
protocol, which invoked jspawnhelper with the "%d:%d" format string in
argv[0], and argv[1] set to NULL. This is what makes the new
jspawnhelper executable segfault.
Therefore, with this particular openjdk-17 upgrade, even it is a minor
'patch' upgrade, it is vital that _ALL_ java processes that intend to
spawn external processes are immediately terminated, and restarted.
I would suggest a BIG PROMINENT note in the upgrade message for this
particular update, since it is likely to bite a lot of people...
Some references:
https://bugs.openjdk.org/browse/JDK-8310265 ("(process) jspawnhelper
should not use argv[0]") is the bug that eventually changed to the JRE
<--> jspawnhelper protocol
https://github.com/openjdk/jdk17u-dev/commit/cd6cb730c934d8e16d4bd8e3342e59e806f158f9
is the corresponding commit for OpenJDK 17.
https://bugs.openjdk.org/browse/JDK-8325567 ("jspawnhelper without args
fails with segfault") is a related upstream bug. I also noticed the same
after the Ubuntu 17.0.10+7-1~22.04.1 package upgrade, because I tried
running jspawnhelper myself, and the very first invocation (without
arguments) segfaulted. :)
In that bug, Aleksey Shipilev notes:
> So this would only affect whoever is invoking jspawnhelper directly. But that
> would also run into problems when jspawnhelper protocol changes like in
> JDK-8310265.
E.g. it is clear that the jspawnhelper protocol was changed without
taking into account that any "old" JRE process would now run the helper
tool in a way that makes it segfault. I don't think they thought this
through correctly, even though it is an internal JRE implementation
detail...
Bottom line, this is not really an Ubuntu bug in the package, so feel free to
close this ticket, but I would still suggest adding a visible notice that any
running OpenJDK processes should be restarted!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055280
Title:
openjdk-17-jre-headless 17.0.10+7-1~22.04.1: segfault in jspawnhelper
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/2055280/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055280] Re: openjdk-17-jre-headless 17.0.10+7-1~22.04.1: segfault in jspawnhelper
There isn't anything special as far as I know, it's just a plain Ubuntu 22.04 VM which is accessed by Jenkins over SSH. Note that we're using the stable branch Jenkins, which is at 2.440.1, so it may be possible that only that version is buggy. I noticed a `_usr_lib_jvm_java-17-openjdk- amd64_lib_jspawnhelper.1007.crash` file in `/var/crash`, so I could unpack that and throw it in gdb: ``` Core was generated by `41:44'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __rawmemchr_evex () at ../sysdeps/x86_64/multiarch/memchr-evex.S:111 Download failed: Invalid argument. Continuing without source file ./string/../sysdeps/x86_64/multiarch/memchr-evex.S. 111 ../sysdeps/x86_64/multiarch/memchr-evex.S: No such file or directory. (gdb) bt #0 __rawmemchr_evex () at ../sysdeps/x86_64/multiarch/memchr-evex.S:111 #1 0x7f21c298d9e8 in _IO_str_init_static_internal (sf=sf@entry=0x7fffde73e550, ptr=ptr@entry=0x0, size=size@entry=0, pstart=pstart@entry=0x0) at ./libio/strops.c:41 #2 0x7f21c2960323 in _IO_strfile_read (string=0x0, sf=0x7fffde73e550) at ../libio/strfile.h:95 #3 __GI___isoc99_sscanf (s=0x0, format=format@entry=0x55f74431f0a1 "%d:%d") at ./stdio-common/isoc99_sscanf.c:28 #4 0x55f74431d391 in main (argc=, argv=) at src/java.base/unix/native/jspawnhelper/jspawnhelper.c:140 ``` So for some reason, it looks like `argv[0]` is actually "41:44", which results in sscanf() being called on argv[1] which is NULL. I have no idea yet whether this is a Jenkins bug or a Java bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055280 Title: openjdk-17-jre-headless 17.0.10+7-1~22.04.1: segfault in jspawnhelper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/2055280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055280] Re: openjdk-17-jre-headless 17.0.10+7-1~22.04.1: segfault in jspawnhelper
Possibly related: https://issues.jenkins.io/browse/JENKINS-72665 So the question is what the Jenkins agent does: I'm not sure it invokes jspawnhelper directly, I assume it is going via the Java API, but there could be some other bug that causes it to pass incorrect arguments to jspawnhelper. It looks like the command line interface of jspawnhelper is not very bullet proof, which is understandable since it's not meant to be run directly. But still, segfaulting is bad :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055280 Title: openjdk-17-jre-headless 17.0.10+7-1~22.04.1: segfault in jspawnhelper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/2055280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055280] [NEW] openjdk-17-jre-headless 17.0.10+7-1~22.04.1: segfault in jspawnhelper
Public bug reported: We recently upgraded a bunch of Jenkins build machines that run Ubuntu 22.04.04 LTS to openjdk-17-jre-headless_17.0.10+7-1~22.04.1. Shortly after, all the Jenkins agents running on these machines were getting segfaults in jspawnhelper, when the JRE tried to spawn an external shell to run build jobs: $ /bin/sh -xe /tmp/jenkins1281456674251232.sh FATAL: command execution failed java.io.IOException: error=0, Failed to exec spawn helper: pid: 1291715, signal: 11 at java.base/java.lang.ProcessImpl.forkAndExec(Native Method) at java.base/java.lang.ProcessImpl.(ProcessImpl.java:314) at java.base/java.lang.ProcessImpl.start(ProcessImpl.java:244) at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1110) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to ubuntu22-amd64-docker-3 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1787) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:1003) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1121) at hudson.Launcher$ProcStarter.start(Launcher.java:506) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:144) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:92) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:818) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:164) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:526) at hudson.model.Run.execute(Run.java:1895) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) I'm unsure how Jenkins's agent exactly invokes jspawnhelper, but I assume it just uses Java's regular API to run external processes, as shown in the above stack trace. I.e. it uses java.lang.ProcessBuilder, which implicitly invokes its java.lang.ProcessImpl.forkAndExec method. And finally I assume that java.lang.ProcessImpl.forkAndExec somehow forks jspawnhelper to do its thing. In any case, with 17.0.10+7-1~22.04.1 this almost always results in a segfault now, which the previous version of openjdk-17-jre-headless never did. So it is some sort of regression. For now, I have downgraded to the release version, which is 17.0.2+8-1, since the previous security update version has disappeared from the Ubuntu mirrors. I have not yet dug any deeper since I have a lack of time to spend on it, but I wanted to make this bug report so other people experiencing this might be able to find it on Launchpad. ** Affects: openjdk-17 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055280 Title: openjdk-17-jre-headless 17.0.10+7-1~22.04.1: segfault in jspawnhelper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-17/+bug/2055280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967575] Re: VAAPI is broken in 22.04 (22.3.0+dfsg1-1)
Thanks, I can confirm that 22.3.0+dfsg1-1build1 works. (I manually installed the .deb, as it was not yet available via apt-get.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967575 Title: VAAPI is broken in 22.04 (22.3.0+dfsg1-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1967575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967575] Re: VAAPI is broken in 22.04 (22.3.0+dfsg1-1)
Note: if I download: * intel-media-driver-non-free_22.3.0+ds1-1.dsc * intel-media-driver-non-free_22.3.0+ds1.orig.tar.xz * intel-media-driver-non-free_22.3.0+ds1-1.debian.tar.xz then unpack and rebuild them with dpkg-buildpackage on my own Jammy system, the resulting deb appears to work correctly, as in: * vainfo loads /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so and works OK * /usr/share/mfx/samples/sample_decode can decode a H.264 video in hardware OK So maybe the published .deb files have been built against some incorrect dependency? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967575 Title: VAAPI is broken in 22.04 (22.3.0+dfsg1-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1967575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967575] Re: VAAPI is broken in 22.04 (22.3.0+dfsg1-1)
Bug 1966571 supposedly fixed this, with "Rebuild with the current libva version (lp: #1966571)", for package version 22.2.1+dfsg1-1build1, but that specific build unfortunately disappeared from the ubuntu archive. But indeed now it's broken again; not sure what Sebastien Bacher did for bug 1966571 to fix it, except rebuilding against a different version of libva? Or something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967575 Title: VAAPI is broken in 22.04 (22.3.0+dfsg1-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1967575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937945] [NEW] old gpg keyserver no longer works
Public bug reported:
This is with lxc 1:4.0.6-0ubuntu1~20.04.1 on Ubuntu 20.04 LTS.
All lxc-create commands that need to download GPG keys fail with
something similar to:
$ lxc-create -n foobar -t download -- -d ubuntu -r focal -a amd64
The cached copy has expired, re-downloading...
Setting up the GPG keyring
ERROR: Unable to fetch GPG key from keyserver
lxc-create: foobar: lxccontainer.c: create_run_template: 1616 Failed to create
container from template
It turns out that the GPG keyserver used (pool.sks-keyservers.net) no
longer produces the expected responses. Upstream lxc has a ticket for
this:
https://github.com/lxc/lxc/issues/3894 ('lxc-create fails because
"ERROR: Unable to fetch GPG key from keyserver')
and it was fixed by changing:
DOWNLOAD_KEYSERVER="hkp://pool.sks-keyservers.net"
to:
DOWNLOAD_KEYSERVER="hkp://keyserver.ubuntu.com"
in this commit:
https://github.com/lxc/lxc/commit/f2a5d95d00a55bed27ef9920d67617cc75fecad8
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937945
Title:
old gpg keyserver no longer works
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1937945/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Can you please show the output of: apt-key export C8CAB6595FDFF622 | gpg --list-packets ? I guess for some reason your apt keyring isn't updated correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)
Note: this is a duplicate of bug #1920610, which was submitted a few hours earlier. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920640 Title: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920610] Re: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed
Note: a duplicate bug #1920640 was added a few hours after this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920610 Title: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920610] Re: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed
The GPG key has simply expired, as of 2021-03-20: $ wget -q http://ddebs.ubuntu.com/dists/focal-proposed/Release http://ddebs.ubuntu.com/dists/focal-proposed/Release.gpg $ gpg --verify Release.gpg Release gpg: Signature made Fri 19 Mar 2021 04:52:53 AM CET gpg:using RSA key 0xC8CAB6595FDFF622 gpg: Good signature from "Ubuntu Debug Symbol Archive Automatic Signing Key (2016) " [expired] gpg: Note: This key has expired! Primary key fingerprint: F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 $ gpg --list-key 0xC8CAB6595FDFF622 pub rsa4096/0xC8CAB6595FDFF622 2016-03-21 [SC] [expired: 2021-03-20] Key fingerprint = F2ED C64D C5AE E1F6 B9C6 21F0 C8CA B659 5FDF F622 uid [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key (2016) Time to generate a new key and distribute it, I guess. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920610 Title: The repository 'http://ddebs.ubuntu.com groovy Release' is not signed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1920610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 333608] Re: deskbar-applet crashed with SIGSEGV in PyType_IsSubtype()
Looks like comment #32 here: http://bugzilla.gnome.org/show_bug.cgi?id=577649#c32 and its followups seem to fix the problem. When I remove the inheritance of gobject in GnomeURLopener, the crash goes away. There is a more complete patch at http://bugzilla.gnome.org/attachment.cgi?id=132271action=view , which is apparently already commited in the upstream version. It applies fine, though the file locations are a bit different in Ubuntu, and also solves the crash, at least for me. -- deskbar-applet crashed with SIGSEGV in PyType_IsSubtype() https://bugs.launchpad.net/bugs/333608 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 333608] Re: deskbar-applet crashed with SIGSEGV in PyType_IsSubtype()
Here's a hopefully useful stack trace: GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu... (gdb) run Starting program: /usr/bin/python /usr/lib/deskbar-applet/deskbar-applet -d [Thread debugging using libthread_db enabled] [New Thread 0x7f4eac4076f0 (LWP 5237)] 04-09 11:10:36 root INFO Starting Deskbar instance: gnome.applet.Applet object at 0x25411e0 (PanelApplet at 0x25b) OAFIID:Deskbar_Applet 04-09 11:10:36 deskbar.core.Keybinder INFO Binding Global shortcut AltF3 to focus the deskbar 04-09 11:10:36 deskbar.core.CoreImpl INFO Successfully binded Deskbar to AltF3 04-09 11:10:36 deskbar.core.ModuleLoader WARNING Class EpiphanyBookmarksHandler in file /usr/lib/deskbar-applet/modules-2.20-compatible/epiphany.py has missing requirements. Skipping. 04-09 11:10:36 deskbar.core.ModuleLoader WARNING Class EpiphanyHistoryHandler in file /usr/lib/deskbar-applet/modules-2.20-compatible/epiphany.py has missing requirements. Skipping. 04-09 11:10:36 deskbar.core.ModuleLoader WARNING Class EpiphanySearchHandler in file /usr/lib/deskbar-applet/modules-2.20-compatible/epiphany.py has missing requirements. Skipping. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'Programs' from file /usr/lib/deskbar-applet/modules-2.20-compatible/programs.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'Dictionary' from file /usr/lib/deskbar-applet/modules-2.20-compatible/programs.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'Files and Folders Search' from file /usr/lib/deskbar-applet/modules-2.20-compatible/programs.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'Developer Documentation' from file /usr/lib/deskbar-applet/modules-2.20-compatible/programs.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'Tomboy Notes' from file /usr/lib/deskbar-applet/modules-2.20-compatible/tomboy.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'Web' from file /usr/lib/deskbar-applet/modules-2.20-compatible/web_address.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'OpenSearch' from file /usr/lib/deskbar-applet/modules-2.20-compatible/opensearch.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'Calculator' from file /usr/lib/deskbar-applet/modules-2.20-compatible/calculator.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'del.icio.us Bookmarks' from file /usr/lib/deskbar-applet/modules-2.20-compatible/desklicious.py. 04-09 11:10:36 deskbar.core.ModuleLoader INFO Loading module 'Computer Actions' from file /usr/lib/deskbar-applet/modules-2.20-compatible/gdmactions.py. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f4eac4076f0 (LWP 5237)] PyType_IsSubtype (a=0xfffd, b=0x7f4eaa26e6a0) at ../Objects/typeobject.c:1157 1157../Objects/typeobject.c: No such file or directory. in ../Objects/typeobject.c (gdb) bt #0 PyType_IsSubtype (a=0xfffd, b=0x7f4eaa26e6a0) at ../Objects/typeobject.c:1157 #1 0x7f4eaa0599fc in pyg_type_add_interfaces (class=0x292d530, instance_type=42386864, bases=0x28ea5a8, new_interfaces=0, parent_interfaces=0x288c7e0, n_parent_interfaces=0) at /build/buildd/pygobject-2.16.1/gobject/gobjectmodule.c:1088 #2 0x7f4eaa059d23 in pyg_type_register (class=0x292d530, type_name=value optimized out) at /build/buildd/pygobject-2.16.1/gobject/gobjectmodule.c:1237 #3 0x7f4eaa05ab78 in _wrap_pyg_type_register (self=value optimized out, args=value optimized out) at /build/buildd/pygobject-2.16.1/gobject/gobjectmodule.c:954 #4 0x004a2b03 in PyEval_EvalFrameEx (f=0x1b8e9c0, throwflag=value optimized out) at ../Python/ceval.c:3706 #5 0x004a3dae in PyEval_EvalFrameEx (f=0x1b281c0, throwflag=value optimized out) at ../Python/ceval.c:3792 #6 0x004a4649 in PyEval_EvalCodeEx (co=0x7f4eac327468, globals=value optimized out, locals=value optimized out, args=0x28d1590, argcount=4, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:2968 #7 0x005329ad in function_call (func=0x7f4eac2676e0, arg=0x28d1578, kw=0x0) at ../Objects/funcobject.c:524 #8 0x0041d3bd in PyObject_Call (func=0x7f4eac2676e0, arg=0x28d1578, kw=0x0) at ../Objects/abstract.c:2492 #9 0x00424f48 in instancemethod_call (func=0x7f4eac2676e0, arg=0x28d1578, kw=0x0) at ../Objects/classobject.c:2579 #10 0x0041d3bd in PyObject_Call (func=0x27cb9b0, arg=0x28bd9b0, kw=0x0) at ../Objects/abstract.c:2492 #11 0x0047413c in slot_tp_init (self=0x292d530, args=0x28bd9b0,
[Bug 312105] Re: [jaunty] Cannot change eth0 properties (greyed out)
I have exactly the same problem, on two Jauntu boxes (up-to-date on 2009-03-02). On the box I'm currently using: $ polkit-auth --show-obtainable org.freedesktop.consolekit.system.stop-multiple-users org.freedesktop.consolekit.system.restart-multiple-users org.freedesktop.policykit.read org.freedesktop.policykit.revoke org.freedesktop.policykit.grant org.freedesktop.policykit.modify-defaults com.ubuntu.systemservice.setproxy com.ubuntu.systemservice.setnoproxy com.ubuntu.systemservice.setkeyboard org.freedesktop.hal.device-access.modem org.freedesktop.hal.device-access.ppdev org.freedesktop.network-manager-settings.system.modify org.gnome.clockapplet.mechanism.settimezone org.gnome.clockapplet.mechanism.settime org.gnome.clockapplet.mechanism.configurehwclock org.freedesktop.hal.storage.mount-fixed org.freedesktop.hal.storage.unmount-others org.freedesktop.hal.storage.crypto-setup-fixed com.ubuntu.screenresolution.mechanism.configure com.ubuntu.screenresolution.mechanism.dontzap org.gnome.cpufreqselector org.freedesktop.systemtoolsbackends.set org.freedesktop.systemtoolsbackends.self.set org.gnome.gconf.defaults.set-system org.gnome.gconf.defaults.set-mandatory org.freedesktop.hal.power-management.shutdown-multiple-sessions org.freedesktop.hal.power-management.reboot-multiple-sessions com.ubuntu.devicedriver.install $ ck-list-sessions Session8: unix-user = '1000' realname = 'Dimitry Andric,,,' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2009-03-02T21:57:04.909821Z' login-session-id = '4294967295' -- [jaunty] Cannot change eth0 properties (greyed out) https://bugs.launchpad.net/bugs/312105 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295127] Re: libpar-perl won't install on intrepid due to libfile-temp-perl (= 0.05) dependency
Hi maintainer, can you please either apply the proposed fix to intrepid, or close the bug if you don't want or don't care about the fix? Then it won't keep cluttering the bug database at least... Thanks. -- libpar-perl won't install on intrepid due to libfile-temp-perl (= 0.05) dependency https://bugs.launchpad.net/bugs/295127 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286792] Re: Crash in CompositeTrapezoids+0x9b
On intrepid, using the debs from https://edge.launchpad.net/~intel-gfx- testing/+archive, I get precisely the same backtrace as before: Backtrace: 0: /usr/X11R6/bin/X(xorg_backtrace+0x26) [0x4ee236] 1: /usr/X11R6/bin/X(mieqEnqueue+0x23f) [0x4cebbf] 2: /usr/X11R6/bin/X(xf86PostKeyboardEvent+0x85) [0x487785] 3: /usr/lib/xorg/modules/input//evdev_drv.so [0x7f3e5b3189de] 4: /usr/X11R6/bin/X [0x498df5] 5: /usr/X11R6/bin/X [0x473457] 6: /lib/libpthread.so.0 [0x7f3e7498b0f0] 7: /lib/libc.so.6(ioctl+0x7) [0x7f3e72feda17] 8: /usr/lib/libdrm.so.2(drmIoctl+0x23) [0x7f3e71bc8383] 9: /usr/lib/libdrm.so.2(drmCommandWrite+0x1b) [0x7f3e71bc860b] 10: /usr/lib/dri/i915_dri.so(intelWaitIrq+0x60) [0x7f3e60cb7e00] 11: /usr/lib/dri/i915_dri.so [0x7f3e60cb4449] 12: /usr/lib/dri/i915_dri.so [0x7f3e60c94ebe] 13: /usr/lib/dri/i915_dri.so [0x7f3e60c959fd] 14: /usr/lib/dri/i915_dri.so [0x7f3e60c95ca0] 15: /usr/lib/dri/i915_dri.so(_intel_batchbuffer_flush+0xa7) [0x7f3e60c9d4c7] 16: /usr/lib/dri/i915_dri.so [0x7f3e60cb2a2f] 17: /usr/lib/dri/i915_dri.so(intelStartInlinePrimitive+0x2f) [0x7f3e60cc071f] 18: /usr/lib/dri/i915_dri.so [0x7f3e60c9bc30] 19: /usr/lib/dri/i915_dri.so [0x7f3e60c9b398] 20: /usr/lib/dri/i915_dri.so(_tnl_run_pipeline+0x15f) [0x7f3e60d5c53f] 21: /usr/lib/dri/i915_dri.so [0x7f3e60cc03f4] 22: /usr/lib/dri/i915_dri.so(_tnl_draw_prims+0x4e0) [0x7f3e60d5cb00] 23: /usr/lib/dri/i915_dri.so [0x7f3e60d5568e] 24: /usr/lib/xorg/modules/extensions//libglx.so [0x7f3e7241d5bd] 25: /usr/lib/xorg/modules/extensions//libglx.so [0x7f3e72417a66] 26: /usr/lib/xorg/modules/extensions//libglx.so [0x7f3e7241bbd2] 27: /usr/X11R6/bin/X(Dispatch+0x364) [0x44d754] 28: /usr/X11R6/bin/X(main+0x45d) [0x43376d] 29: /lib/libc.so.6(__libc_start_main+0xe6) [0x7f3e72f2d466] 30: /usr/X11R6/bin/X [0x432b49] So no change there... I'll see if I can try out the real bleeding edge packages from https://edge.launchpad.net/~xorg-edgers :) -- Crash in CompositeTrapezoids+0x9b https://bugs.launchpad.net/bugs/286792 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 260815] Re: libvnc.so Xorg module failes to load
The NumCurrentSelections is an old API, which was explicitly removed from xserver, see this commit: http://cgit.freedesktop.org/xorg/xserver/commit/?id=34bf308a9e66f1a2f48630a15b1802afad50ec24 E.g. somebody should rewrite vncserver to not depend on this obsolete export anymore... :) -- libvnc.so Xorg module failes to load https://bugs.launchpad.net/bugs/260815 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295127] Re: libpar-perl won't install on intrepid due to libfile-temp-perl (= 0.05) dependency
Can this simple fix also be backported to intrepid, please? The package is now unusable there... -- libpar-perl won't install on intrepid due to libfile-temp-perl (= 0.05) dependency https://bugs.launchpad.net/bugs/295127 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 286792] Re: Fatal server error: lockup
I have the same mieqEnqueue: infinite loop error on intrepid, with xserver-xorg-video-intel 2:2.4.1-1ubuntu10. This only happens when desktop effects (e.g. AIGLX) is turned on, and if the X server is restarted twice (e.g. you login, do some stuff, logout and attempt to login again). There's a patch floating around to get a backtrace whenever the server gets stuck. In my case, this gives: Backtrace: 0: /usr/X11R6/bin/X(xorg_backtrace+0x26) [0x4edc76] 1: /usr/X11R6/bin/X(mieqEnqueue+0x23f) [0x4ce5ff] 2: /usr/X11R6/bin/X(xf86PostMotionEventP+0xc4) [0x473654] 3: /usr/X11R6/bin/X(xf86PostMotionEvent+0xb1) [0x473831] 4: /usr/lib/xorg/modules/input//evdev_drv.so [0x7fd34fe6083f] 5: /usr/X11R6/bin/X [0x48fd45] 6: /usr/X11R6/bin/X [0x470267] 7: /lib/libpthread.so.0 [0x7fd3696860f0] 8: /lib/libc.so.6(ioctl+0x7) [0x7fd367ce8a17] 9: /usr/lib/libdrm.so.2(drmCommandWrite+0x1d) [0x7fd3668c4aed] 10: /usr/lib/dri/i915_dri.so(intelWaitIrq+0x60) [0x7fd355767d00] 11: /usr/lib/dri/i915_dri.so [0x7fd355764349] 12: /usr/lib/dri/i915_dri.so [0x7fd355744e0e] 13: /usr/lib/dri/i915_dri.so [0x7fd35574590d] 14: /usr/lib/dri/i915_dri.so [0x7fd355745bb0] 15: /usr/lib/dri/i915_dri.so(_intel_batchbuffer_flush+0xa7) [0x7fd35574d3d7] 16: /usr/lib/dri/i915_dri.so [0x7fd35576292f] 17: /usr/lib/dri/i915_dri.so(intelStartInlinePrimitive+0x2f) [0x7fd35577061f] 18: /usr/lib/dri/i915_dri.so [0x7fd35574bb40] 19: /usr/lib/dri/i915_dri.so [0x7fd35574b2a8] 20: /usr/lib/dri/i915_dri.so(_tnl_run_pipeline+0x15f) [0x7fd35580c3ef] 21: /usr/lib/dri/i915_dri.so [0x7fd3557702f4] 22: /usr/lib/dri/i915_dri.so(_tnl_draw_prims+0x4e0) [0x7fd35580c9b0] 23: /usr/lib/dri/i915_dri.so [0x7fd35580553e] 24: /usr/lib/xorg/modules/extensions//libglx.so [0x7fd3671185bd] 25: /usr/lib/xorg/modules/extensions//libglx.so [0x7fd367112a66] 26: /usr/lib/xorg/modules/extensions//libglx.so [0x7fd367116bd2] 27: /usr/X11R6/bin/X(Dispatch+0x364) [0x44d714] 28: /usr/X11R6/bin/X(main+0x45d) [0x43372d] 29: /lib/libc.so.6(__libc_start_main+0xe6) [0x7fd367c28466] 30: /usr/X11R6/bin/X [0x432b09] [mi] mieqEnqueue: server stuck, please see backtrace above. [mi] mieqEnqueue: server stuck, please see backtrace above. [...endless, server is not responsive anymore...] So what is going wrong here? :) Please note, I have run this exact same box using hardy for a long time, and never encountered any problem with X, even if you restart it dozens of times. I guess this must be some regression in either libdrm or the intel driver... -- Fatal server error: lockup https://bugs.launchpad.net/bugs/286792 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295127] [NEW] libpar-perl won't install on intrepid due to libfile-temp-perl (= 0.05) dependency
Public bug reported: Binary package hint: libpar-perl Attempting to installing libpar-perl (0.980-1) on intrepid gives: $ sudo apt-get install libpar-perl Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: libpar-perl: Depends: libfile-temp-perl (= 0.05) E: Broken packages It seems that in intrepid, libfile-temp-perl is provided by the perl- modules package, but it looks like this doesn't contain any version number. I've seen that in the jaunty version of this package, the libfile-temp-perl dependency has had its version number removed: diff -Nru /tmp/gN3tZ7472W/libpar-perl-0.980/debian/control /tmp/D51uOGgGlB/libpar-perl-0.983/debian/control --- libpar-perl-0.980/debian/control2008-11-05 22:27:21.0 + +++ libpar-perl-0.983/debian/control2008-11-05 22:27:21.0 + [...] - libcompress-zlib-perl (= 1.3), libfile-temp-perl (= 0.05) + libcompress-zlib-perl (= 1.3), libfile-temp-perl Can you please change it for the intrepid package too? Thanks! ** Affects: libpar-perl (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Package won't install on intrepid due to libfile-temp-perl (= 0.05) dependency + libpar-perl won't install on intrepid due to libfile-temp-perl (= 0.05) dependency -- libpar-perl won't install on intrepid due to libfile-temp-perl (= 0.05) dependency https://bugs.launchpad.net/bugs/295127 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204850] Re: gnome-settings-daemon crashed with SIGSEGV in gsd_mouse_manager_start()
I'm having precisely the same problem as the people in this bug report,
and almost exactly the same backtrace. :)
I downloaded the debug symbols, and this is what I got:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f1966f937a0 (LWP 19394)]
set_touchpad_enabled (state=value optimized out) at gsd-mouse-manager.c:420
420 gsd-mouse-manager.c: No such file or directory.
in gsd-mouse-manager.c
(gdb) bt
#0 set_touchpad_enabled (state=value optimized out) at gsd-mouse-manager.c:420
#1 0x7f195a26a8cd in gsd_mouse_manager_start (manager=0x660af0,
error=value optimized out) at gsd-mouse-manager.c:836
#2 0x7f195a2697f7 in impl_activate (plugin=0x660ac0) at
gsd-mouse-plugin.c:78
#3 0x00404f0c in gnome_settings_plugin_info_activate ()
#4 0x00403c85 in ?? ()
#5 0x7f1962928e0d in g_slist_foreach () from /usr/lib/libglib-2.0.so.0
#6 0x00403e94 in gnome_settings_manager_start ()
#7 0x00403ad8 in main ()
(gdb) print devicelist
$1 = (XDeviceInfo *) 0x0
(gdb) print numdevices
$2 = 32537
In my case, I'm running a GNOME session under VNC server, which does NOT
support the XInputExtension. However, the set_touchpad_enabled()
function in plugins/mouse/gsd-mouse-manager.c (which was introduced by
debian/patches/08_extra_touchpad_options.patch) uses XListInputDevices()
to get a list anyway:
static int
set_touchpad_enabled (gboolean state)
{
int numdevices, i;
int values[2];
XDeviceInfo *devicelist = XListInputDevices (GDK_DISPLAY(),
numdevices);
[...]
for (i = 0; i numdevices; i++) {
if (strcmp (devicelist[i].name, Synaptics Touchpad) == 0) {
The problem, as you can see in the gdb conversation above, is that if
devicelist is NULL, numdevices is *not* set to zero by the call to
XListInputDevices. Later on, the for loop will segfault in the first
strcmp() call.
I've attached a patch which fixes at least this particular problem.
** Attachment added: Fix segfault in
plugins/mouse/gsd-mouse-manager.c:set_touchpad_enabled()
http://launchpadlibrarian.net/17058549/09_extra_touchpad_options_fix.patch
--
gnome-settings-daemon crashed with SIGSEGV in gsd_mouse_manager_start()
https://bugs.launchpad.net/bugs/204850
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146946] Re: Gnome settings daemon randomly does not work
Sorry for the pollution, I've filed my story under bug 204850 here: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/204850/comments/9 -- Gnome settings daemon randomly does not work https://bugs.launchpad.net/bugs/146946 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199245] Re: gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
I have approximately the same crash here. It looks like the gsd- keyboard-xkb filter gets a CreateWindow notification event, but the window id isn't valid anymore (maybe the window already disappeared?), for an unknown reason. When the xklavier engine tries to get the Window's title property, it gets the BadWindow error: #0 gdk_x_error (display=value optimized out, error=0x7fff588b82f0) at /home/dim/deb/gtk+2.0-2.12.9/gdk/x11/gdkmain-x11.c:623 #1 0x7fab4e307b6d in _XError (dpy=0x6288c0, rep=0x778110) at ../../src/XlibInt.c:2905 #2 0x7fab4e30f068 in _XReply (dpy=0x6288c0, rep=0x7fff588b83f4, extra=0, discard=0) at ../../src/xcb_io.c:417 #3 0x7fab4e2edb3d in XGetWindowProperty (dpy=0x6288c0, w=37749790, property=39, offset=0, length=-1, delete=0, req_type=31, actual_type=0x7fff588b8508, actual_format=0x7fff588b8514, nitems=0x7fff588b8500, bytesafter=0x7fff588b84f8, prop=0x7fff588b84f0) at ../../src/GetProp.c:64 #4 0x7fab43f9c8a7 in xkl_engine_get_window_title (engine=value optimized out, w=3) at xklavier_util.c:53 #5 0x7fab43f9c905 in xkl_get_debug_window_title (engine=0x6288c0, win=3) at xklavier_util.c:122 #6 0x7fab43f97359 in xkl_engine_process_focus_out_evt (engine=0x6288c0, fev=0x7fff588b8780) at xklavier_evt.c:336 #7 0x7fab43f97a79 in xkl_engine_filter_events (engine=0x68e920, xev=0x3) at xklavier_evt.c:44 #8 0x7fab445b8036 in gsd_keyboard_xkb_evt_filter (xev=0x3, event=value optimized out) at gsd-keyboard-xkb.c:282 #9 0x7fab4fe7a14c in gdk_event_apply_filters (xevent=0x7fff588b8780, event=0x779740, filters=value optimized out) at /home/dim/deb/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c:345 #10 0x7fab4fe7b7f6 in gdk_event_translate (display=0x633110, event=0x3, xevent=0x7fff588b8780, return_exposes=0) at /home/dim/deb/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c:896 #11 0x7fab4fe7d142 in _gdk_events_queue (display=0x633110) at /home/dim/deb/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c:2285 #12 0x7fab4fe7d55e in gdk_event_dispatch (source=value optimized out, callback=0x3, user_data=0x0) at /home/dim/deb/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c:2345 #13 0x7fab4c2043d4 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #14 0x7fab4c2076e5 in ?? () from /usr/lib/libglib-2.0.so.0 #15 0x7fab4c207a05 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #16 0x7fab50213f03 in IA__gtk_main () at /home/dim/deb/gtk+2.0-2.12.9/gtk/gtkmain.c:1163 #17 0x00403949 in main () -- gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc https://bugs.launchpad.net/bugs/199245 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199245] Re: gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc
Okay, I've done some serious digging, and it looks like a window is created (in my case it's mostly gnome-screensaver), but it disappears *before* the CreateNotify goes out. This is because gnome-screensaver complains that it's already running, and immediately quits. Thus it doesn't seem to call XDestroyWindow, and apparently the events belonging to the window aren't ditched somehow. Is anyone seeing these BadWindow errors when they're *not* under Xvnc ? -- gnome-settings-daemon crash opening any window: BadWindow X error under Xvnc https://bugs.launchpad.net/bugs/199245 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 204850] Re: gnome-settings-daemon crashed with SIGSEGV in gsd_mouse_manager_start()
Yes, that BadWindow error is indeed the next error. You can duct-tape- fix it using your patch, or by simply disabling the gnome-settings- daemon keyboard plugin (using gconf-editor). The BadWindow error is researched in bug 199245, bug 254671, and possibly others (even http://bugzilla.gnome.org/show_bug.cgi?id=537592)... but it's a strange one, looks like some race condition or bad event interaction. -- gnome-settings-daemon crashed with SIGSEGV in gsd_mouse_manager_start() https://bugs.launchpad.net/bugs/204850 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146946] Re: Gnome settings daemon randomly does not work
Well, since set_touchpad_enabled() and other functions that were introduced by 08_extra_touchpad_options.patch also didn't contain any #ifdef HAVE_XINPUT sections, I thought it would be a bit overkill. It all depends on whether the extra_touchpad_options code will be sent upstream later. If that's the case, it should probably be cleaned up a little more anyway. Any idea if it's going to be sent upstream? As to the issue other people in this bug report have, when I apply my own fix, gnome-settings-daemon does startup now, but sooner or later I also get the dreaded The program 'gnome-settings-daemon' received an X Window System error message. :) So back to stack-tracing again... -- Gnome settings daemon randomly does not work https://bugs.launchpad.net/bugs/146946 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146946] Re: Gnome settings daemon randomly does not work
I'm having precisely the same problem as BruceBeare, and almost exactly
the same backtrace. :)
I downloaded the debug symbols, and this is what I got:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f1966f937a0 (LWP 19394)]
set_touchpad_enabled (state=value optimized out) at gsd-mouse-manager.c:420
420 gsd-mouse-manager.c: No such file or directory.
in gsd-mouse-manager.c
(gdb) bt
#0 set_touchpad_enabled (state=value optimized out) at
gsd-mouse-manager.c:420
#1 0x7f195a26a8cd in gsd_mouse_manager_start (manager=0x660af0,
error=value optimized out) at gsd-mouse-manager.c:836
#2 0x7f195a2697f7 in impl_activate (plugin=0x660ac0) at
gsd-mouse-plugin.c:78
#3 0x00404f0c in gnome_settings_plugin_info_activate ()
#4 0x00403c85 in ?? ()
#5 0x7f1962928e0d in g_slist_foreach () from /usr/lib/libglib-2.0.so.0
#6 0x00403e94 in gnome_settings_manager_start ()
#7 0x00403ad8 in main ()
(gdb) print devicelist
$1 = (XDeviceInfo *) 0x0
(gdb) print numdevices
$2 = 32537
In my case, I'm running a GNOME session under VNC server, which does NOT
support the XInputExtension. However, the set_touchpad_enabled()
function in plugins/mouse/gsd-mouse-manager.c (which was introduced by
debian/patches/08_extra_touchpad_options.patch) uses XListInputDevices()
to get a list anyway:
static int
set_touchpad_enabled (gboolean state)
{
int numdevices, i;
int values[2];
XDeviceInfo *devicelist = XListInputDevices (GDK_DISPLAY(),
numdevices);
[...]
for (i = 0; i numdevices; i++) {
if (strcmp (devicelist[i].name, Synaptics Touchpad) == 0) {
The problem, as you can see in the gdb conversation above, is that if
devicelist is NULL, numdevices is *not* set to zero by the call to
XListInputDevices. Later on, the for loop will segfault in the first
strcmp() call.
I've attached a patch which fixes at least this particular problem.
** Attachment added: Fix segfault in
plugins/mouse/gsd-mouse-manager.c:set_touchpad_enabled()
http://launchpadlibrarian.net/17041472/09_extra_touchpad_options_fix.patch
--
Gnome settings daemon randomly does not work
https://bugs.launchpad.net/bugs/146946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 146946] Re: Gnome settings daemon randomly does not work
Sorry, that patch contains a typo... That'll teach me to test compilation before uploading. ;) Revised patch attached. ** Attachment added: Fix segfault in plugins/mouse/gsd-mouse-manager.c:set_touchpad_enabled() (rev 2) http://launchpadlibrarian.net/17041631/09_extra_touchpad_options_fix.patch -- Gnome settings daemon randomly does not work https://bugs.launchpad.net/bugs/146946 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94368] Re: Hardware database applet crashes when no xorg.conf file is present
** Attachment added: Dependencies.txt http://librarian.launchpad.net/6880883/Dependencies.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/6880884/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/6880885/ProcStatus.txt ** Attachment added: Traceback.txt http://librarian.launchpad.net/6880886/Traceback.txt -- Hardware database applet crashes when no xorg.conf file is present https://launchpad.net/bugs/94368 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94368] Hardware database applet crashes when no xorg.conf file is present
Public bug reported: Binary package hint: hwdb-client - Remove xorg.conf - Start X.org (should start without problems on most systems) - Start hardware database applet - Fill in questions - When you get to the assembling data screen, you'll get a python exception about the missing xorg.conf file. ProblemType: Crash Architecture: i386 Date: Wed Mar 21 10:47:13 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/hwdb-xml InterpreterPath: /usr/bin/python2.5 Package: hwdb-client-common 0.6.6 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/hwdb-xml -a ProcCwd: /home/dim ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=C SHELL=/bin/bash PythonArgs: ['/usr/bin/hwdb-xml', '-a'] SourcePackage: hwdb-client Uname: Linux lance 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux ** Affects: hwdb-client (Ubuntu) Importance: Undecided Status: Unconfirmed -- Hardware database applet crashes when no xorg.conf file is present https://launchpad.net/bugs/94368 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
