ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Jan 24 12:47:09 2013
DistroRelease: Ubuntu 12.10
ExecutablePath: /usr/lib/i386-linux-gnu/colord/colord-sane
ExecutableTimestamp: 1349865025
ProcCmdline: /usr/lib/i386-linux-gnu/colord/colord-sane
ProcCwd: /
ProcStatus:
Name:
Ubuntu 13.04 on Microsoft Hyper-V 2008 R2 SP1. Happened after reboot.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1026520
Title:
colord-sane crashed with SIGSEGV in __opendirat()
Has this bug really been fixed? I'm seeing it every time I boot the
final Ubuntu 12.10 x86 ISO image in VirtualBox (selecting Try Ubuntu to
load the Unity desktop). It gives a pretty poor first impression of
Ubuntu. If the 12.10 ISO images are ever rebuilt/updated I hope this
issue can be
** Branch linked: lp:~ubuntu-branches/ubuntu/quantal/colord/quantal-
proposed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1026520
Title:
colord-sane crashed with SIGSEGV in
This bug was fixed in the package colord - 0.1.21-1ubuntu2
---
colord (0.1.21-1ubuntu2) quantal-proposed; urgency=low
* debian/patches/one_shot_colord-sane.patch:
- Rework colord-sane to be spawned each time a sane scan is required.
Works around fd leaks in libsane and
Report after update 12.04.1 to 12.10 beta 2.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1026520
Title:
colord-sane crashed with SIGSEGV in __opendirat()
Status in “colord”
Still present in 12.10...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1026520
Title:
colord-sane crashed with SIGSEGV in __opendirat()
Status in “colord” package in Ubuntu:
I hate to burst bubbles here, but I received a crash on this issue
today, and I am running colord 0.1.21-1ubuntu1 since 13 sept :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
[Laughters]
I too have suffered from first colord annoyance today.
Actually, apport does not bring me on this page, but on:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1027139
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Not to report any problem, but just to note that, having installed the
12/09/13 quantal build about 10 hours ago, I have yet to witness a
colord crash, which was so frequent when I had one of the alpha builds
installed.
If this is the case, that this has been fixed, then long live magic.
--
You
** Changed in: colord (Ubuntu Quantal)
Importance: High = Medium
** Changed in: colord (Ubuntu Quantal)
Milestone: None = ubuntu-12.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to colord in Ubuntu.
status incomplete
Because the stacktrace on this is quite weird, I'm going to be
super-optimistic and hope that fixing the thread-unsafe usage of DBus in
colord-sane has magically fixed this.
Please pipe up if you see this crash with colord 0.1.21-1ubuntu1.
** Changed in: colord (Ubuntu)
12 matches
Mail list logo
