Bug#722850: Bug#722580: 722580 reopen
Reopening this bug report is correct. I won't play re-open tag with you, though I hope you will consider re-opening the bug. Just checking for devtmpfs in /proc/filesystems is not enough. The update caused my system to stop booting, which no update should ever do. You are correct that I have no initramfs. I did have an up-to-date /etc/init.d/udev. On Wed, Sep 18, 2013 at 1:34 AM, Michael Biebl bi...@debian.org wrote: Version: 204-4 Am 18.09.2013 07:49, schrieb Andrew Chant: 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. That doesn't make sense. The reference you quoted is aborting the upgrade if DEVTMPFS is missing, which isn't in your case. So re-opening this particular bug report is wrong. I assume you have no initramfs and and outdated /etc/init.d/udev. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722850: Bug#722580: 722580 reopen
As-mentioned, using the kernel from which I ran this: chant@zbz:~$ zcat /proc/config.gz | grep DEVTMP CONFIG_DEVTMPFS=y # CONFIG_DEVTMPFS_MOUNT is not set I got a system which didn't load any modules and which failed to boot, same symptoms as the initial bug. I 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 bi...@debian.org wrote: Am 18.09.2013 19:01, schrieb Andrew Chant: Reopening this bug report is correct. I won't play re-open tag with you, though I hope you will consider re-opening the bug. Just checking for devtmpfs in /proc/filesystems is not enough. The Why not? update caused my system to stop booting, which no update should ever do. You are correct that I have no initramfs. I did have an up-to-date /etc/init.d/udev. If you can show that there is an actual bug, sure then we can re-open the bug report, but not without more information. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722850: Bug#722580: 722580 reopen
Woops, CC'd the wrong bug. sorry for the noise. On Wed, Sep 18, 2013 at 11:17 AM, Andrew Chant andrew.chant+deb...@gmail.com wrote: As-mentioned, using the kernel from which I ran this: chant@zbz:~$ zcat /proc/config.gz | grep DEVTMP CONFIG_DEVTMPFS=y # CONFIG_DEVTMPFS_MOUNT is not set I got a system which didn't load any modules and which failed to boot, same symptoms as the initial bug. I 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 bi...@debian.org wrote: Am 18.09.2013 19:01, schrieb Andrew Chant: Reopening this bug report is correct. I won't play re-open tag with you, though I hope you will consider re-opening the bug. Just checking for devtmpfs in /proc/filesystems is not enough. The Why not? update caused my system to stop booting, which no update should ever do. You are correct that I have no initramfs. I did have an up-to-date /etc/init.d/udev. If you can show that there is an actual bug, sure then we can re-open the bug report, but not without more information. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722580: 722580 reopen
+722580 -722850, woops. As-mentioned, I am using the kernel from which I ran this: chant@zbz:~$ zcat /proc/config.gz | grep DEVTMP CONFIG_DEVTMPFS=y # CONFIG_DEVTMPFS_MOUNT is not set I got a system which didn't load any modules and which failed to boot, same symptoms as the initial bug. I 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 bi...@debian.org wrote: Am 18.09.2013 19:01, schrieb Andrew Chant: Reopening this bug report is correct. I won't play re-open tag with you, though I hope you will consider re-opening the bug. Just checking for devtmpfs in /proc/filesystems is not enough. The Why not? update caused my system to stop booting, which no update should ever do. You are correct that I have no initramfs. I did have an up-to-date /etc/init.d/udev. If you can show that there is an actual bug, sure then we can re-open the bug report, but not without more information. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722580: 722580 reopen
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 UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679827: chromium always hangs on https://github.com
Which version of libcairo2 are you held at? Could you try the latest version (1.12.2-2) and see if you can still reproduce the issue? On Mon, Jul 2, 2012 at 3:13 AM, Soeren Sonnenburg so...@debian.org wrote: I now created a fresh new user to test this - same thing. 100% reliably hangs on github and various other pages. Tried to disable all kinds of gpu and related hardware accel in about:flags - no change: still crashes. I asked other people and for them everything was fine (intel gfx) so it might very well be this nvidia card / driver combo here. Now I have no 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? On Sun, Jul 1, 2012 at 2:30 PM, Soeren Sonnenburg so...@debian.org wrote: Package: chromium Version: 20.0.1132.43~r143823-1 Severity: grave On various webpages like e.g. https://github.com chromium reproducibly hangs since this upgrade to 20.X (same with google-chrome even from dev channel 21.X). This occurs with all plugins and extensions disabled and even in incognito mode and even after removing .cache .config -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.5.0-rc3-sonne+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 20.0.1132.43~r143823-1 ii gconf-service 3.2.5-1 ii libasound2 1.0.25-3 ii libatk1.0-0 2.4.0-2 ii libbz2-1.0 1.0.6-3 ii libc6 2.13-34 pn libcairo2 none ii libcups21.5.3-2 ii libdbus-1-3 1.6.2-1 ii libevent-2.0-5 2.0.19-stable-3 ii libexpat1 2.1.0-1 ii libflac81.2.1-6 ii libfontconfig1 2.9.0-6 ii libfreetype62.4.9-1 ii libgcc1 1:4.7.1-2 ii libgconf-2-43.2.5-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgnome-keyring0 3.4.1-1 ii libgtk2.0-0 2.24.10-1 ii libjpeg88d-1 ii libnspr42:4.9.1-1 ii libnss3 2:3.13.5-1 ii libnss3-1d 2:3.13.5-1 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-3 ii libspeex1 1.2~rc1-6 ii libstdc++6 4.7.1-2 ii libudev0175-3.1 ii libwebp20.1.3-3 ii libx11-62:1.5.0-1 ii libxcomposite1 1:0.4.3-2 ii libxext62:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxml2 2.8.0+dfsg1-4 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-12+rebuild1 ii libxss1 1:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zlib1g 1:1.2.7.dfsg-13 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n none -- no debconf information -- For the one fact about the future of which we can be certain is that it will be utterly fantastic. -- Arthur C. Clarke, 1962
Bug#679827: chromium always hangs on https://github.com
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 so...@debian.org wrote: Package: chromium Version: 20.0.1132.43~r143823-1 Severity: grave On various webpages like e.g. https://github.com chromium reproducibly hangs since this upgrade to 20.X (same with google-chrome even from dev channel 21.X). This occurs with all plugins and extensions disabled and even in incognito mode and even after removing .cache .config -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.5.0-rc3-sonne+ (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 20.0.1132.43~r143823-1 ii gconf-service 3.2.5-1 ii libasound2 1.0.25-3 ii libatk1.0-0 2.4.0-2 ii libbz2-1.0 1.0.6-3 ii libc6 2.13-34 pn libcairo2 none ii libcups21.5.3-2 ii libdbus-1-3 1.6.2-1 ii libevent-2.0-5 2.0.19-stable-3 ii libexpat1 2.1.0-1 ii libflac81.2.1-6 ii libfontconfig1 2.9.0-6 ii libfreetype62.4.9-1 ii libgcc1 1:4.7.1-2 ii libgconf-2-43.2.5-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgnome-keyring0 3.4.1-1 ii libgtk2.0-0 2.24.10-1 ii libjpeg88d-1 ii libnspr42:4.9.1-1 ii libnss3 2:3.13.5-1 ii libnss3-1d 2:3.13.5-1 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-3 ii libspeex1 1.2~rc1-6 ii libstdc++6 4.7.1-2 ii libudev0175-3.1 ii libwebp20.1.3-3 ii libx11-62:1.5.0-1 ii libxcomposite1 1:0.4.3-2 ii libxext62:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxml2 2.8.0+dfsg1-4 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-12+rebuild1 ii libxss1 1:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zlib1g 1:1.2.7.dfsg-13 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n none -- no debconf information
Bug#676636: Patch doesn't work
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 o...@onur.im wrote: I compiled chromium with this patch, but unfortunately I am still getting crashes when I try to search something. It's not frequently but it is still making chromium unusable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676636: [PATCH] Fix Chromium's third_party/sqlite deferencing an out-of-scope pointer.
The other patch failed and this one works because the other patch
fixes sources that are used to generate the sqlite.c file which is
elsewhere in the source tree. The debian source build process doesn't
regenerate src/third_party/sqlite/amalgamation/sqlite3.c/h so the
patch had no effect.
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 ach...@google.com wrote:
Patch directly applied from http://codereview.chromium.org/10387026/ Patch
Set 2.
Upstream patch author: Evangelos Foutras evange...@foutrelis.com
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 | 1 +
...thirdparty-sqlite-invalid-stack-reference.patch | 119
2 files changed, 120 insertions(+)
create mode 100644
debian/patches/thirdparty-sqlite-invalid-stack-reference.patch
diff --git a/debian/patches/series b/debian/patches/series
index 2d4bcc8..064a03d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -22,3 +22,4 @@ arm-no-float-abi.patch
vpx.patch
pulseaudio.patch
gcc4.7.patch
+thirdparty-sqlite-invalid-stack-reference.patch
diff --git a/debian/patches/thirdparty-sqlite-invalid-stack-reference.patch
b/debian/patches/thirdparty-sqlite-invalid-stack-reference.patch
new file mode 100644
index 000..ffabfaf
--- /dev/null
+++ b/debian/patches/thirdparty-sqlite-invalid-stack-reference.patch
@@ -0,0 +1,119 @@
+Fix Chromium's third_party/sqlite deferencing an out-of-scope pointer.
+
+Patch applied from http://codereview.chromium.org/10387026/ Patch Set 2.
+Index: chromium-browser-20.0.1132.21~r139451/src/AUTHORS
+===
+--- chromium-browser-20.0.1132.21~r139451.orig/src/AUTHORS 2012-06-10
20:55:50.534940299 -0700
chromium-browser-20.0.1132.21~r139451/src/AUTHORS 2012-06-10
20:55:54.721607126 -0700
+@@ -177,3 +177,4 @@
+ Alexandre Abreu wiss1...@gmail.com
+ Erik Sjölund erik.sjol...@gmail.com
+ Simon Arlott simon.arl...@gmail.com
++Evangelos Foutras evange...@foutrelis.com
+Index:
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/README.chromium
+===
+---
chromium-browser-20.0.1132.21~r139451.orig/src/third_party/sqlite/README.chromium
2012-06-10 20:55:50.534940299 -0700
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/README.chromium
2012-06-10 20:55:54.721607126 -0700
+@@ -70,6 +70,7 @@
+ test.patch
+ mac_time_machine.patch
+ system-sqlite.patch
++sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch
+
+ So, e.g. you could do this to apply all our patches to vanilla SQLite:
+
+@@ -84,6 +85,7 @@
+ patch -p0 ../sqlite/test.patch
+ patch -p0 ../sqlite/mac_time_machine.patch
+ patch -p0 ../sqlite/system-sqlite.patch
++patch -p0 ../sqlite/sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch
+
+ This will only be the case if all changes we make also update the
corresponding
+ patch files. Therefore please remember to do that whenever you make a
change!
+Index:
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/amalgamation/sqlite3.c
+===
+---
chromium-browser-20.0.1132.21~r139451.orig/src/third_party/sqlite/amalgamation/sqlite3.c
2012-06-10 20:55:50.534940299 -0700
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/amalgamation/sqlite3.c
2012-06-10 20:55:54.734940460 -0700
+@@ -119149,13 +119149,13 @@
+ Fts3SegReader **ppReader /* OUT: SegReader for pending-terms */
+ ){
+ Fts3SegReader *pReader = 0; /* Fts3SegReader object to return */
++ Fts3HashElem *pE; /* Iterator variable */
+ Fts3HashElem **aElem = 0; /* Array of term hash entries to scan */
+ int nElem = 0; /* Size of array at aElem */
+ int rc = SQLITE_OK; /* Return Code */
+
+ if( isPrefix ){
+ int nAlloc = 0; /* Size of allocated array at aElem */
+- Fts3HashElem *pE = 0; /* Iterator variable */
+
+ for(pE=fts3HashFirst(p-pendingTerms); pE; pE=fts3HashNext(pE)){
+ char *zKey = (char *)fts3HashKey(pE);
+@@ -119187,7 +119187,7 @@
+ }
+
+ }else{
+- Fts3HashElem *pE = fts3HashFindElem(p-pendingTerms, zTerm, nTerm);
++ pE = fts3HashFindElem(p-pendingTerms, zTerm, nTerm);
+ if( pE ){
+ aElem = pE;
+ nElem = 1;
+Index:
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/src/ext/fts3/fts3_write.c
Bug#676636: [PATCH] Fix Chromium's third_party/sqlite deferencing an out-of-scope pointer.
Patch directly applied from http://codereview.chromium.org/10387026/ Patch Set
2.
Upstream patch author: Evangelos Foutras evange...@foutrelis.com
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 |2 +-
debian/patches/sqlite.patch| 28 -
...thirdparty-sqlite-invalid-stack-reference.patch | 119
3 files changed, 120 insertions(+), 29 deletions(-)
delete mode 100644 debian/patches/sqlite.patch
create mode 100644
debian/patches/thirdparty-sqlite-invalid-stack-reference.patch
diff --git a/debian/patches/series b/debian/patches/series
index 311b071..064a03d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -22,4 +22,4 @@ arm-no-float-abi.patch
vpx.patch
pulseaudio.patch
gcc4.7.patch
-sqlite.patch
+thirdparty-sqlite-invalid-stack-reference.patch
diff --git a/debian/patches/sqlite.patch b/debian/patches/sqlite.patch
deleted file mode 100644
index 95abf36..000
--- a/debian/patches/sqlite.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-Index: sid/src/third_party/sqlite/src/ext/fts3/fts3_write.c
-===
sid.orig/src/third_party/sqlite/src/ext/fts3/fts3_write.c 2012-05-19
16:54:33.0 +0200
-+++ sid/src/third_party/sqlite/src/ext/fts3/fts3_write.c 2012-06-11
16:16:11.607585285 +0200
-@@ -1238,13 +1238,13 @@
- Fts3SegReader **ppReader/* OUT: SegReader for pending-terms */
- ){
- Fts3SegReader *pReader = 0; /* Fts3SegReader object to return */
-+ Fts3HashElem *pE; /* Iterator variable */
- Fts3HashElem **aElem = 0; /* Array of term hash entries to scan */
- int nElem = 0; /* Size of array at aElem */
- int rc = SQLITE_OK; /* Return Code */
-
- if( isPrefix ){
- int nAlloc = 0; /* Size of allocated array at aElem */
--Fts3HashElem *pE = 0; /* Iterator variable */
-
- for(pE=fts3HashFirst(p-pendingTerms); pE; pE=fts3HashNext(pE)){
- char *zKey = (char *)fts3HashKey(pE);
-@@ -1276,7 +1276,7 @@
- }
-
- }else{
--Fts3HashElem *pE = fts3HashFindElem(p-pendingTerms, zTerm, nTerm);
-+pE = fts3HashFindElem(p-pendingTerms, zTerm, nTerm);
- if( pE ){
- aElem = pE;
- nElem = 1;
diff --git a/debian/patches/thirdparty-sqlite-invalid-stack-reference.patch
b/debian/patches/thirdparty-sqlite-invalid-stack-reference.patch
new file mode 100644
index 000..ffabfaf
--- /dev/null
+++ b/debian/patches/thirdparty-sqlite-invalid-stack-reference.patch
@@ -0,0 +1,119 @@
+Fix Chromium's third_party/sqlite deferencing an out-of-scope pointer.
+
+Patch applied from http://codereview.chromium.org/10387026/ Patch Set 2.
+Index: chromium-browser-20.0.1132.21~r139451/src/AUTHORS
+===
+--- chromium-browser-20.0.1132.21~r139451.orig/src/AUTHORS 2012-06-10
20:55:50.534940299 -0700
chromium-browser-20.0.1132.21~r139451/src/AUTHORS 2012-06-10
20:55:54.721607126 -0700
+@@ -177,3 +177,4 @@
+ Alexandre Abreu wiss1...@gmail.com
+ Erik Sjölund erik.sjol...@gmail.com
+ Simon Arlott simon.arl...@gmail.com
++Evangelos Foutras evange...@foutrelis.com
+Index:
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/README.chromium
+===
+---
chromium-browser-20.0.1132.21~r139451.orig/src/third_party/sqlite/README.chromium
2012-06-10 20:55:50.534940299 -0700
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/README.chromium
2012-06-10 20:55:54.721607126 -0700
+@@ -70,6 +70,7 @@
+ test.patch
+ mac_time_machine.patch
+ system-sqlite.patch
++sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch
+
+ So, e.g. you could do this to apply all our patches to vanilla SQLite:
+
+@@ -84,6 +85,7 @@
+ patch -p0 ../sqlite/test.patch
+ patch -p0 ../sqlite/mac_time_machine.patch
+ patch -p0 ../sqlite/system-sqlite.patch
++patch -p0 ../sqlite/sqlite-3.7.6.3-fix-out-of-scope-memory-reference.patch
+
+ This will only be the case if all changes we make also update the
corresponding
+ patch files. Therefore please remember to do that whenever you make a change!
+Index:
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/amalgamation/sqlite3.c
+===
+---
chromium-browser-20.0.1132.21~r139451.orig/src/third_party/sqlite/amalgamation/sqlite3.c
2012-06-10 20:55:50.534940299 -0700
chromium-browser-20.0.1132.21~r139451/src/third_party/sqlite/amalgamation/sqlite3.c
2012-06-10 20:55:54.734940460 -0700
+@@ -119149,13 +119149,13 @@
+ Fts3SegReader **ppReader/* OUT: SegReader for pending-terms */
+ ){
+ Fts3SegReader *pReader = 0; /* Fts3SegReader object to return */
++
Bug#676636:
From: Andrew Chant ach...@google.com 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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674726: closed by Giuseppe Iuculano giuse...@iuculano.it (fixed in 20.0.1132.21~r139451-1)
confirmed fixed. 20.0.1132.21~r139451-1 builds fine on my box. On Fri, Jun 1, 2012 at 9:48 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the chromium package: #674726: FTBFS: webcursor_gtk.cc:185 ‘gdk_pixbuf_unref’ is deprecated, Use 'g_object_unref' instead It has been closed by Giuseppe Iuculano giuse...@iuculano.it. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Giuseppe Iuculano giuse...@iuculano.it by replying to this email. -- 674726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Forwarded message -- From: Giuseppe Iuculano giuse...@iuculano.it 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 -- Forwarded message -- From: Andrew Chant andrew.chant+deb...@gmail.com To: Debian Bug Tracking System sub...@bugs.debian.org Cc: Date: Sat, 26 May 2012 19:21:20 -0700 Subject: FTBFS: webcursor_gtk.cc:185 ‘gdk_pixbuf_unref’ is deprecated, Use 'g_object_unref' instead 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/glue/webcursor_gtk.cc:185:3: error: ‘void gdk_pixbuf_unref(GdkPixbuf*)’ is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use 'g_object_unref' instead [-Werror=deprecated-declarations] webkit/glue/webcursor_gtk.cc:185:26: error: ‘void gdk_pixbuf_unref(GdkPixbuf*)’ is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use 'g_object_unref' instead [-Werror=deprecated-declarations] My libgdk-pixbuf2.0-dev is at version 2.26.1-1 Version: 2.26.1-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0intel1 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 18.0.1025.168~r134367-1 ii gconf-service 3.2.5-1 ii libasound2 1.0.25-3 ii libavcodec53 6:0.8.2-2 ii libavformat53 6:0.8.2-2 ii libavutil51 6:0.8.2-2 ii libbz2-1.0 1.0.6-1 ii libc6 2.13-32 ii libcairo2 1.12.2-2 ii libcups2 1.5.3-1 ii libdbus-1-3 1.5.12-1 ii libevent-2.0-5 2.0.19-stable-2 ii libexpat1 2.1.0-1 ii libflac8 1.2.1-6 ii libfontconfig1 2.9.0-5 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.0-9 ii libgconf-2-4 3.2.5-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libjpeg8 8d-1 ii libnspr4-0d 2:4.9-3 ii libnss3-1d 2:3.13.4-3 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-3 ii libspeex1 1.2~rc1-5 ii libstdc++6 4.7.0-9 ii libudev0 175-3.1 ii libwebp2 0.1.3-3 ii libx11-6 2:1.4.99.901-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxml2 2.7.8.dfsg-9.1 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-11 ii libxss1 1:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zlib1g 1:1.2.7.dfsg-11 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n none -- 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#674726: FTBFS: webcursor_gtk.cc:185 ‘gdk_pixbuf_unref’ is deprecated, Use 'g_object_unref' instead
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:21 PM, Andrew Chant andrew.chant+deb...@gmail.com wrote: 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/glue/webcursor_gtk.cc:185:3: error: ‘void gdk_pixbuf_unref(GdkPixbuf*)’ is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use 'g_object_unref' instead [-Werror=deprecated-declarations] webkit/glue/webcursor_gtk.cc:185:26: error: ‘void gdk_pixbuf_unref(GdkPixbuf*)’ is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use 'g_object_unref' instead [-Werror=deprecated-declarations] My libgdk-pixbuf2.0-dev is at version 2.26.1-1 Version: 2.26.1-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0intel1 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 18.0.1025.168~r134367-1 ii gconf-service 3.2.5-1 ii libasound2 1.0.25-3 ii libavcodec53 6:0.8.2-2 ii libavformat53 6:0.8.2-2 ii libavutil51 6:0.8.2-2 ii libbz2-1.0 1.0.6-1 ii libc6 2.13-32 ii libcairo2 1.12.2-2 ii libcups2 1.5.3-1 ii libdbus-1-3 1.5.12-1 ii libevent-2.0-5 2.0.19-stable-2 ii libexpat1 2.1.0-1 ii libflac8 1.2.1-6 ii libfontconfig1 2.9.0-5 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.0-9 ii libgconf-2-4 3.2.5-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libjpeg8 8d-1 ii libnspr4-0d 2:4.9-3 ii libnss3-1d 2:3.13.4-3 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-3 ii libspeex1 1.2~rc1-5 ii libstdc++6 4.7.0-9 ii libudev0 175-3.1 ii libwebp2 0.1.3-3 ii libx11-6 2:1.4.99.901-2 ii libxext6 2:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxml2 2.7.8.dfsg-9.1 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-11 ii libxss1 1:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zlib1g 1:1.2.7.dfsg-11 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n none -- 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#674726: FTBFS: webcursor_gtk.cc:185 ‘gdk_pixbuf_unref’ is deprecated, Use 'g_object_unref' instead
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/glue/webcursor_gtk.cc:185:3: error: ‘void gdk_pixbuf_unref(GdkPixbuf*)’ is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use 'g_object_unref' instead [-Werror=deprecated-declarations] webkit/glue/webcursor_gtk.cc:185:26: error: ‘void gdk_pixbuf_unref(GdkPixbuf*)’ is deprecated (declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:243): Use 'g_object_unref' instead [-Werror=deprecated-declarations] My libgdk-pixbuf2.0-dev is at version 2.26.1-1 Version: 2.26.1-1 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0intel1 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium depends on: ii chromium-inspector 18.0.1025.168~r134367-1 ii gconf-service 3.2.5-1 ii libasound2 1.0.25-3 ii libavcodec536:0.8.2-2 ii libavformat53 6:0.8.2-2 ii libavutil51 6:0.8.2-2 ii libbz2-1.0 1.0.6-1 ii libc6 2.13-32 ii libcairo2 1.12.2-2 ii libcups21.5.3-1 ii libdbus-1-3 1.5.12-1 ii libevent-2.0-5 2.0.19-stable-2 ii libexpat1 2.1.0-1 ii libflac81.2.1-6 ii libfontconfig1 2.9.0-5 ii libfreetype62.4.9-1 ii libgcc1 1:4.7.0-9 ii libgconf-2-43.2.5-1 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libjpeg88d-1 ii libnspr4-0d 2:4.9-3 ii libnss3-1d 2:3.13.4-3 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii libpulse0 2.0-3 ii libspeex1 1.2~rc1-5 ii libstdc++6 4.7.0-9 ii libudev0175-3.1 ii libwebp20.1.3-3 ii libx11-62:1.4.99.901-2 ii libxext62:1.3.1-2 ii libxfixes3 1:5.0-4 ii libxml2 2.7.8.dfsg-9.1 ii libxrender1 1:0.9.7-1 ii libxslt1.1 1.1.26-11 ii libxss1 1:1.2.2-1 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zlib1g 1:1.2.7.dfsg-11 chromium recommends no packages. Versions of packages chromium suggests: pn chromium-l10n none -- 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#665440: Info received (chromium-browser: No audio will play again if an audio file plays to completion)
This bug has been resolved in 18.0.1025.168~r134367-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665440: chromium-browser: No audio will play again if an audio file plays to completion
Package: chromium-browser Version: 17.0.963.78~r125577-1 Severity: normal Dear Maintainer, After letting an audio file (both .mp3 and .wav tested) play to completion, chromium will no longer play any audio, and no progress will be shown on the song progress bar. Example: navigate to http://www.mediacollege.com/audio/tone/files/250Hz_44100Hz_16bit_05sec.wav let the tone play to the end of 5 seconds, then click play to get it to play again. Nothing will happen. There is identical behaviour with mp3s. This is *not* repeatable on the Chromium project continuous builds. I tried the continous build at revision 125587 (closest avail to 125577) at http://commondatastorage.googleapis.com/chromium-browser-continuous/index.html?path=Linux_x64/125587/ and it worked fine. (Note: the continous build won't play .mp3s, just wavs). Note that I have alsa installed and not pulseaudio. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages chromium-browser depends on: ii chromium 17.0.963.78~r125577-1 chromium-browser recommends no packages. chromium-browser 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#563891: openbox: signal 11 while exploring menus
Starting program: /usr/bin/openbox Program received signal SIGSEGV, Segmentation fault. 0x00431eb7 in menu_entry_frame_show_submenu () (gdb) bt #0 0x00431eb7 in menu_entry_frame_show_submenu () #1 0x004321e9 in ?? () #2 0x0042f7b5 in ob_main_loop_run () #3 0x004369c3 in main () (gdb) quit On Wed, Jan 6, 2010 at 9:51 AM, Nico Golde n...@debian.org wrote: Hi, * Andrew Chant andrew.chant+deb...@gmail.com [2010-01-06 14:22]: Since upgrading from 3.4.8-1 to 3.4.9-2_amd64.deb I get segfaults if I explore teh openbox menus for ~30seconds - 1 minute. This appears in .xsession-errors: How are you gentlemen? All your base are belong to us. (Openbox received signal 11) Reproduces easily, but takes a non-deterministic number of menu explorations. Can you provide a backtrace please? Cheers Nico -- Nico Golde - http://www.ngolde.de - n...@jabber.ccc.de - GPG: 0xA0A0 For security reasons, all text in this mail is double-rot13 encrypted. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563891: openbox: signal 11 while exploring menus
Package: openbox Version: 3.4.9-2 Severity: important Since upgrading from 3.4.8-1 to 3.4.9-2_amd64.deb I get segfaults if I explore teh openbox menus for ~30seconds - 1 minute. This appears in .xsession-errors: How are you gentlemen? All your base are belong to us. (Openbox received signal 11) Reproduces easily, but takes a non-deterministic number of menu explorations. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-rc2 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openbox depends on: ii libc6 2.10.2-3 Embedded GNU C Library: Shared lib ii libglib2.0-02.22.3-2 The GLib library of C routines ii libice6 2:1.0.6-1X11 Inter-Client Exchange library ii libobparser21 3.4.9-2 parsing library for openbox ii libobrender21 3.4.9-2 rendering library for openbox them ii libsm6 2:1.1.1-1X11 Session Management library ii libstartup-notification00.10-1 library for program launch feedbac ii libx11-62:1.3.2-1X11 client-side library ii libxau6 1:1.0.5-1X11 authorisation library ii libxext62:1.0.4-1X11 miscellaneous extension librar ii libxinerama12:1.0.3-2X11 Xinerama extension library ii libxml2 2.7.6.dfsg-1 GNOME XML library ii libxrandr2 2:1.3.0-2X11 RandR extension library ii libxrender1 1:0.9.5-1X Rendering Extension client libra Versions of packages openbox recommends: ii openbox-themes1.0.2 Themes for the Openbox window mana Versions of packages openbox suggests: pn libxml2-dev none (no description available) ii menu 2.1.42 generates programs menu for all me pn obconfnone (no description available) ii python2.5.4-5An interactive high-level object-o pn ttf-dejavunone (no description available) -- 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#539526: alsa-utils: missing dependency on package that provides smixer-python.so
Package: alsa-utils Version: 1.0.20-2 Severity: normal When running alsamixer -a basic, I get the following message: ch...@chanxbox:/data/src/snd_mixer$ alsamixer -a basic ALSA lib simple_abst.c:131:(try_open_full) Unable to open library '/usr/lib/alsa-lib/smixer/smixer-python.so' alsamixer: function snd_mixer_selem_register failed: No such device or address I imagine this is as a result of an unfilled dependency of alsa-utils. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages alsa-utils depends on: ii libasound21.0.20-3 shared library for ALSA applicatio ii libc6 2.9-23 GNU C Library: Shared libraries ii libncurses5 5.7+20090613-1 shared libraries for terminal hand ii linux-sound-base 1.0.20+dfsg-1 base package for ALSA and OSS soun ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip ii module-init-tools 3.9-2 tools for managing Linux kernel mo ii whiptail 0.52.10-4 Displays user-friendly dialog boxe Versions of packages alsa-utils recommends: ii alsa-base 1.0.20+dfsg-1 ALSA driver configuration files ii pciutils 1:3.1.3-1 Linux PCI Utilities alsa-utils 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#488978: mistake
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]
Bug#488978: fix
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't play nicely together. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#488978: Another confirmation
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]
Bug#488978: Update
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]
Bug#433677: xserver-xorg-video-ati: Massive performance reduction from etch to lenny on radeon 9250
Package: xserver-xorg-video-ati Version: 1:6.6.3-2 Severity: important Under Etch, iceweasel is fast on X server with EXA. After upgrade to Lenny, running iceweasel makes the X display unresponsive (1-2 second lag ). I'm often unable to drag windows around the screen as the window just ignores the input. CPU usage by Xorg maxes out. I know this is a problem with the X server not iceweasel because I ran etch under chroot and etch's iceweasel had the same laggy/CPU-hogging response. Radeon 9250, 1920x1200x24bpp xorg.conf attached. -Andrew -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xserver-xorg-video-ati depends on: ii libc6 2.6-2GNU C Library: Shared libraries ii xserver-xorg-core 2:1.3.0.0.dfsg-6 X.Org X server -- core server xserver-xorg-video-ati recommends no packages. -- no debconf information # xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true EndSection Section Device Identifier Generic Video Card Driver ati Option AccelMethod EXA EndSection Section Monitor Identifier Generic Monitor Option DPMS HorizSync 28-96 VertRefresh 43-60 EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor Generic Monitor DefaultDepth24 SubSection Display Modes 1920x1200 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice Configured Mouse EndSection -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420382: installation-reports: Install hangs when 30GB ipod connected via USB
Did anyone get a chance to check out the log I sent? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#383642: xspecs: Still Not Fixed
Package: xspecs Version: 1:1.2+git20061105-3 Followup-For: Bug #383642 Hi, this bug was not resolved. PDF files are still missing. -Andrew -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20.7 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369461: xspecs: Still Not Fixed
Package: xspecs Version: 1:1.2+git20061105-3 Followup-For: Bug #369461 Hi, this bug was not resolved as described. Text files are still missing. -Andrew -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.20.7 Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420382: installation-reports: Install hangs when 30GB ipod connected via USB
I've attached the syslog after adding set -x to /lib/partman/definitions.sh, as requested. The reason I suggest adding it to the workarounds is because it is not obvious that it is the ipod that is causing the hang. It took me a few hours to figure out that /dev/scsi/host2 was actually my ipod, which normally I don't consider as an HD - I just have it connected all the time so that it charges. On 4/22/07, Frans Pop [EMAIL PROTECTED] wrote: reassign 420382 partman-base thanks On Sunday 22 April 2007 08:14, Christian Perrier wrote: During Starting up the partitioner.. Scanning disks... I get the message Warning! Device /dev/scsi/host2/bus0/target0/lun0/disc has logical sector size of 2048. Not all parts of GNU parted support this at the moment, and the working code is highly experimental. That message obviously seem to come from gparted. How is it displayed on screen? Not gparted, but libparted. I read this message as a warning that devices with a sector size of 2048 are not really supported by libparted and that if you continue you run a risk of losing the data on the device and possibly even the device (if it cannot be formatted again). Personally I probably would not continue even if the partitioner did not hang. AFAIK, normal sector sizes are 512 and 1024. The only people who can tell if this warning is still valid or not and what the status of support for 2048 size sectors is, are the maintainers (and possibly only the upstream maintainers) of libparted. My understanding is that this failure is badly handled by partman. But this needs to be confirmed. It is correct that partman should not hang, and the fact that it does is probably an indication that it really is not supported. AFAIK such messages from partman are normally fairly well handled. Is the installer hanging completely, or can you still switch to VT2? If you can, it would be interesting if you could add a line set -x near the top of /lib/partman/definitions.sh _before_ partman is run (using nano as editor), and send us /var/log/syslog (gzipped) after the hang. That would give us the information on where exactly the warning is displayed and the hang occurs. The option Save debug logs in the main menu may help as well. As you are the first person to report this issue, I don't think we'll add it in the errata just yet, but we'll keep the issue in mind. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#420382: installation-reports: Install hangs when 30GB ipod connected via USB
this time I've actually attached it. -Andrew On 4/22/07, Andrew Chant [EMAIL PROTECTED] wrote: I've attached the syslog after adding set -x to /lib/partman/definitions.sh, as requested. The reason I suggest adding it to the workarounds is because it is not obvious that it is the ipod that is causing the hang. It took me a few hours to figure out that /dev/scsi/host2 was actually my ipod, which normally I don't consider as an HD - I just have it connected all the time so that it charges. On 4/22/07, Frans Pop [EMAIL PROTECTED] wrote: reassign 420382 partman-base thanks On Sunday 22 April 2007 08:14, Christian Perrier wrote: During Starting up the partitioner.. Scanning disks... I get the message Warning! Device /dev/scsi/host2/bus0/target0/lun0/disc has logical sector size of 2048. Not all parts of GNU parted support this at the moment, and the working code is highly experimental. That message obviously seem to come from gparted. How is it displayed on screen? Not gparted, but libparted. I read this message as a warning that devices with a sector size of 2048 are not really supported by libparted and that if you continue you run a risk of losing the data on the device and possibly even the device (if it cannot be formatted again). Personally I probably would not continue even if the partitioner did not hang. AFAIK, normal sector sizes are 512 and 1024. The only people who can tell if this warning is still valid or not and what the status of support for 2048 size sectors is, are the maintainers (and possibly only the upstream maintainers) of libparted. My understanding is that this failure is badly handled by partman. But this needs to be confirmed. It is correct that partman should not hang, and the fact that it does is probably an indication that it really is not supported. AFAIK such messages from partman are normally fairly well handled. Is the installer hanging completely, or can you still switch to VT2? If you can, it would be interesting if you could add a line set -x near the top of /lib/partman/definitions.sh _before_ partman is run (using nano as editor), and send us /var/log/syslog (gzipped) after the hang. That would give us the information on where exactly the warning is displayed and the hang occurs. The option Save debug logs in the main menu may help as well. As you are the first person to report this issue, I don't think we'll add it in the errata just yet, but we'll keep the issue in mind. Cheers, FJP syslog.gz Description: GNU Zip compressed data
Bug#420382: installation-reports: Install hangs when 30GB ipod connected via USB
I've attached the new log. I think you found the problem - close_dialog is not returning. BTW the file was /lib/partman/ not /var/lib/partman/..., I hope.. What happens is after I get the previously-described message, I can click continue or go back from that message. Regardless of which I click, the screen simply returns to the Starting up Partitioner - Scanning Disks 41% progress bar. -Andrew On 4/22/07, Frans Pop [EMAIL PROTECTED] wrote: On Sunday 22 April 2007 09:18, Andrew Chant wrote: I've attached the syslog after adding set -x to /lib/partman/definitions.sh, as requested. Thank you for the log. It shows the warning being displayed, but not what happens after that. I've done some testing of my own, simulating the error (though not actually triggering the error in the library) and I cannot reproduce any hang. Can you describe the hang and when exactly it happens in more detail? What should happen is that when you get the warning, you can choose either Go Back or Continue. In fact, what you choose does not matter. Can you still do this? Does the warning disappear? Does the progress bar progress at all after that? Could you do another test and add a few logging statements near the bottom of /var/lib/partman/init.d/30parted as follows: cd $dev logger -t test Opening device open_dialog OPEN $(cat $dev/device) logger -t test Back from dialog read_line response logger -t test Response is: '$response' close_dialog logger -t test Dialog closed if [ $response = failed ]; then cd / rm -rf $dev fi Please also add the set -x in that script instead of definitions.sh this time. The reason I suggest adding it to the workarounds is because it is not obvious that it is the ipod that is causing the hang. It took me a few hours to figure out that /dev/scsi/host2 was actually my ipod, which normally I don't consider as an HD - I just have it connected all the time so that it charges. Well, it's detected as an USB stick by linux, so from our point of view it's perfectly normal that it is detected at that stage. Having additional storage devices (not needed for the install itself) plugged into a system is in general not advisable, and an iPod _is_ a storage device :-) Cheers, FJP syslog.gz Description: GNU Zip compressed data
