would hope you would be more cautious and careful when considering
reports that you're making people's systems unbootable. Erring on the
side of caution and all that on such an important package.
On Wed, Sep 18, 2013 at 10:08 AM, Michael Biebl wrote:
> Am 18.09.2013 19:01, sc
This update made my system unbootable due to no devices being created
by udev. However, I believe your fix won't work on my system.
chant@zbz:~$ zcat /proc/config.gz | grep DEVTMP
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
this configuration was enough to cause the problem.
--
To UN
; more ideas what to try :/
>
> Re cairo: I have libcairo2 installed (but set on hold).
>
> Soeren
>
> On Sun, 2012-07-01 at 14:38 -0700, Andrew Chant wrote:
> > Doesn't happen for me. Out of curiosity, how did you manage to
> > install chromium without libcairo2
Doesn't happen for me. Out of curiosity, how did you manage to install
chromium without libcairo2?
On Sun, Jul 1, 2012 at 2:30 PM, Soeren Sonnenburg wrote:
> Package: chromium
> Version: 20.0.1132.43~r143823-1
> Severity: grave
>
> On various webpages like e.g. https://github.com chromium repro
Which patch are you using? I had the problem occur with very regular
frequently without the patch that I posted, and it disappeared
completely with the patch. I'm pretty certain that solved the omnibox problem.
On Tue, Jun 12, 2012 at 3:47 PM, Onur Aslan wrote:
> I compiled chromium with this p
Patch directly applied from http://codereview.chromium.org/10387026/ Patch Set
2.
Upstream patch author: Evangelos Foutras
Remove this patch when upstream is fixed.
The use of g++ 4.7 by Debian seems to make the crashes more frequent
than on upstream's pre-4.6 gcc.
---
debian/patches/series
From: Andrew Chant
Subject: [PATCH] Fix Chromium's third_party/sqlite deferencing a NULL ptr
In-Reply-To:
This is an updated patch on top of pkg-chromium master that undoes the
previous patch as well.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subje
This patch also adds more attribution. I tested this patch over the
last day and no more annoying crashes, at least not on amd64.
Please apply a revert of the original and use this one.
-Andrew
On Mon, Jun 11, 2012 at 5:09 PM, Andrew Chant wrote:
> Patch directly applied f
- Forwarded message --
> From: Giuseppe Iuculano
> To: 674726-d...@bugs.debian.org
> Cc:
> Date: Fri, 01 Jun 2012 18:20:21 +0200
> Subject: fixed in 20.0.1132.21~r139451-1
> Source: chromium-browser
> Source-Version: 20.0.1132.21~r139451-1
>
>
>
>
>
> --
Note: the recent gyp-0.1~svn1395-1 breaks the build even more.
NameError: name 'LINKER_SUPPORTS_ICF' is not defined while evaluating
condition 'LINKER_SUPPORTS_ICF==1 and release_valgrind_build==0' in
build/all.gyp while trying to load build/all.gyp
On Sat, May 26, 2012 at 7
Package: chromium
Version: 18.0.1025.168~r134367-1
Severity: serious
Justification: FTBFS
Dear Maintainer,
Can't build chromium from source after patching w/ fix from bug #671994.
I get:
webkit/glue/webcursor_gtk.cc: In member function ‘GdkCursor*
WebCursor::GetCustomCursor()’:
webkit/gl
I understand what you mean now - the fix is to update
audacious-plugins to 1.5.1 to match audacious.
This should be fixed in the "depends" field of the audacious package.
Note that in 'testing', audacious-plugins 1.5.1 isn't available while
audacious-1.5.1 is the only one available, and the two don
clearly the bug cannot be fixed in 1.5.1-1, as that is the version
that we reported it in.
-Andrew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The segfault goes away if I remove ~/.config/audacious/playlist.xspf.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I also get audacious segfaulting at startup, which began only with the
update to 1.5.1.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
15 matches
Mail list logo
