Bug#675852: colord: segfault during the boot

2012-11-16 Thread ygmarchi 
Package: colord
Version: 0.1.21-1
Followup-For: Bug #675852

Dear Maintainer,

I think I'm experiencing the same problem

Nov 17 00:34:54 Uranus kernel: [  341.379942] colord-sane[3612]: segfault at 41
ip 7f7b1e6c57d7 sp 7f7b1e69bb78 error 6 in
libdbus-1.so.3.7.2[7f7b1e69d000+44000]

which apparently causes the boot sequence to hang indefinitely. It's not
deterministic, usually the system starts normally.

Regards,
Carlo.



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages colord depends on:
ii  acl2.2.51-8
ii  adduser3.113+nmu3
ii  libc6  2.13-35
ii  libcolord1 0.1.21-1
ii  libglib2.0-0   2.33.12+really2.32.4-3
ii  libgudev-1.0-0 175-7
ii  libgusb2   0.1.3-5
ii  liblcms2-2 2.2+git20110628-2.2
ii  libpolkit-gobject-1-0  0.105-1
ii  libsane1.0.22-7.4
ii  libsqlite3-0   3.7.13-1
ii  libusb-1.0-0   2:1.0.11-1
ii  multiarch-support  2.13-35
ii  policykit-10.105-1

colord recommends no packages.

colord suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#675852: colord: segfault during the boot

2012-11-16 Thread Vincent Lefevre 
On 2012-11-17 00:55:52 +0100, ygmarchi wrote:
 Package: colord
 Version: 0.1.21-1
   
Your version is too old. The bug has been fixed in 0.1.21-2.

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#675852: colord: segfault during the boot

2012-08-22 Thread Kees de Jong 
Package: colord
Version: 0.1.21-1
Followup-For: Bug #675852

I can confirm that this bug is still not resolved.



Kind regards,
Kees



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages colord depends on:
ii  acl2.2.51-8
ii  adduser3.113+nmu3
ii  libc6  2.13-35
ii  libcolord1 0.1.21-1
ii  libglib2.0-0   2.32.3-1
ii  libgudev-1.0-0 175-3.1
ii  libgusb2   0.1.3-5
ii  liblcms2-2 2.2+git20110628-2.2
ii  libpolkit-gobject-1-0  0.105-1
ii  libsane1.0.22-7.3
ii  libsqlite3-0   3.7.13-1
ii  libusb-1.0-0   2:1.0.11-1
ii  multiarch-support  2.13-35
ii  policykit-10.105-1

colord recommends no packages.

colord suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#675852: colord: segfault during the boot

2012-06-13 Thread Paul Menzel 
forwarded 675852 https://bugs.freedesktop.org/show_bug.cgi?id=51031
quit


Am Sonntag, den 10.06.2012, 17:08 -0400 schrieb Douglas F. Calvert:
 Package: colord
 Version: 0.1.21-1
 Followup-For: Bug #675852

Douglas, unfortunately using reportbug is not quite useful for doing
follow ups, since it does not add people to CC being involved in the
report and it messes up threading.

Downloading the last message over the mbox link or getting the whole
mbox with `bts show --mbox 675852` is preferable in my experience. You
then can import it from `~/.devscripts_cache/bts/` to your mail program.

 Here is what i did:
 
 1. I rebuilt the colord packages with debuging symbols

It would be great if a package with debugging symbols could be provided.
James, do you need a separate report for that?

 2. Logged into gnome and killed colord / colord-sane and restarted them under 
 gdb
 3. When I restart gdm3 colord crashes. 

Great that you rebuilt the package and could reproduce the crash I am
also seeing.

 I have attached the gdb log. I ran
 
 bt
 bt full
 thread apply all bt
 thread apply all bt full

I created a new ticket at the freedesktop.org Bugzilla tracked as
#51031.


Thanks,

Paul


[1] https://bugs.freedesktop.org/show_bug.cgi?id=51031


signature.asc
Description: This is a digitally signed message part

Bug#675852: colord: segfault during the boot

2012-06-13 Thread Douglas F. Calvert 
Paul you can subscribe[1] to any individual bugs that you are interested in by 
sending an email to nnn-subscr...@bugs.debian.org. I think its easier that way 
to keep on top of bugs your interested in than to hope that someone CC's you on 
the report. 

[1] http://www.debian.org/Bugs/Developer#subscribe

-Original Message-
From: Paul Menzel pm.deb...@googlemail.com
Date: Wed, 13 Jun 2012 13:39:53 
To: Douglas F. Calvertd...@douglasfcalvert.net; 675...@bugs.debian.org
Cc: Vincent Lefevrevinc...@vinc17.net
Subject: Re: Bug#675852: colord: segfault during the boot

forwarded 675852 https://bugs.freedesktop.org/show_bug.cgi?id=51031
quit


Am Sonntag, den 10.06.2012, 17:08 -0400 schrieb Douglas F. Calvert:
 Package: colord
 Version: 0.1.21-1
 Followup-For: Bug #675852

Douglas, unfortunately using reportbug is not quite useful for doing
follow ups, since it does not add people to CC being involved in the
report and it messes up threading.

Downloading the last message over the mbox link or getting the whole
mbox with `bts show --mbox 675852` is preferable in my experience. You
then can import it from `~/.devscripts_cache/bts/` to your mail program.

 Here is what i did:
 
 1. I rebuilt the colord packages with debuging symbols

It would be great if a package with debugging symbols could be provided.
James, do you need a separate report for that?

 2. Logged into gnome and killed colord / colord-sane and restarted them under 
 gdb
 3. When I restart gdm3 colord crashes. 

Great that you rebuilt the package and could reproduce the crash I am
also seeing.

 I have attached the gdb log. I ran
 
 bt
 bt full
 thread apply all bt
 thread apply all bt full

I created a new ticket at the freedesktop.org Bugzilla tracked as
#51031.


Thanks,

Paul


[1] https://bugs.freedesktop.org/show_bug.cgi?id=51031

Bug#675852: colord: segfault during the boot

2012-06-13 Thread Christopher James Halse Rogers 
On Wed, 2012-06-13 at 13:39 +0200, Paul Menzel wrote:
 ...
  Here is what i did:
  
  1. I rebuilt the colord packages with debuging symbols
 
 It would be great if a package with debugging symbols could be provided.
 James, do you need a separate report for that?

Yeah, I guess I'm resigned to the necessity for a colord-dbg package.
They're a bad workaround for toolchain flaws (and it would be great if
Debian adopted Ubuntu's dbgsym system ☺), but a necessary evil.

The next upload with have a -dbg package.


signature.asc
Description: This is a digitally signed message part

Bug#675852: colord: segfault during the boot

2012-06-13 Thread Paul Menzel 
Am Mittwoch, den 13.06.2012, 13:39 +0200 schrieb Paul Menzel:
 forwarded 675852 https://bugs.freedesktop.org/show_bug.cgi?id=51031
 quit
 
 
 Am Sonntag, den 10.06.2012, 17:08 -0400 schrieb Douglas F. Calvert:
  Package: colord
  Version: 0.1.21-1
  Followup-For: Bug #675852
 
 Douglas, unfortunately using reportbug is not quite useful for doing
 follow ups, since it does not add people to CC being involved in the
 report and it messes up threading.
 
 Downloading the last message over the mbox link or getting the whole
 mbox with `bts show --mbox 675852` is preferable in my experience. You
 then can import it from `~/.devscripts_cache/bts/` to your mail program.
 
  Here is what i did:
  
  1. I rebuilt the colord packages with debuging symbols
 
 It would be great if a package with debugging symbols could be provided.
 James, do you need a separate report for that?
 
  2. Logged into gnome and killed colord / colord-sane and restarted them 
  under gdb
  3. When I restart gdm3 colord crashes. 
 
 Great that you rebuilt the package and could reproduce the crash I am
 also seeing.
 
  I have attached the gdb log. I ran
  
  bt
  bt full
  thread apply all bt
  thread apply all bt full
 
 I created a new ticket at the freedesktop.org Bugzilla tracked as
 #51031.

The author replied to upstream’s report [2]. But running

$ LANG=C sudo /usr/lib/i386-linux-gnu/colord/colord -v

I do not see any critical messages. But it has not crashed either. Can
someone of you reproduce the crash and look for critical warnings?


Thanks,

Paul


 [1] https://bugs.freedesktop.org/show_bug.cgi?id=51031
[2] https://bugs.freedesktop.org/show_bug.cgi?id=51031#c1


signature.asc
Description: This is a digitally signed message part

Bug#675852: Following up on reports (was: Bug#675852: colord: segfault during the boot)

2012-06-13 Thread Paul Menzel 
Am Mittwoch, den 13.06.2012, 11:54 + schrieb Douglas F. Calvert:
 Paul you can subscribe[1] to any individual bugs that you are
 interested in by sending an email to nnn-subscr...@bugs.debian.org. I
 think its easier that way to keep on top of bugs your interested in
 than to hope that someone CC's you on the report.

Douglas, thank you for the reply. My opinion is Debian’s BTS should
automatically subscribe people sending information to a report to that
report. Using subscribe is an option but it is a whole lot more work
since I also have to confirm that subscription and everyone has to do it
in addition to answering to a report. And last time I tried it I did not
get all the messages either for some reason.

And my main problem was the threading and quoting which using

bts show --mbox 675852

would also solve. I hope reportbug and the documentation will be
improved in that regard and I submitted report #677375 [2] for that.

Again thank you for your suggestion and for getting the backtrace.


Thanks,

Paul


 [1] http://www.debian.org/Bugs/Developer#subscribe
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677375


signature.asc
Description: This is a digitally signed message part

Bug#675852: colord: segfault during the boot

2012-06-10 Thread Douglas F. Calvert 
Package: colord
Version: 0.1.21-1
Followup-For: Bug #675852


Hello
Here is what i did:


1. I rebuilt the colord packages with debuging symbols 
2. Logged into gnome and killed colord / colord-sane and restarted them under 
gdb
3. When I restart gdm3 colord crashes. 

I have attached the gdb log. I ran

bt
bt full
thread apply all bt
thread apply all bt full





-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.4-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages colord depends on:
ii  acl2.2.51-7
ii  adduser3.113+nmu3
ii  libc6  2.13-33
ii  libcolord1 0.1.21-1
ii  libglib2.0-0   2.32.3-1
ii  libgudev-1.0-0 175-3.1
ii  libgusb2   0.1.3-4
ii  liblcms2-2 2.2+git20110628-2.2
ii  libpolkit-gobject-1-0  0.105-1
ii  libsane1.0.22-7.1
ii  libsqlite3-0   3.7.12.1-1
ii  libusb-1.0-0   2:1.0.11-1
ii  multiarch-support  2.13-33
ii  policykit-10.105-1

colord recommends no packages.

colord suggests no packages.

-- no debconf information
Starting program: /usr/lib/x86_64-linux-gnu/colord/colord 
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[New Thread 0x74f46700 (LWP 6176)]
[New Thread 0x74745700 (LWP 6177)]
[Thread 0x74f46700 (LWP 6176) exited]
[New Thread 0x74f46700 (LWP 6329)]

Program received signal SIGSEGV, Segmentation fault.
cd_device_register_object (device=0x69b1b0, connection=0x670020, info=0x669650, 
error=0x7fffe328) at cd-device.c:1474
1474g_set_error (error,
#0  cd_device_register_object (device=0x69b1b0, connection=0x670020, 
info=0x669650, error=0x7fffe328) at cd-device.c:1474
#1  0x0041738c in cd_main_device_register_on_bus (device=0x69b1b0, 
error=0x7fffe328) at cd-main.c:399
#2  0x0041869f in cd_main_daemon_method_call (connection_=0x670020, 
sender=0x7fffec004b30 :1.158, object_path=0x7fffec006d10 
/org/freedesktop/ColorManager, interface_name=0x7fffec007820 
org.freedesktop.ColorManager, method_name=0x7fffec006ed0 CreateDevice, 
parameters=0x7fffec016b20, invocation=invocation@entry=0x6a4c60, 
user_data=user_data@entry=0x0) at cd-main.c:1032
#3  0x77027915 in call_in_idle_cb (user_data=0x6a4c60) at 
/tmp/buildd/glib2.0-2.32.3/./gio/gdbusconnection.c:4687
#4  0x76660205 in g_main_dispatch (context=0x636de0) at 
/tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:2539
#5  g_main_context_dispatch (context=context@entry=0x636de0) at 
/tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3075
#6  0x76660538 in g_main_context_iterate (context=0x636de0, 
block=block@entry=1, dispatch=dispatch@entry=1, self=error reading variable: 
Unhandled dwarf expression opcode 0xfa) at 
/tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3146
#7  0x76660932 in g_main_loop_run (loop=0x6368b0) at 
/tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3340
#8  0x0041a25a in main (argc=1, argv=0x7fffe6c8) at cd-main.c:1964
#0  cd_device_register_object (device=0x69b1b0, connection=0x670020, 
info=0x669650, error=0x7fffe328) at cd-device.c:1474
error_local = 0x0
ret = 0
interface_vtable = {method_call = 0x40b1a9 
cd_device_dbus_method_call, get_property = 0x40bde9 
cd_device_dbus_get_property, set_property = 0, padding = {0x0, 0x0, 0x0, 0x0, 
0x0, 0x0, 0x0, 0x0}}
#1  0x0041738c in cd_main_device_register_on_bus (device=0x69b1b0, 
error=0x7fffe328) at cd-main.c:399
ret = 0
#2  0x0041869f in cd_main_daemon_method_call (connection_=0x670020, 
sender=0x7fffec004b30 :1.158, object_path=0x7fffec006d10 
/org/freedesktop/ColorManager, interface_name=0x7fffec007820 
org.freedesktop.ColorManager, method_name=0x7fffec006ed0 CreateDevice, 
parameters=0x7fffec016b20, invocation=invocation@entry=0x6a4c60, 
user_data=user_data@entry=0x0) at cd-main.c:1032
device = 0x69b1b0
scope = CD_OBJECT_SCOPE_TEMP
profile = 0x0
prop_key = 0x6c28c0 Kind
prop_value = 0x6c28c5 display
register_on_bus = 1
ret = 1
device_id = 0x6c2840 xrandr-Lenovo Group Limited
scope_tmp = 0x6c285c temp
error = 0x0
array = 0x0
iter = 0x635140
tuple = 0x0
value = 0x0
fd = -1
uid = 108
fd_handle = 0
metadata_key = 0x0
metadata_value = 0x0
message = 0x10
fd_list = 0x6a4c60
#3  0x77027915 in call_in_idle_cb (user_data=0x6a4c60) at 
/tmp/buildd/glib2.0-2.32.3/./gio/gdbusconnection.c:4687
invocation = 0x6a4c60
vtable = optimized out
registration_id = optimized out
subtree_registration_id = optimized out

Bug#675852: colord: segfault during the boot

2012-06-04 Thread Christopher James Halse Rogers 
Does colord segfault if run explicitly, either by
running /usr/bin/$(dpkg-architecture -qDEB_HOST_MULTIARCH)/colord/colord
or by starting something which bus-activates colord, such as
gnome-color-manager?

There's not much to debug with just the presence of a segfault ;)


signature.asc
Description: This is a digitally signed message part

Bug#675852: colord: segfault during the boot

2012-06-04 Thread Vincent Lefevre 
On 2012-06-04 15:59:31 +1000, Christopher James Halse Rogers wrote:
 Does colord segfault if run explicitly, either by
 running /usr/bin/$(dpkg-architecture -qDEB_HOST_MULTIARCH)/colord/colord
 or by starting something which bus-activates colord, such as
 gnome-color-manager?

It was started automatically at 7:38, and it didn't crash:

Jun  4 07:38:09 xvii dbus[2041]: [system] Activating service 
name='org.freedesktop.ColorManager' (using servicehelper)
Jun  4 07:38:09 xvii dbus[2041]: [system] Successfully activated service 
'org.freedesktop.ColorManager'

and is still running (also with colord-sane, which was started
during the boot):

colord2606 1  0 Jun03 ?00:00:00 
/usr/lib/x86_64-linux-gnu/colord/colord-sane
colord   14565 1  0 07:38 ?00:00:00 
/usr/lib/x86_64-linux-gnu/colord/colord

I don't know why it was started automatically. It could be related to
cron.daily, which was run at 7:35, but I haven't seen any cron script
related to colord.

Note that colord-sane also crashed in a few occasions, but only when
shuting down (segfault at 9 ip 7f6bf755c54c sp 7f6bf7532b78
error 6 in libdbus-1.so.3.7.0), and not always (?); that's bug 668225
(though this bug report doesn't say when).

The colord crash seems always reproducible at boot time:

[...]
Jun  3 15:45:16 xvii dbus[2027]: [system] Activating service 
name='org.freedesktop.ColorManager' (using servicehelper)
Jun  3 15:45:17 xvii dbus[2027]: [system] Activating service 
name='org.freedesktop.UPower' (using servicehelper)
Jun  3 15:45:18 xvii dbus[2027]: [system] Successfully activated service 
'org.freedesktop.UPower'
Jun  3 15:45:18 xvii dbus[2027]: [system] Successfully activated service 
'org.freedesktop.ColorManager'
Jun  3 15:45:18 xvii dbus[2027]: [system] Activating service 
name='org.freedesktop.colord-sane' (using servicehelper)
Jun  3 15:45:19 xvii dbus[2027]: [system] Successfully activated service 
'org.freedesktop.colord-sane'
Jun  3 15:45:21 xvii anacron[2740]: Anacron 2.3 started on 2012-06-03
[... other boot messages ...]
Jun  3 15:45:31 xvii kernel: [   79.418342] colord[2601]: segfault at 8 ip 
0040bc6d sp 7fff9e09b880 error 4 in colord[40+2]
[...]

[...]
Jun  3 19:50:45 xvii dbus[2027]: [system] Activating service 
name='org.freedesktop.ColorManager' (using servicehelper)
Jun  3 19:50:45 xvii dbus[2027]: [system] Successfully activated service 
'org.freedesktop.ColorManager'
Jun  3 19:50:46 xvii kernel: [14794.218978] colord[15567]: segfault at 8 ip 
0040bc6d sp 7fff376633e0 error 4 in colord[40+2]
[...]

[...]
Jun  3 19:53:02 xvii dbus[2032]: [system] Activating service 
name='org.freedesktop.ColorManager' (using servicehelper)
Jun  3 19:53:02 xvii dbus[2032]: [system] Successfully activated service 
'org.freedesktop.ColorManager'
Jun  3 19:53:03 xvii dbus[2032]: [system] Activating service 
name='org.freedesktop.colord-sane' (using servicehelper)
Jun  3 19:53:03 xvii dbus[2032]: [system] Successfully activated service 
'org.freedesktop.colord-sane'
[... other boot messages ...]
Jun  3 19:53:18 xvii kernel: [   79.669036] colord[2593]: segfault at 8 ip 
0040bc6d sp 7fff8e9a4fa0 error 4 in colord[40+2]
[...]

[...]
Jun  3 19:56:02 xvii dbus[2041]: [system] Activating service 
name='org.freedesktop.ColorManager' (using servicehelper)
Jun  3 19:56:03 xvii dbus[2041]: [system] Successfully activated service 
'org.freedesktop.ColorManager'
Jun  3 19:56:03 xvii dbus[2041]: [system] Activating service 
name='org.freedesktop.colord-sane' (using servicehelper)
Jun  3 19:56:04 xvii dbus[2041]: [system] Successfully activated service 
'org.freedesktop.colord-sane'
[... other boot messages ...]
Jun  3 19:56:20 xvii kernel: [   83.404173] colord[2601]: segfault at 8 ip 
0040bc6d sp 7fff2d03ff70 error 4 in colord[40+2]
[...]

-- 
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#675852: colord: segfault during the boot

2012-06-03 Thread Vincent Lefevre 
Package: colord
Version: 0.1.21-1
Severity: normal

dmesg shows:

[   79.418342] colord[2601]: segfault at 8 ip 0040bc6d sp 
7fff9e09b880 error 4 in colord[40+2]

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages colord depends on:
ii  acl2.2.51-7
ii  adduser3.113+nmu3
ii  libc6  2.13-32
ii  libcolord1 0.1.21-1
ii  libglib2.0-0   2.32.3-1
ii  libgudev-1.0-0 175-3.1
ii  libgusb2   0.1.3-4
ii  liblcms2-2 2.2+git20110628-2.2
ii  libpolkit-gobject-1-0  0.105-1
ii  libsane1.0.22-7.1
ii  libsqlite3-0   3.7.12.1-1
ii  libusb-1.0-0   2:1.0.9-1
ii  multiarch-support  2.13-32
ii  policykit-10.105-1

colord recommends no packages.

colord suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org