Bug#704278: marked as done (anarchism won't start because of missing init script)
Your message dated Sun, 31 Mar 2013 15:57:35 +0600 with message-id 20130331095735.ga17...@belkar.wrar.name and subject line Re: Bug#704278: anarchism won't start because of missing init script has caused the Debian Bug report #704278, regarding anarchism won't start because of missing init script to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: anarchism Version: 13.4-1 Severity: critical Justification: breaks the whole system The anarchism package is broken for a long time now (at least since Debian Potatoe). Manpages are fully functional but it seems as if someone forgot to implement an init script to start anarchism. Anarchism is quite useless without getting started at one point. Another feature to implement is the new kernel device module for /dev/riot in the next official release of all debian kernels to fix the essential bug of the anarchism process not starting up. For full mass support the blockdevice /dev/occupy might also be needed. Also, the package revoltution should be recommend, but because Revolution is indeed a violent process we suggest the package individual-revolution 0.9. For full economic support the package syndicalism-0910 or better should be a dependency as well. -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash anarchism depends on no packages. anarchism recommends no packages. Versions of packages anarchism suggests: pn www-browser none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- On Sun, Mar 31, 2013 at 12:04:34AM +, Emma Goldman wrote: Package: anarchism Version: 13.4-1 Severity: critical Justification: breaks the whole system The anarchism package is broken for a long time now (at least since Debian Potatoe). Manpages are fully functional but it seems as if someone forgot to implement an init script to start anarchism. Anarchism is quite useless without getting started at one point. Another feature to implement is the new kernel device module for /dev/riot in the next official release of all debian kernels to fix the essential bug of the anarchism process not starting up. For full mass support the blockdevice /dev/occupy might also be needed. Also, the package revoltution should be recommend, but because Revolution is indeed a violent process we suggest the package individual-revolution 0.9. For full economic support the package syndicalism-0910 or better should be a dependency as well. It's only March 31st. -- WBR, wRAR signature.asc Description: Digital signature ---End Message---
Bug#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t
On Sat, Mar 30, 2013 at 05:37:27PM +, Dominic Hargreaves wrote: In a clean wheezy chroot: ok 51 - code not ok 52 - errstr # Failed test 'errstr' # at t/050-async-client.t line 268. # 'Lua error: stack overflow (call: out of stack)' # doesn't match '(?^:Partial key in)' FWIW it didn't fail here in a sid am64 chroot. -- WBR, wRAR signature.asc Description: Digital signature
Bug#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t
On Sun, Mar 31, 2013 at 04:00:24PM +0600, Andrey Rahmatullin wrote: On Sat, Mar 30, 2013 at 05:37:27PM +, Dominic Hargreaves wrote: In a clean wheezy chroot: ok 51 - code not ok 52 - errstr # Failed test 'errstr' # at t/050-async-client.t line 268. # 'Lua error: stack overflow (call: out of stack)' # doesn't match '(?^:Partial key in)' FWIW it didn't fail here in a sid am64 chroot. True; in sid, the failure (with 0.15-1) seems to come at # Failed test 'errstr' # at t/020-low_level_client.t line 125. # 'Duplicate key exists in unique index 0' # doesn't match '(?^:already exists)' (i386 and amd64). Note also the different bug report for 0.35-1: #704266 I should note I don't have any personal interest in this back, but came across the failures when testing for perl 5.16 specific breakage. Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704267: libdr-tarantool-perl: FTBFS: test failure: t/050-async-client.t
On Sun, Mar 31, 2013 at 12:54:32PM +0100, Dominic Hargreaves wrote: FWIW it didn't fail here in a sid am64 chroot. True; in sid, the failure (with 0.15-1) seems to come at # Failed test 'errstr' # at t/020-low_level_client.t line 125. # 'Duplicate key exists in unique index 0' # doesn't match '(?^:already exists)' (i386 and amd64). Oh, I also missed the fact that the bug has a different version that I tested. So, to be clear, I tested 0.35-1 which is the sid version. 0.15-1 from testing on a sid amd64 chroot fails with the same error as in your quote above. -- WBR, wRAR signature.asc Description: Digital signature
Bug#704266: libdr-tarantool-perl: FTBFS: test failure: t/110-netsplit-readahead.t
On Sat, Mar 30, 2013 at 05:23:25PM +, Dominic Hargreaves wrote: Source: libdr-tarantool-perl Version: 0.35-1 Severity: serious Justification: FTBFS Tags: sid This package FTBFS in a clean sid chroot: # Failed test 'delay maximum' # at t/110-netsplit-readahead.t line 141. # '0.468052864074707' # # '0.331' # Looks like you failed 1 test of 24. t/110-netsplit-readahead.t .. 1..24 I cannot reproduce this with an amd64 sid sbuild, the package builds corectly there. -- WBR, wRAR signature.asc Description: Digital signature
Bug#704111: marked as done (clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting.)
Your message dated Sun, 31 Mar 2013 12:32:44 + with message-id e1umhre-0004yc...@franck.debian.org and subject line Bug#704111: fixed in clang 1:3.0-6.2 has caused the Debian Bug report #704111, regarding clang fails to correctly implement hard float ABI during default compiles due to rediculously low default CPU setting. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: clang Version: 1:3.0-6.1 Severity: grave x-debbugs-cc: debian-...@lists.debian.org; cfe-...@cs.uiuc.edu (note for non-debian people reading this, the version of clang in debian wheezy is a 3.0 based version which already has patches to make it invoke the linker with appropriate arguments. The llvm version also appears to be 3.0 again somewhat patched by debian) I recently discovered that the version of clang in debian wheezy and raspbian wheezy does not work correctly on either debian armhf or raspbian. It seems the problem is that clang can't work out what CPU type it should be using and defaults to something very low (specifically arm7tdmi). With this CPU selected clang silently fails to properly use the hard float ABI and as such any armhf code it generates is broken and won't call floating point routines correctly. It also causes an assertion failure in the bfd linker (but links successfully with the gold linker). Setting the CPU type to something sensible makes it implement the hard float ABI correctly and also stops the assertion failure in the bfd linker. I have managed to figure out how to patch clang to change the default CPU for armhf (patch attatched). However i'm not sure what it is best to set it to for debian armhf*. In particular this block of code from just below where my patch is applied seems to map all armv7 variants to a CPU type of coretex-a8. return llvm::StringSwitchconst char *(MArch) .Cases(armv2, armv2a,arm2) .Case(armv3, arm6) .Case(armv3m, arm7m) .Cases(armv4, armv4t, arm7tdmi) .Cases(armv5, armv5t, arm10tdmi) .Cases(armv5e, armv5te, arm1026ejs) .Case(armv5tej, arm926ej-s) .Cases(armv6, armv6k, arm1136jf-s) .Case(armv6j, arm1136j-s) .Cases(armv6z, armv6zk, arm1176jzf-s) .Case(armv6t2, arm1156t2-s) .Cases(armv7, armv7a, armv7-a, cortex-a8) .Cases(armv7r, armv7-r, cortex-r4) .Cases(armv7m, armv7-m, cortex-m3) .Case(ep9312, ep9312) .Case(iwmmxt, iwmmxt) .Case(xscale, xscale) .Cases(armv6m, armv6-m, cortex-m0) // If all else failed, return the most base CPU LLVM supports.
Bug#659861: Processed: your mail
On 31.03.2013 00:17, Thorsten Glaser wrote: Adam D. Barratt dixit: In which case it should probably be closed, as it doesn't apply to any current package in the archive and no changes in the package are required to resolve it. OK. Hrm. How do I tell the BTS’ version tracking that it’s fixed in 1:1.12.13-12+squeeze1+b1 on amd64 and not found in 1:1.12.13-12+squeeze1 on all other architectures… I don't think you can (in either case). You can mark a bug as found / fixed in a binary version, but the BTS will translate that to the corresponding source version. Similarly bug versions apply to the package, not to particular architectures. I think the cleanest solution is simply to mark the report as closed, on the basis that it wasn't a bug in the source and was resolved without any changes to the source. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: closing 658295, closing 659390
Processing commands for cont...@bugs.debian.org:
unarchive 659390
Bug #659390 {Done: David Prévot taf...@debian.org} [semanticscuttle]
semanticscuttle: config.default.php not found
Unarchived Bug 659390
reopen 659390
Bug #659390 {Done: David Prévot taf...@debian.org} [semanticscuttle]
semanticscuttle: config.default.php not found
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions semanticscuttle/0.98.4+dfsg-1.
found 659390 0.98.4+dfsg-1
Bug #659390 [semanticscuttle] semanticscuttle: config.default.php not found
Marked as found in versions semanticscuttle/0.98.4+dfsg-1.
severity 659390 grave
Bug #659390 [semanticscuttle] semanticscuttle: config.default.php not found
Severity set to 'grave' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
659390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659390: bug#670232
On Sun, Mar 31, 2013 at 03:23:23PM +0200, Ana Guerrero wrote: unarchive 659390 reopen 659390 found 659390 0.98.4+dfsg-1 severity 659390 grave thanks On Sun, Aug 19, 2012 at 04:53:33PM -0400, David Prévot wrote: close 658295 0.98.4+dfsg-1 close 659390 0.98.4+dfsg-1 thanks The bugs have not been closed automatically because they were fixed in version 0.98.3+dfsg-6 that has never been uploaded, superseded by 0.98.4+dfsg-1 that contains those fixes as documented in the changelog. Hi, The bug is still there, just ran into it. The changelog of the version 0.98.3+dfsg-6, mentions fixing the warnings when restarting apache that are mentioned in this bug report and close this bug. But they don't solve the problem originally reported. Tiago's summary of the problem is good: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659390#47 And without populating the database, the package is useless, that's why I'm raising the severity. And this bug was reported already some time ago: http://bugs.debian.org/670232 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659390: closing 658295, closing 659390
unarchive 659390 reopen 659390 found 659390 0.98.4+dfsg-1 severity 659390 grave thanks On Sun, Aug 19, 2012 at 04:53:33PM -0400, David Prévot wrote: close 658295 0.98.4+dfsg-1 close 659390 0.98.4+dfsg-1 thanks The bugs have not been closed automatically because they were fixed in version 0.98.3+dfsg-6 that has never been uploaded, superseded by 0.98.4+dfsg-1 that contains those fixes as documented in the changelog. Hi, The bug is still there, just ran into it. The changelog of the version 0.98.3+dfsg-6, mentions fixing the warnings when restarting apache that are mentioned in this bug report and close this bug. But they don't solve the problem originally reported. Tiago's summary of the problem is good: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659390#47 And without populating the database, the package is useless, that's why I'm raising the severity. Ana -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704190: ltsp-build-client fails because of apt GPG error
Package: debootstrap Version: 1.0.44 Followup-For: Bug #704190 Vagrant, thanks for reply. Both mirrors You gave don't work, ltsp-build-client ends with error such as: E: unknown location http.debian.net/debian/dists/wheezy/InRelease error: LTSP client installation ended abnormally I don't see any reason for marking the bug wishlist. For now the ltsp-server- standalone package is not working at all for some users, depending on redirector. I think serious is more than appropriate. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=sk_SK.UTF-8, LC_CTYPE=sk_SK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debootstrap depends on: ii wget 1.13.4-3 Versions of packages debootstrap recommends: ii debian-archive-keyring 2012.4 ii gnupg 1.4.12-7 debootstrap suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659861: Processed: your mail
Adam D. Barratt dixit: I don't think you can (in either case). You can mark a bug as found / fixed in a binary version, but the BTS will translate that to the corresponding source version. Similarly bug versions apply to the package, not to particular architectures. Hrm. I think the cleanest solution is simply to mark the report as closed, on the basis that it wasn't a bug in the source and was resolved without any changes to the source. Okay, that’s the current state AFAICT. bye, //mirabilos -- [DJBDNS Zone] TTL 86400 – Natureshadow kann man da auch 1d schreiben? mirabilos nö, außerdem kann ein Deutscher oder ein Japaner mit 1d ja erstmal nix anfangen, oder könntest du 1日 im zone file lesen? Natureshadow das heißt für mich: ein Regal, das u.U. schiefstehen könnte -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#704190: ltsp-build-client fails because of apt GPG error
Processing control commands:
tags 704190 confirmed
Bug #704190 {Done: Christian Perrier bubu...@debian.org} [debootstrap]
ltsp-build-client fails because of apt GPG error
Bug #703146 {Done: Christian Perrier bubu...@debian.org} [debootstrap] apt:
BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)?
Added tag(s) confirmed.
Added tag(s) confirmed.
--
703146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703146
704190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704190: ltsp-build-client fails because of apt GPG error
Control: tags 704190 confirmed On Sun, Mar 31, 2013 at 03:37:25PM +0200, Peter Tuharsky wrote: thanks for reply. Both mirrors You gave don't work, ltsp-build-client ends with error such as: E: unknown location http.debian.net/debian/dists/wheezy/InRelease error: LTSP client installation ended abnormally I don't see any reason for marking the bug wishlist. For now the ltsp-server- standalone package is not working at all for some users, depending on redirector. I think serious is more than appropriate. Apologies; I tested it with the version of debootstrap from sid (1.0.47). That was sloppy on my part... I *was* able to reproduce the bug you experienced with ltsp-build-client with the debootstrap version from wheezy (1.0.44). I believe installing the newer version of debootstrap should resolve your issue. It has now been reassigned and merged with the debootstrap bug, which is marked as serious severity, and needs to get fixed for wheezy. Thanks for the report! live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695224: Locale::Maketext versioning in perl package
Dear release team, There is a problem with the perl package, as discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695224#55 onwards, whereby the application of the security fix in that ticket now causes double-escaping problems where people workaround the problem by escaping themselves, when they detect an earlier Locale::Maketext by version number. I am slightly wary about importing the new (1.23) version of Locale::Maketext as I mentioned in that bug already, but my fears may be unfounded. Could you comment about whether you would accept such a change in wheezy at this time? (I can't really decide whether it's RC or not). I've attached a diff which implements the change in question. I haven't carried out extensive testing yet, but the package builds fine. The same change is in the dom/locale-maketext-version branch of the git repository at http://anonscm.debian.org/gitweb/?p=perl/perl.git. Note that if you approve this, I would still want to get feedback from Niko, co-maintainer of the perl pacakge, before an upload. This also affects stable, and so I've also CCed the security team (the problem was introduced in a DSA). Thanks as always for your excellent work (especially during the freeze) and apologies for bringing such a thorny issue to you this close to release. Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) diff --git a/debian/.git-dpm b/debian/.git-dpm index 2a4791b..c8c980a 100644 --- a/debian/.git-dpm +++ b/debian/.git-dpm @@ -1,6 +1,6 @@ # see git-dpm(1) from git-dpm package -89405c8ebc5bf8ae4ed6479de2bc0f311c1f6fe1 -89405c8ebc5bf8ae4ed6479de2bc0f311c1f6fe1 +93f6c83c7454de33df00a0e3fde3a890d6c87e91 +93f6c83c7454de33df00a0e3fde3a890d6c87e91 5f99bf7a09dd2ae3c22081331f4973210a543731 5f99bf7a09dd2ae3c22081331f4973210a543731 perl_5.14.2.orig.tar.bz2 diff --git a/debian/changelog b/debian/changelog index dd05cd9..e306117 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +perl (5.14.2-21) UNRELEASED; urgency=low + + * Update the Locale::Maketext fix by importing 1.23, to avoid +double-escaping problems (see: #695224) + + -- Dominic Hargreaves d...@earth.li Sun, 31 Mar 2013 13:58:59 +0100 + perl (5.14.2-20) unstable; urgency=low * Fix an Encode memory leak that occurred in the UTF-8 encoding. diff --git a/debian/patches/fixes/64bitint-signedness-wraparound.diff b/debian/patches/fixes/64bitint-signedness-wraparound.diff index cae0b3d..edeaf9e 100644 --- a/debian/patches/fixes/64bitint-signedness-wraparound.diff +++ b/debian/patches/fixes/64bitint-signedness-wraparound.diff @@ -1,4 +1,4 @@ -From e36d65ba661bd0f9c9ae741c8f18d2e08682e97a Mon Sep 17 00:00:00 2001 +From 3e75c3189622c59ded9070bf678ef42f8185961a Mon Sep 17 00:00:00 2001 From: Andy Dougherty dough...@lafayette.edu Date: Wed, 16 Jan 2013 12:30:43 -0500 Subject: Avoid wraparound when casting unsigned size_t to signed ssize_t. diff --git a/debian/patches/fixes/digest-sha-doublefree.diff b/debian/patches/fixes/digest-sha-doublefree.diff index c49a84a..b9a1e12 100644 --- a/debian/patches/fixes/digest-sha-doublefree.diff +++ b/debian/patches/fixes/digest-sha-doublefree.diff @@ -1,4 +1,4 @@ -From d2d9e1560afaeb402dda69eba1d6e808d80c0c96 Mon Sep 17 00:00:00 2001 +From 0c6c3e57ab9ee86fbce162071dce1c2748a494b5 Mon Sep 17 00:00:00 2001 From: Niko Tyni nt...@debian.org Date: Fri, 25 Jan 2013 15:00:00 +0200 Subject: Fix a double-free bug in Digest::SHA diff --git a/debian/patches/fixes/encode-memleak.diff b/debian/patches/fixes/encode-memleak.diff index b30e6d0..baed27f 100644 --- a/debian/patches/fixes/encode-memleak.diff +++ b/debian/patches/fixes/encode-memleak.diff @@ -1,4 +1,4 @@ -From 89405c8ebc5bf8ae4ed6479de2bc0f311c1f6fe1 Mon Sep 17 00:00:00 2001 +From 93f6c83c7454de33df00a0e3fde3a890d6c87e91 Mon Sep 17 00:00:00 2001 From: chansen chan...@cpan.org Date: Sun, 3 Mar 2013 22:43:53 +0100 Subject: Encode: Fixed a memory leak that occurred in the UTF-8 encoding. diff --git a/debian/patches/fixes/hsplit-rehash.diff b/debian/patches/fixes/hsplit-rehash.diff index c2fd7e2..ba235f7 100644 --- a/debian/patches/fixes/hsplit-rehash.diff +++ b/debian/patches/fixes/hsplit-rehash.diff @@ -1,4 +1,4 @@ -From 5d86bf622ad5ac2cc69da54d76000a4618518410 Mon Sep 17 00:00:00 2001 +From ac695b3c3106de8292c4200c84ab4c57b6998b73 Mon Sep 17 00:00:00 2001 From: Yves Orton demer...@gmail.com Date: Tue, 12 Feb 2013 10:53:05 +0100 Subject: Prevent premature hsplit() calls, and only trigger REHASH after diff --git a/debian/patches/fixes/maketext-code-execution.diff b/debian/patches/fixes/maketext-code-execution.diff index 117ef2d..b781de9 100644 --- a/debian/patches/fixes/maketext-code-execution.diff +++ b/debian/patches/fixes/maketext-code-execution.diff @@ -1,4 +1,4 @@ -From 9da6928f4cbc7cfa3c2c474b00042a51083e12af Mon Sep 17 00:00:00 2001 +From 97aa10fd1926ed8299448eb69f70c01546918d15 Mon Sep 17 00:00:00 2001 From: Brian Carlson
Bug#704418: openjdk-7: Re: Your message to Ubuntu-devel-discuss awaits moderator approval
Source: openjdk-7 Version: 7u17-2.3.8-1 Severity: serious The maintainer address bounces as it switched to the Ubuntu devel mailing list: ubuntu-devel-discuss-boun...@lists.ubuntu.com writes: Your mail to 'Ubuntu-devel-discuss' with the subject Processing of openjdk-7_7u17-2.3.8-1_amd64.changes Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: https://lists.ubuntu.com/mailman/confirm/ubuntu-devel-discuss/3940a73b229e088a37189e037b35c8802511f0ff -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686200: open-vm-tools: fails to upgrade do failing to stop the old daemon
severity 686200 minor retitle 686200 doesn't need the additional sleep 1 in init anymore thanks Bernd Zeimetz b.zeim...@conova.com wrote: you've added the one second sleep fix to the init script again i have not added it, i kept it, and included a non-intrusive version of the patch you did in the NMU (see 2:9.2.2-893683-1). keeping the sleep 1 is purely cosmetic. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: open-vm-tools: fails to upgrade do failing to stop the old daemon
Processing commands for cont...@bugs.debian.org: severity 686200 minor Bug #686200 [open-vm-tools] open-vm-tools: fails to upgrade do failing to stop the old daemon Severity set to 'minor' from 'serious' retitle 686200 doesn't need the additional sleep 1 in init anymore Bug #686200 [open-vm-tools] open-vm-tools: fails to upgrade do failing to stop the old daemon Changed Bug title to 'doesn't need the additional sleep 1 in init anymore' from 'open-vm-tools: fails to upgrade do failing to stop the old daemon' thanks Stopping processing here. Please contact me if you need assistance. -- 686200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org: # Sunday 31 March 19:03:13 UTC 2013 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: a href=http://packages.qa.debian.org/virtualbox;virtualbox/a tags 703358 + pending Bug #703358 [virtualbox-guest-dkms] virtualbox-guest-dkms: vboxvideo_drm.c fails to compile after upgrade of linux-headers-3.2.0-4 from 3.2.35-2 to 3.2.39-2 Bug #703239 [virtualbox-guest-dkms] virtualbox-guest-x11: Bad return status for module build on kernel Added tag(s) pending. Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 703239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703239 703358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614498: svn 90
hi I tried guppy SVN 90. It works with python 2.7 in Debian wheezy. a. -- Andrea Mennucc E' un mondo difficile. Che vita intensa! (Tonino Carotone) signature.asc Description: Digital signature
Bug#703823: marked as done (amarok: Not installable)
Your message dated Sun, 31 Mar 2013 22:39:35 +0200 with message-id 51589f07.1050...@gmail.com and subject line Closing has caused the Debian Bug report #703823, regarding amarok: Not installable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 703823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: amarok Version: 2.7.0-1 Severity: grave Justification: renders package unusable Amarok 2.7.0-1 is uninstallable: $ apt-get -t experimental install amarok Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: amarok : Depends: libavcodec-extra-53 (= 6:0.8.3-1~) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Best regards Torquil Sørensen -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (700, 'unstable'), (500, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.4 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages amarok-common depends on: ii perl 5.14.2-20 amarok-common recommends no packages. Versions of packages amarok is related to: ii phonon-backend-gstreamer [phonon-backend] 4:4.6.0.0-2 ---End Message--- ---BeginMessage--- Package: amarok Version: 2.7.0-1 Closing this bug. The problem was related to having packages from deb-multimedia.org Best regards Torquil Sørensen---End Message---
Bug#703239: marked as done (virtualbox-guest-x11: Bad return status for module build on kernel)
Your message dated Sun, 31 Mar 2013 20:52:05 + with message-id e1umpet-0003ma...@franck.debian.org and subject line Bug#703358: fixed in virtualbox 4.1.18-dfsg-2+deb7u1 has caused the Debian Bug report #703358, regarding virtualbox-guest-x11: Bad return status for module build on kernel to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 703358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: virtualbox-guest-x11: Bad return status for module build on kernel Package: virtualbox-guest-x11 Version: 4.1.18-dfsg-2 Justification: renders package unusable Severity: grave Dear Maintainer, please have a look at the following logs. Tell me in case you need further information, I shall provide. sudo apt-get install virtualbox-guest-x11 Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: virtualbox-guest-dkms virtualbox-guest-utils The following NEW packages will be installed: virtualbox-guest-dkms virtualbox-guest-utils virtualbox-guest-x11 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 1589 kB of archives. After this operation, 9878 kB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://ftp.us.debian.org/debian/ wheezy/main virtualbox-guest-utils i386 4.1.18-dfsg-2 [328 kB] Get:2 http://ftp.us.debian.org/debian/ wheezy/main virtualbox-guest-dkms all 4.1.18-dfsg-2 [435 kB] Get:3 http://ftp.us.debian.org/debian/ wheezy/main virtualbox-guest-x11 i386 4.1.18-dfsg-2 [826 kB] Fetched 1589 kB in 34s (46.3 kB/s) Selecting previously unselected package virtualbox-guest-utils. (Reading database ... 80131 files and directories currently installed.) Unpacking virtualbox-guest-utils (from .../virtualbox-guest-utils_4.1.18-dfsg- 2_i386.deb) ... Selecting previously unselected package virtualbox-guest-dkms. Unpacking virtualbox-guest-dkms (from .../virtualbox-guest-dkms_4.1.18-dfsg- 2_all.deb) ... Selecting previously unselected package virtualbox-guest-x11. Unpacking virtualbox-guest-x11 (from .../virtualbox-guest-x11_4.1.18-dfsg- 2_i386.deb) ... Processing triggers for man-db ... Setting up virtualbox-guest-utils (4.1.18-dfsg-2) ... Setting up virtualbox-guest-dkms (4.1.18-dfsg-2) ... Loading new virtualbox-guest-4.1.18 DKMS files... First Installation: checking all kernels... Building only for 3.2.0-4-686-pae Building initial module for 3.2.0-4-686-pae Error! Bad return status for module build on kernel: 3.2.0-4-686-pae (i686) Consult /var/lib/dkms/virtualbox-guest/4.1.18/build/make.log for more information. Setting up virtualbox-guest-x11 (4.1.18-dfsg-2) ... DKMS make.log for virtualbox-guest-4.1.18 for kernel 3.2.0-4-686-pae (i686) Sun Mar 17 09:30:25 UTC 2013 make: Entering directory `/usr/src/linux-headers-3.2.0-4-686-pae' LD /var/lib/dkms/virtualbox-guest/4.1.18/build/built-in.o LD /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/built-in.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VBoxGuest- linux.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VBoxGuest.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VBoxGuest2.o CC [M] /var/lib/dkms/virtualbox- guest/4.1.18/build/vboxguest/GenericRequest.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/HGCMInternal.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/Init.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/PhysHeap.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/SysHlp.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VMMDev.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/alloc- r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/initterm- r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/memobj- r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv /mpnotification-r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv /powernotification-r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/linux /alloc-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/linux /assert-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/linux /initterm-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/linux /memobj-r0drv-linux.o CC [M]
Bug#703358: marked as done (virtualbox-guest-dkms: vboxvideo_drm.c fails to compile after upgrade of linux-headers-3.2.0-4 from 3.2.35-2 to 3.2.39-2)
Your message dated Sun, 31 Mar 2013 20:52:05 + with message-id e1umpet-0003ma...@franck.debian.org and subject line Bug#703358: fixed in virtualbox 4.1.18-dfsg-2+deb7u1 has caused the Debian Bug report #703358, regarding virtualbox-guest-dkms: vboxvideo_drm.c fails to compile after upgrade of linux-headers-3.2.0-4 from 3.2.35-2 to 3.2.39-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 703358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703358 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: virtualbox-guest-dkms Version: 4.1.18-dfsg-2 Severity: important Dear Maintainer, Making dpkg-reconfigure on virtualbox-guest-dkms gives the following error: Loading new virtualbox-guest-4.1.18 DKMS files... Building only for 3.2.0-4-amd64 Building initial module for 3.2.0-4-amd64 Error! Bad return status for module build on kernel: 3.2.0-4-amd64 (x86_64) Consult /var/lib/dkms/virtualbox-guest/4.1.18/build/make.log for more information. The make.log says (full contents of the file attached to the report): [...] CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxvideo/vboxvideo_drm.o [...] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxvideo/vboxvideo_drm.c:115:9: error: field name not in record or union initializer It seems this is the same problem that occurred earlier in RHEL: since linux-3.3.0-rc1 drm_driver::fops is a pointer, but this change was backported to erlier versions of the kernel, which the code in vboxvideo_drm.c does not recognize (it tests only wheather LINUX_VERSION_CODE KERNEL_VERSION(3,3,0)). Indeed, when I replaced the offending file vboxvideo_drm.c with the following downloaded from the internet: https://www.virtualbox.org/svn/vbox/trunk/src/VBox/Additions/linux/drm/vboxvideo_drm.c and added the following line to it: #define DRM_RHEL63 then the compilation went successfully. I recreated the problem and report it from my virtualbox host system (although installing guest additions in a host system makes little sense), but the errors occurring during installation on the guest system (despite a different architecture: pae instead of amd64) were identical. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (901, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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 DKMS make.log for virtualbox-guest-4.1.18 for kernel 3.2.0-4-amd64 (x86_64) Mon Mar 18 19:32:34 CET 2013 make: Entering directory `/usr/src/linux-headers-3.2.0-4-amd64' LD /var/lib/dkms/virtualbox-guest/4.1.18/build/built-in.o LD /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/built-in.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VBoxGuest-linux.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VBoxGuest.o /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VBoxGuest.c: In function ‘VBoxGuestCommonIOCtl’: /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VBoxGuest.c:2480:9: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VBoxGuest2.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/GenericRequest.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/HGCMInternal.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/Init.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/PhysHeap.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/SysHlp.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/VMMDev.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/alloc-r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/initterm-r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/memobj-r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/mpnotification-r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/powernotification-r0drv.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/linux/alloc-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/linux/assert-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/linux/initterm-r0drv-linux.o CC [M] /var/lib/dkms/virtualbox-guest/4.1.18/build/vboxguest/r0drv/linux/memobj-r0drv-linux.o CC [M]
Bug#704422: dovecot-solr: Segfault using dovecot-solr plug-in
Package: dovecot-solr
Version: 1:2.1.7-7
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After setting up a tomcat-solr instance, if I try to use the
dovecot-solr plug-in, I get segfaults on login.
I modified my dovecot.conf as follows:
mail_plugins = $mail_plugins fts fts_solr
plugin {
fts = solr
fts_squat = url=http://localhost:8080/solr/
}
# mail_plugins = $mail_plugins fts fts_squat
#
# plugin {
# fts = squat
# fts_squat = partial=4 full=4
# }
Dovecot works when the commented-out section is used instead of the
uncommented-out section. When using the fts_solr plugin, the session
segfaults after IMAP login:
md5i@maru:/usr/local/home/md5i$ telnet localhost imap
Trying 127.0.0.1...
Connected to maru.md5i.com.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE
STARTTLS AUTH=PLAIN] Dovecot ready.
1 login md5i
Connection closed by foreign host.
The following is logged:
== /var/log/mail.log ==
Mar 31 15:43:03 maru dovecot: imap(md5i): Fatal: master: service(imap):
child 17060 killed with signal 11 (core dumped)
I can get a core dump, but have been unable to get a usable backtrace,
even with the dovecot-dbg package installed.
Marked as grave since this renders the dovecot-solr package
unusable. Feel free to downgrade if this if appropriate. I am happy
to supply further information by request.
-- Package-specific info:
dovecot configuration
-
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-686-pae i686 Debian 7.0
mail_plugins = fts fts_squat
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date ihave
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox Sent Messages {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
driver = pam
}
plugin {
fts = squat
fts_squat = partial=4 full=4
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap sieve
service managesieve-login {
inet_listener sieve {
port = 4190
}
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
driver = passwd
}
protocol lda {
mail_plugins = sieve
}
-- System Information:
Debian Release: 7.0
APT prefers unstable
APT policy: (102, 'unstable'), (101, 'experimental'), (99, 'testing'), (9,
'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (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 dovecot-solr depends on:
ii dovecot-core 1:2.1.7-7
ii libc62.13-38
ii libcurl3-gnutls 7.29.0-2
ii libexpat12.1.0-1
dovecot-solr recommends no packages.
dovecot-solr suggests no packages.
Versions of packages dovecot-solr is related to:
ii dovecot-core [dovecot-common] 1:2.1.7-7
ii dovecot-dbg1:2.1.7-7
pn dovecot-devnone
ii dovecot-gssapi 1:2.1.7-7
ii dovecot-imapd 1:2.1.7-7
ii dovecot-ldap 1:2.1.7-7
pn dovecot-lmtpd none
ii dovecot-managesieved 1:2.1.7-7
ii dovecot-mysql 1:2.1.7-7
ii dovecot-pgsql 1:2.1.7-7
pn dovecot-pop3d none
ii dovecot-sieve 1:2.1.7-7
ii dovecot-sqlite 1:2.1.7-7
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704423: systemd: gdm does not start, user sessions have multiple issues, root session works normally
Package: systemd Version: 44-11 Severity: grave Justification: renders package unusable Dear Maintainer, ***I'm marking this as grave because it causes some fairly serious usability issues for me, if you feel this status is incorrect please feel free to change it.*** As you might know, much of GNOME 3.8 has landed in Experimental recently, certainly enough to run a GNOME 3.8 environment at least. GNOME 3.8, or, more specifically, gnome-settings-daemon 3.8, depends on systemd for a number of things, most notably the power manager plugin (requires systemd-logind to be running), leaving me without a power status indicator in GNOME Shell when using sysvinit. As I am operating on a laptop, having this indicator is most definitely desired, so I decided to switch my init system to systemd. This is where things go wrong. Firstly, after the initial boot phase is complete, when the desktop manager (GDM) is supposed to start, it doesn't. Xorg appears to start fine, and I get the busy cursor for a short while as the system seems to be loading, then the cursor changes to the normal pointer and nothing further happens. So I drop to a tty, and log in to my personal account. That's when I get these two messages: -su: /dev/cgroup/cpu/user/2866/tasks: No such file or directory -su: /dev/cgroup/cpu/user/2866/notify_on_release: No such file or directory Already this does not bode well for me. Next, I stop GDM, kill Xorg (for some reason it doesn't quit when GDM is stopped), and start an X session. It takes a few moments, but eventually everything loads and I'm in GNOME Shell. This is when I discover that things aren't working as I would expect them to. The entire environment is very laggy, cursor movements stutter, my audio doesn't work (PulseAudio shows my audio as Dummy Output), the network status indicator doesn't show my network connection status or show a list of nearby networks (or even the Network Settings menu option, nothing at all pops up) when clicked on, and when checking the Graphics information in the Details applet of GNOME Control Center, I see that it's using Gallium 0.4 on llvmpipe (LLVM 0x209) when it should be using my Intel integrated graphics (this probably accounts for the lag and stutters). I do get my power status indicator back, however, my graphical user session basically just doesn't work properly. So I close the session and logout, log in as root, and start an X session. Everything works as I would expect. The environment operates smoothly, I have sound, my graphics adapter is detected properly (Mobile Intel® GM45 Express Chipset), I have my power status indicator, the network status icon reflects my connected status and shows the nearby networks. It all works! So now I'm wondering... Maybe it's a problem with my personal user account? I create a brand new user account, log in as that user (and get two similar messages as when I logged into my personal account), and start an X session. It suffers the same problems as my personal user account. Now I have no idea what's going on, so I decide to file this bug report and hopefully get some ideas of what to do to determine what's going wrong and why, and possibly how to fix it all. All this, because I wanted my power status indicator back, because it doesn't show up when using sysvinit. Everything else seems to work just fine, but that indicator is missing and it bothered me that much. (I will note that I discovered that starting systemd-logind manually when using sysvinit, then killing and restarting gnome-settings-daemon does give me back the power status indicator without any other complications, however, this is not an ideal solution.) You'll have to forgive me for this lengthy report. I really wasn't sure how else to get everything across accurately. -- System Information: Debian Release: 7.0 APT prefers experimental APT policy: (650, 'experimental'), (650, 'unstable'), (600, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii dpkg 1.16.10 ii initscripts 2.88dsf-41 ii libacl1 2.2.51-8 ii libaudit01:1.7.18-1.1 ii libc62.17-0experimental2 ii libcap2 1:2.22-1.2 ii libcryptsetup4 2:1.4.3-4 ii libdbus-1-3 1.6.8-1 ii libkmod2 9-2 ii liblzma5 5.1.1alpha+20120614-2 ii libpam0g 1.1.3-9 ii libselinux1 2.1.12-1 ii libsystemd-daemon0 44-11 ii libsystemd-id128-0 44-11 ii libsystemd-journal0 44-11 ii libsystemd-login044-11 ii libudev0 175-7.1 ii libwrap0 7.6.q-24 ii udev 175-7.1 ii util-linux 2.20.1-5.3 Versions of packages systemd recommends: pn libpam-systemd none Versions of packages systemd suggests: ii
Bug#704300: [scuttle]
Hi,
could you try changing second line in /usr/share/scuttle/www/header.inc.php
from
ini_set('display_errors', '1');
to
ini_set('display_errors', '0');
?
This should silence those warnings not to appear in a browser window. It's a
crude hack, of course.
Cheers,
Jan
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704423: systemd: gdm does not start, user sessions have multiple issues, root session works normally
Get us a debug log of the boot process [1] ii util-linux 2.20.1-5.3 Versions of packages systemd recommends: pn libpam-systemd none Make sure to install libpam-systemd. Michael [1] http://freedesktop.org/wiki/Software/systemd/Debugging -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#704423: systemd: gdm does not start, user sessions have multiple issues, root session works normally
...Wow, I feel really dumb right now. That was all it took to get things working. Thank you so much! (I have to wonder now, though... if that package is necessary to make things work properly, why isn't a dependency of the package?) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#700169: non-free license: requires to obey US export regulation even, when not in the US
Control: retitle -1 please include correct license in upstream tarball Control: severity -1 normal Michael Stapelberg stapelb...@debian.org writes: Can we just ignore this bug for wheezy? To me, the licensing intention seems very clear. I think that's fine. The package seems to be also licensed under the GPL-2 even if that's not clear in the (current) upstream tarball; the notice in the upstream FAQ was already there years ago (I checked on archive.org). It would still be nice to have the correct license in the upstream tarball (and d/copyright as the code seems now to be released under three licenses), but that's not a serious bug. So downgrading accordingly. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: non-free license: requires to obey US export regulation even, when not in the US
Processing control commands: retitle -1 please include correct license in upstream tarball Bug #700169 [src:acpica-unix] non-free license: requires to obey US export regulation even when not in the US Changed Bug title to 'please include correct license in upstream tarball' from 'non-free license: requires to obey US export regulation even when not in the US' severity -1 normal Bug #700169 [src:acpica-unix] please include correct license in upstream tarball Severity set to 'normal' from 'serious' -- 700169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700169 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704423: marked as done (systemd: gdm does not start, user sessions have multiple issues, root session works normally)
Your message dated Mon, 01 Apr 2013 00:35:18 +0200 with message-id 5158ba26.9020...@debian.org and subject line Re: Bug#704423: systemd: gdm does not start, user sessions have multiple issues, root session works normally has caused the Debian Bug report #704423, regarding systemd: gdm does not start, user sessions have multiple issues, root session works normally to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 44-11 Severity: grave Justification: renders package unusable Dear Maintainer, ***I'm marking this as grave because it causes some fairly serious usability issues for me, if you feel this status is incorrect please feel free to change it.*** As you might know, much of GNOME 3.8 has landed in Experimental recently, certainly enough to run a GNOME 3.8 environment at least. GNOME 3.8, or, more specifically, gnome-settings-daemon 3.8, depends on systemd for a number of things, most notably the power manager plugin (requires systemd-logind to be running), leaving me without a power status indicator in GNOME Shell when using sysvinit. As I am operating on a laptop, having this indicator is most definitely desired, so I decided to switch my init system to systemd. This is where things go wrong. Firstly, after the initial boot phase is complete, when the desktop manager (GDM) is supposed to start, it doesn't. Xorg appears to start fine, and I get the busy cursor for a short while as the system seems to be loading, then the cursor changes to the normal pointer and nothing further happens. So I drop to a tty, and log in to my personal account. That's when I get these two messages: -su: /dev/cgroup/cpu/user/2866/tasks: No such file or directory -su: /dev/cgroup/cpu/user/2866/notify_on_release: No such file or directory Already this does not bode well for me. Next, I stop GDM, kill Xorg (for some reason it doesn't quit when GDM is stopped), and start an X session. It takes a few moments, but eventually everything loads and I'm in GNOME Shell. This is when I discover that things aren't working as I would expect them to. The entire environment is very laggy, cursor movements stutter, my audio doesn't work (PulseAudio shows my audio as Dummy Output), the network status indicator doesn't show my network connection status or show a list of nearby networks (or even the Network Settings menu option, nothing at all pops up) when clicked on, and when checking the Graphics information in the Details applet of GNOME Control Center, I see that it's using Gallium 0.4 on llvmpipe (LLVM 0x209) when it should be using my Intel integrated graphics (this probably accounts for the lag and stutters). I do get my power status indicator back, however, my graphical user session basically just doesn't work properly. So I close the session and logout, log in as root, and start an X session. Everything works as I would expect. The environment operates smoothly, I have sound, my graphics adapter is detected properly (Mobile Intel® GM45 Express Chipset), I have my power status indicator, the network status icon reflects my connected status and shows the nearby networks. It all works! So now I'm wondering... Maybe it's a problem with my personal user account? I create a brand new user account, log in as that user (and get two similar messages as when I logged into my personal account), and start an X session. It suffers the same problems as my personal user account. Now I have no idea what's going on, so I decide to file this bug report and hopefully get some ideas of what to do to determine what's going wrong and why, and possibly how to fix it all. All this, because I wanted my power status indicator back, because it doesn't show up when using sysvinit. Everything else seems to work just fine, but that indicator is missing and it bothered me that much. (I will note that I discovered that starting systemd-logind manually when using sysvinit, then killing and restarting gnome-settings-daemon does give me back the power status indicator without any other complications, however, this is not an ideal solution.) You'll have to forgive me for this lengthy report. I really wasn't sure how else to get everything across accurately. -- System Information: Debian Release: 7.0 APT prefers experimental APT policy: (650, 'experimental'), (650, 'unstable'), (600, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/2
Processed: Re: closing 658295, closing 659390
Processing commands for cont...@bugs.debian.org: # the pending was to fix a minor bug, reported in the same bug report... tag 659390 -pending Bug #659390 [semanticscuttle] semanticscuttle: config.default.php not found Removed tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 659390: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659390 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659390: bug#670232
Hi Ana, and others, I will not have time to process this bug in the next two weeks, feel free to NMU or RM. A. -- Evil exists to glorify the good. Evil is negative good. It is a relative term. Evil can be transmuted into good. What is evil to one at one time, becomes good at another time to somebody else. - Sivananda pgpg5763uT68t.pgp Description: PGP signature
Bug#704426: isc-dhcp: cve-2013-2494
package: isc-dhcp severity: serious version: 4.2.2.dfsg.1-5 The embedded bind library is affected by the subject issue. I am currently working on fixed packages. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704426: marked as done (isc-dhcp: cve-2013-2494)
Your message dated Mon, 01 Apr 2013 00:32:47 + with message-id e1umsg3-fh...@franck.debian.org and subject line Bug#704426: fixed in isc-dhcp 4.2.4-6 has caused the Debian Bug report #704426, regarding isc-dhcp: cve-2013-2494 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704426 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: isc-dhcp severity: serious version: 4.2.2.dfsg.1-5 The embedded bind library is affected by the subject issue. I am currently working on fixed packages. ---End Message--- ---BeginMessage--- Source: isc-dhcp Source-Version: 4.2.4-6 We believe that the bug you reported is fixed in the latest version of isc-dhcp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 704...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Gilbert mgilb...@debian.org (supplier of updated isc-dhcp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 31 Mar 2013 23:52:58 + Source: isc-dhcp Binary: isc-dhcp-server isc-dhcp-server-dbg isc-dhcp-server-ldap isc-dhcp-common isc-dhcp-dev isc-dhcp-client isc-dhcp-client-dbg isc-dhcp-client-udeb isc-dhcp-relay isc-dhcp-relay-dbg Architecture: source amd64 Version: 4.2.4-6 Distribution: unstable Urgency: high Maintainer: Debian ISC DHCP maintainers pkg-dhcp-de...@lists.alioth.debian.org Changed-By: Michael Gilbert mgilb...@debian.org Description: isc-dhcp-client - ISC DHCP client isc-dhcp-client-dbg - ISC DHCP client (debugging symbols) isc-dhcp-client-udeb - ISC DHCP Client for debian-installer (udeb) isc-dhcp-common - common files used by all the isc-dhcp* packages isc-dhcp-dev - API for accessing and modifying the DHCP server and client state isc-dhcp-relay - ISC DHCP relay daemon isc-dhcp-relay-dbg - DHCP relay daemon (debugging symbols) isc-dhcp-server - ISC DHCP server for automatic IP address assignment isc-dhcp-server-dbg - ISC DHCP server for automatic IP address assignment (debug) isc-dhcp-server-ldap - DHCP server able to use LDAP as backend Closes: 704426 Changes: isc-dhcp (4.2.4-6) unstable; urgency=high . * Fix cve-2013-2494: issues with regular expression handling in the embedded bind library (closes: #704426). Checksums-Sha1: ddcf7dc06eeb580990ff60b8a5b2ceae6ac47860 3246 isc-dhcp_4.2.4-6.dsc cf60825dce0d1317483b4e7989a3e4e67f01ef2b 95367 isc-dhcp_4.2.4-6.debian.tar.gz 84bfcbfe0e0e4158ed1272c743db7a67ded208bd 935444 isc-dhcp-server_4.2.4-6_amd64.deb abe90232de78b29ba3f5f1e3571e579c0a17ad66 2581876 isc-dhcp-server-dbg_4.2.4-6_amd64.deb 4922ef1aa20d3222b5147aa638a480dfd30f80a5 880568 isc-dhcp-server-ldap_4.2.4-6_amd64.deb 49f7bfd9da8258314c29ca0e1822d5e23f557017 855162 isc-dhcp-common_4.2.4-6_amd64.deb 31fd67240a48b52996cda14a7f57c4356a35db1b 774352 isc-dhcp-dev_4.2.4-6_amd64.deb 539f335f937f4e986784ee5bd07c5ac38811ba04 793882 isc-dhcp-client_4.2.4-6_amd64.deb 9fe05927dd0714552f338d50dd42c78489827f1f 2253404 isc-dhcp-client-dbg_4.2.4-6_amd64.deb 896395f341ebb7dcedd6a5eaff6801604f379f3b 52 isc-dhcp-client-udeb_4.2.4-6_amd64.udeb ed8227b2d969edc59104e5bc4d2a0f73a29905e4 734454 isc-dhcp-relay_4.2.4-6_amd64.deb db3e6db6e41265e42af731cc946b7aaddfc5601f 2155602 isc-dhcp-relay-dbg_4.2.4-6_amd64.deb Checksums-Sha256: f8f4a688d926fc2e266b4c4589dc2fc31dde6e94432074eab59d7431d1e61382 3246 isc-dhcp_4.2.4-6.dsc e9e5c70b81f3fe404fb76d4ae0fe65b00139cb5500d32b8a6adc56323058b32e 95367 isc-dhcp_4.2.4-6.debian.tar.gz a2c8cff02bf358256f2deba3162ad584836128b475e89d765b99455a6b6b9f3f 935444 isc-dhcp-server_4.2.4-6_amd64.deb ee132a6bc9ac95a24a1a9709a98fd98f00c7cd5c63bfb4c94c13c416a5b2add5 2581876 isc-dhcp-server-dbg_4.2.4-6_amd64.deb e9d846ccc83e932d47fcdbedaf5a041ab136dc37e8961d6dafdcfe3894ccf3fb 880568 isc-dhcp-server-ldap_4.2.4-6_amd64.deb 9b5803ba3217cfcd89eea886a9ef8f2726fab9893763b6c987ed189b6656 855162 isc-dhcp-common_4.2.4-6_amd64.deb 9362241e84b45a0c067dad6f4130ce173e23c262df702f3be48325850551dc1a 774352 isc-dhcp-dev_4.2.4-6_amd64.deb 09cd34386595a1614ba4a65d22b4a8769e45745978c424ac8dff23c101f23760 793882
Bug#659390: bug#670232
On Sun, Mar 31, 2013 at 08:04:26PM -0400, Antoine Beaupré wrote: Hi Ana, and others, I will not have time to process this bug in the next two weeks, feel free to NMU or RM. I looked into it and after populating the database by hand and also fixing manually the initial issue [1]. It doesn't work anyway, the following errors appear: [Mon Apr 01 02:15:47 2013] [error] [client x.x.x.x] PHP Warning: include(bookmarks.tpl.php): failed to open stream: No such file or directory in /usr/share/php/SemanticScuttle/Model/Template.php on line 89 [Mon Apr 01 02:15:47 2013] [error] [client x.x.x.x] PHP Warning: include(): Failed opening 'bookmarks.tpl.php' for inclusion (include_path='/etc/semanticscuttle/templates/default:/etc/semanticscuttle/templates/default:.:/usr/share/php:/usr/share/pear:/usr/share/php/SemanticScuttle/../') in /usr/share/php/SemanticScuttle/Model/Template.php on line 89 I wonder if this package have ever worked (looking at popcorn doesn't look like). At this stage, I prefer looking for a nicer replacement of scuttle/semanticscuttle. I doubt a NMU would have small changes, I would go with removing semanticscuttle from Wheezy. Ana [1] what's missing is: cp /usr/share/semanticscuttle/data/config.default.php /etc/semanticscuttle -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704257: marked as done (missing dependency)
Your message dated Mon, 1 Apr 2013 02:52:12 +0200 with message-id 20130401025212.08c6e...@fornost.bigon.be and subject line Re: missing dependency has caused the Debian Bug report #704257, regarding missing dependency to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704257: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: empathy Version: 3.4.2.3-2 Severity: serious Refuses to run If started from a shell, displays an error in the console about missing GLX support Looking at /var/log/Xorg.0.log, I notice that GLX is indeed not working: [ 30101.482] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: cannot open shared object file: No such file or directory) # apt-get install libgl1-mesa-dri resolved the issue, so maybe that is an essential dependency. This problem was experienced on a host upgraded from squeeze to wheezy a few days ago. ---End Message--- ---BeginMessage--- Hello, Thanks for your bug report. libgl1-mesa-dri is not required directly by empathy. It's needed by some other component lower in the stack (mesa?). xorg, xserver-xorg and xserver-xorg-core are already depending/recommending libgl1-mesa-dri so it should be installed by default on the system. I'm closing this bugreport. Cheers Laurent Bigonville---End Message---
Bug#634560: marked as done (r-cran-rjags: FTBFS: configure: error: JAGS module directory /usr/lib/JAGS/modules-2.2.0 does not exist.)
Your message dated Sun, 31 Mar 2013 21:10:00 -0400 with message-id 20130401010959.ga3...@lordsutch.dyndns.org and subject line Fixed quite a while ago has caused the Debian Bug report #634560, regarding r-cran-rjags: FTBFS: configure: error: JAGS module directory /usr/lib/JAGS/modules-2.2.0 does not exist. to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 634560: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: r-cran-rjags Version: 2.2.0-4-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20110718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: fakeroot debian/rules binary /usr/share/cdbs/1/rules/simple-patchsys.mk:31: WARNING: simple-patchsys.mk is deprecated - please use source format 3.0 (quilt) instead test -x debian/rules dh_testroot dh_prep dh_installdirs -A mkdir -p . dh_installdirsusr/lib/R/site-library if test -f /usr/bin/xvfb-run; then\ xvfb-run -a\ R CMD INSTALL -l /build/r-cran-rjags-f2JXEp/r-cran-rjags-2.2.0-4/debian/r-cran-rjags/usr/lib/R/site-library --clean \ . ;\ else\ R CMD INSTALL -l /build/r-cran-rjags-f2JXEp/r-cran-rjags-2.2.0-4/debian/r-cran-rjags/usr/lib/R/site-library \ --clean . ;\ fi * installing *source* package 'rjags' ... checking for prefix by checking for jags... /usr/bin/jags checking whether the C++ compiler works... yes checking for C++ compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking how to run the C++ preprocessor... g++ -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking Console.h usability... yes checking Console.h presence... yes checking for Console.h... yes checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for jags_version in -ljags... yes configure: error: JAGS module directory /usr/lib/JAGS/modules-2.2.0 does not exist. ERROR: configuration failed for package 'rjags' * removing '/build/r-cran-rjags-f2JXEp/r-cran-rjags-2.2.0-4/debian/r-cran-rjags/usr/lib/R/site-library/rjags' make: *** [R_any_arch] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2011/07/18/r-cran-rjags_2.2.0-4-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Version: 3.3-1 Perusing the buildd logs for various architectures, I can't see any build failures like the one reported here back to at least version 3.3-1. Accordingly I am closing this report, unless it can be replicated again with current version 3.10-1. Chris -- Chris Lawrence lawre...@debian.org - http://blog.lordsutch.com/---End Message---
Bug#704251: marked as done ([fp-compiler] On upgrade, update-alternatives error may occur)
Your message dated Sun, 31 Mar 2013 21:25:50 -0400 with message-id CANTw=MOTTta6RMEuVzfLZL_1eXuBPRe-yB5dKqB=m7azykc...@mail.gmail.com and subject line re: [fp-compiler] On upgrade, update-alternatives error may occur has caused the Debian Bug report #704251, regarding [fp-compiler] On upgrade, update-alternatives error may occur to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704251: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fp-compiler Version: 2.6.0-7 Severity: serious This bug is identified by code review while fixing the same issue on Lazarus. For more details please refer to bug#698385 and bug#696075. signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- I upgraded squeeze-wheezy with fp-compiler in a clean chroot, and it worked fine. Closing the bug since there is far too little information here to do anything. Please reopen if you can provide logs showing exactly what you're doing and what went wrong. Best wishes, Mike---End Message---
Bug#703468: linux-image-3.2.0-4-amd64 fails to boot on apple iMac
The following string is still recognizable: i915_gem_init_ppgtt+0x93/0x16c [i915] This is going to take some work on your end to get fixed. 3.2.39-1 included backported patches from aspects of the i915 driver. To help, you could do some testing by unapplying those patches and rebuilding the kernel package to figure out which one is causing your crash. You can find what has changed between 3.2.35 and 3.2.39 by using debdiff from the devscripts package, and the patches that you'll want to unapply will be in debian/patches. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [3.2.35-2 - 3.2.39-1 regression] fails to boot on apple iMac
Processing commands for cont...@bugs.debian.org: found 703468 linux/3.2.41-2 Bug #703468 [src:linux] linux-image-3.2.0-4-amd64 fails to boot on apple iMac Marked as found in versions linux/3.2.41-2. quit Stopping processing here. Please contact me if you need assistance. -- 703468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703468: [3.2.35-2 - 3.2.39-1 regression] fails to boot on apple iMac
found 703468 linux/3.2.41-2 quit Jonathan Nieder wrote: I think a good place to start would be to try 3.2.41-2 from unstable, since it includes some i915 fixes. Ah, looking back over the log I see that's been tried. So: A good next step would be to try 3.8.y from experimental. If it works, we can try to find what is missing in the 3.4.y driver backport. If it doesn't work, we can get help from upstream. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703468: [3.2.35-2 - 3.2.39-1 regression] fails to boot on apple iMac
Hi, Michael Gilbert wrote: The following string is still recognizable: i915_gem_init_ppgtt+0x93/0x16c [i915] This is going to take some work on your end to get fixed. 3.2.39-1 included backported patches from aspects of the i915 driver. I think a good place to start would be to try 3.2.41-2 from unstable, since it includes some i915 fixes. A good next step would be to try 3.8.y from experimental. If it works, we can try to find what is missing in the 3.4.y driver backport. If it doesn't work, we can get help from upstream. [...] You can find what has changed between 3.2.35 and 3.2.39 by using debdiff from the devscripts package Unfortunately that range includes a pretty major change: * Backport drm and agp subsystems from Linux 3.4.29 (closes: #687442) Hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#703239: The failure to properly resize the window automatically is caused by, installation resetting this auto-resize feature
I would like to report that auto-resizing of root window now works as expected after tweaking the setting of virtualbox. I found out that the X11 root window did not resize automatically when the virtualbox window on the host (XP) changed its size because it seems that the setting for auto-resize was cleared during the installation process somewhere. After I toggled auto-resize (view- automatic resize of guest OS window [I don't know the exact English message since I used Japanese version of Windows] (host+G), all is well. I have not realized that this setting is a toggle switch. I have not touched it for a very long time. So this was not a problem of debian package, virtualbox, etc. Also, I notice that there is a patched ISO now, thank you. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 697619
Processing commands for cont...@bugs.debian.org: tags 697619 + patch Bug #697619 [initramfs-tools] Many HID drivers not included in initramfs Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. -- 697619: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: linux-image-3.2.0-4-amd64 fails to boot on apple iMac
Processing commands for cont...@bugs.debian.org: # boot failure, hardware-specific, regression severity 703468 important Bug #703468 [src:linux] linux-image-3.2.0-4-amd64 fails to boot on apple iMac Severity set to 'important' from 'grave' End of message, stopping processing here. Please contact me if you need assistance. -- 703468: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703468 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: 703146 affects pbuilder
Processing commands for cont...@bugs.debian.org:
affects 703146 pbuilder
Bug #703146 {Done: Christian Perrier bubu...@debian.org} [debootstrap] apt:
BADSIG AED4B06F473041FA Debian Archive Automatic Signing Key (6.0/squeeze)?
Bug #704190 {Done: Christian Perrier bubu...@debian.org} [debootstrap]
ltsp-build-client fails because of apt GPG error
Added indication that 703146 affects pbuilder
Added indication that 704190 affects pbuilder
thanks
Stopping processing here.
Please contact me if you need assistance.
--
703146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703146
704190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
