GNOME Bugzilla – Bug 532525
Crash on adding accounts
Last modified: 2008-05-18 09:43:46 UTC
Steps to reproduce: 1. On Fedora 9, with selinux running (that selinux is enabled may be a red herring) 2. Use the accounts dialog add an account 3. Note that on clicking "ok" the application crashes Stack trace: An strace provides the following 1. socket(PF_INET, SOCK_DGRAM, IPPROTO_IP) = 47 2. ioctl(47, FIONBIO, [1]) = 0 3. fcntl64(47, F_SETFD, FD_CLOEXEC) = 0 4. ioctl(47, SIOCGIFCONF, {96, {{"lo", {AF_INET, inet_addr("127.0.0.1")}}, {"wlan0", {AF_INET, inet_addr("192.168.1.106")}}, {"virbr0", {AF_INET, inet_addr("192.168.122.1")}}}}) = 0 5. ioctl(47, SIOCGIFFLAGS, {ifr_name="lo", ifr_flags=IFF_UP|IFF_LOOPBACK|IFF_RUNNING}) = 0 6. ioctl(47, SIOCGIFHWADDR, {ifr_name="lo", ifr_hwaddr=00:00:00:00:00:00}) = 0 7. ioctl(47, SIOCGIFADDR, {ifr_name="lo", ifr_addr={AF_INET, inet_addr("127.0.0.1")}}) = 0 8. ioctl(47, SIOCGIFNETMASK, {ifr_name="lo", ifr_netmask={AF_INET, inet_addr("255.0.0.0")}}) = 0 9. ioctl(47, SIOCGIFFLAGS, {ifr_name="wlan0", ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_MULTICAST}) = 0 10. ioctl(47, SIOCGIFHWADDR, {ifr_name="wlan0", ifr_hwaddr=00:18:de:72:01:af}) = 0 11. ioctl(47, SIOCGIFADDR, {ifr_name="wlan0", ifr_addr={AF_INET, inet_addr("192.168.1.106")}}) = 0 12. ioctl(47, SIOCGIFNETMASK, {ifr_name="wlan0", ifr_netmask={AF_INET, inet_addr("255.255.255.0")}}) = 0 13. ioctl(47, SIOCGIFFLAGS, {ifr_name="virbr0", ifr_flags=IFF_UP|IFF_BROADCAST|IFF_RUNNING|IFF_MULTICAST}) = 0 14. ioctl(47, SIOCGIFHWADDR, {ifr_name="virbr0", ifr_hwaddr=da:5a:8b:1e:97:6f}) = 0 15. ioctl(47, SIOCGIFADDR, {ifr_name="virbr0", ifr_addr={AF_INET, inet_addr("192.168.122.1")}}) = 0 16. ioctl(47, SIOCGIFNETMASK, {ifr_name="virbr0", ifr_netmask={AF_INET, inet_addr("255.255.255.0")}}) = 0 17. shutdown(47, 2 /* send and receive */) = -1 ENOTCONN (Transport endpoint is not connected) 18. close(47) = 0 19. --- SIGSEGV (Segmentation fault) @ 0 (0) --- Other information: I manually added an account to the gconf keys, after doing that I get a crash with the following output bash-3.2$ ekiga 6ec4f46d-435c-80bd-43b7c337-4bbbb32c is dumped This may be a Fedora specific bug. Will provide a gdb stacktrace later.
GDB stacktrace (from bug-buddy): Distribution: Fedora release 9 (Sulphur) Gnome Release: 2.22.1 2008-04-30 (Red Hat, Inc) BugBuddy Version: 2.22.0 System: Linux 2.6.25-14.fc9.i686 #1 SMP Thu May 1 06:28:41 EDT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10499901 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 105746432 vsize: 105746432 resident: 31010816 share: 20209664 rss: 31010816 rss_rlim: 4294967295 CPU usage: start_time: 1210448763 rtime: 125 utime: 109 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/ekiga' [?1034h[Thread debugging using libthread_db enabled] [New Thread 0xb7eed730 (LWP 4275)] [New Thread 0xb4c20b90 (LWP 4287)] [New Thread 0xb4c61b90 (LWP 4286)] [New Thread 0xb4cb9b90 (LWP 4284)] [New Thread 0xb56bab90 (LWP 4282)] [New Thread 0xb7a82b90 (LWP 4279)] [New Thread 0xb7ac3b90 (LWP 4278)] 0x00110416 in __kernel_vsyscall ()
+ Trace 197404
Thread 1 (Thread 0xb7eed730 (LWP 4275))
This is a downstream packaging issue https://bugzilla.redhat.com/show_bug.cgi?id=441202
*** Bug 516215 has been marked as a duplicate of this bug. ***
Thanks for confirming it was a packaging issue!
*** Bug 533629 has been marked as a duplicate of this bug. ***