Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
Hi, > Try this: > > https://snapshot.debian.org/binary/firehol/ Thanks for the pointer. I run Approx, so I have the history of packages here anyway. The issue is whether I have to delve into it for manual installation, or whether the Debian Sid package can be rescinded. I suspect not, I think Debian is "the only direction is forward" which is fair enough. It sounds like usrmerge is becoming a Debian standard, so I might try it on that one machine. signature.asc Description: This is a digitally signed message part
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
> It does not look as a solution anyway. > And the issue does not seem to be a FireHOL issue. > I guess that we have to stick to package 3.1.6+ds-4 for a while. I've held all but one machine on 3.1.6+ds-4 but now need to revert the one test machine. Aptitude is telling me there is only 3.1.6+ds-5. Can this version be removed from the repository and 3.1.6+ds-4 reinstated, or do I just have to manually grab the packages and install them? signature.asc Description: This is a digitally signed message part
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
> Package: usrmerge > Description-en: Convert the system to the merged /usr directories scheme That seems like the beastie, and it is a once and for all time thing it seems. I have not installed this. At least not as yet. I am hesitant to do this as it is clearly not Debian Sid standard and it is not reversible. signature.asc Description: This is a digitally signed message part
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
Hi, I found this: https://www.theregister.co.uk/2016/11/24/debian_testing_merged_codeusrcode/ but if it is standard in Debian Sid, I clearly do not have it switched on. signature.asc Description: This is a digitally signed message part
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
> Can you get te version og the ffirehol package ? |> dpkg -l *firehol* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=---= iF firehol 3.1.6+ds-5 all easy to use but powerful iptables stateful firewall (program) ii firehol-common3.1.6+ds-5 all easy to use but powerful traffic suite (common library) ii firehol-doc 3.1.6+ds-5 all easy to use but powerful iptables stateful firewall (docs) un firehol-tools (no description available) ii firehol-tools-doc 3.1.6+ds-5 all easy to use but powerful traffic suite (extra tools docs) signature.asc Description: This is a digitally signed message part
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
Hi, > No assumption, everything is configured with configure.ac I was hoping it was generated rather than manual! :-) > I rebuilt the package in schroot environment , and the path for mktemp is > correct. > > Can you determine from which package version the faulty install.config come > from ? > |> dpkg -S /usr/lib/firehol/install.config firehol-common: /usr/lib/firehol/install.config |> dpkg -S /bin/mktemp coreutils: /bin/mktemp signature.asc Description: This is a digitally signed message part
Bug#913552: firehol: Firehol upgrade 3.1.6+ds-4 to 3.1.6+ds-5 leaves firehol broken
Hi, > It looks weird. > > Is MKTEMP_CMD defined as expected in /usr/lib/firehol/install.config ? > |> grep -i mktemp /usr/lib/firehol/install.config MKTEMP_CMD="/usr/bin/mktemp" I think the file assumes everything that isn't in /usr/sbin is in /usr/bin, but Debian has mktemp in /bin not /usr/bin. signature.asc Description: This is a digitally signed message part
Bug#815404: Acknowledgement (linux-image-4.4.0-1-amd64 fails to boot on Lenovo X1 Carbon)
I just upgraded and got the kernel 4.4.2-3 (2016-02-21) which seems to boot fine. Thanks for dealing with this very quickly, it is much appreciated. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Bug#813339: isc-dhcp-server: Update to 4.3.3-7 today makes isc-dhcp-server unable to work
On Sun, 31 Jan 2016 21:33:35 +0100 Sven Hartge <s...@svenhartge.de> wrote: […] > > The variable to define which interface the dhcpd runs on has changed, > but unfortunately the contents of /etc/default/isc-dhcp-server were not > adapted at the same time. > > You need to change > > INTERFACES="..." > > to > > INTERFACESv4="..." > > to be able to start the DHCP server again. > > And I guess this bug is not just important but of severity "grave". I tried: INTERFACESv4="" on the assumption of interface discovery as used to happen, but this didn't work. INTERFACESv4="eth0" does however work fine. I have a DHCP server again. :-) Thanks for pointing me to the solution, and quickly, it is very much appreciated. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Bug#793630: groovy 1.8.6 and libcommons-cli-java 1.3.1 FTBFS
Emmanuel, Miguel, On Wed, 2015-07-29 at 09:57 +0200, Emmanuel Bourg wrote: Le 29/07/2015 03:35, Miguel Landaeta a écrit : Since you have worked upstream with libcommons-cli-java, I hope to don't bother you with this help request. commons-cli provides several parsers with different behaviors. Up to 1.2 there was a gnu and a posix parsers, and starting with 1.3 I introduced a new unified parser (DefaultParser). You may try using it, it's just a matter of changing the instantiation and it's likely to work better. As far as I am aware, the Apache Groovy source explicitly imports and uses the GnuParser – even now despite it being deprecated – as part of the CliBuilder class. All other uses of org.apache.commons.cli in the Apache Groovy source use DefaultParser. If I remember correctly, DefaultParser, which is PosixParser I believe, enforces bursting of single hyphen options, which is fine for the Groovy command line, but not sufficiently flexible for the CliBuilder. The Java Way is for a version of something, in this case Groovy 1.8.6 to retain its original dependency, in this case Commons CLI 1.2.x, rather than have the dependencies altered without a new release – most people get their dependencies from JCenter or Maven Central via Gradle or Maven. Apache Groovy 1.x series is no longer maintained. All effort is now on the Apache Groovy 2.4.x and 2.5-SNAPSHOT versions. If Debian is to remove Commons CLI 1.2 then I suggest removing the groovy package since the groovy2 package is in place already, and is the right version for Debian to go with. Unless I am missing something. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Bug#762755: Bug#762805: bind 9 crash / assertion failure
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mike, I upgraded to bind9 1:9.9.5.dfsg-4.2 (and all the associated packages) this morning and no more immediate crashing problem, the same process has now been running for 6 hours :-) Thanks for getting the fix into Debian Sid quickly. - -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlQ5TCEACgkQ+ooS3F10Be/gbACg93sfbc/w+QVWdkP7/eQjSYd6 Le8AoMH8QCc/PN1LfSstYQTE2c4c4DVN =31oS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#725711: whyteboard: import wx.media - ImportError: No module named media
This problem remains in Debian Unstable. It seems the Ubuntu folk have solved it, but Debian folk have not. If there is a problem with the packaging then put the wx.media stuff in a separate package and allow whyteboard to depend on that? -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#728562: libgpars-groovy-java, groovy: error when trying to install together: overwriting /usr/share/groovy/lib/gpars.jar
Andreas, On Sun, 2013-11-03 at 02:34 +0100, Andreas Beckmann wrote: Package: libgpars-groovy-java,groovy Version: 2.1.6+dfsg-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Architecture: amd64 Distribution: sid + experimental Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preparing to replace groovy 1.8.6-1 (using .../groovy_2.1.6+dfsg-1_all.deb) ... Unpacking replacement groovy ... dpkg: error processing /var/cache/apt/archives/groovy_2.1.6+dfsg-1_all.deb (--unpack): trying to overwrite '/usr/share/groovy/lib/gpars.jar', which is also in package libgpars-groovy-java 0.10-1 This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Whilst this may a priori be a failure of the Debian packaging rules, the situation stems from the fact that GPars used to be a totally separate thing from Groovy, but now the Groovy distribution includes and relies on GPars even though it is has a separate development line. I argue that the Debian package strategy may well be the underlying problem here because it does not allow multiple versions of artefacts as is standard practice in the JVM-verse. Whilst libgpars-groovy-java used to be a good idea, the gpars artefact should be an integral part of the groovy package from Groovy 2.0 onwards. Also worth noting that GPars 0.10 is ancient, we are now at 1.1 and wondering when to release 1.2. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/share/groovy/lib/gpars.jar This raises the issue of why Debian has a single unnumbered artefact when the Java universe works with numbered artefacts so that different versions can be used in the same system. In particular, in order to have Gradle 1.x installed, Groovy 1.8.x must be installed, which means Groovy 2.1.x cannot be installed unless Gradle is removed. There is a viscous circle here leading to Debian being unable to support the Groovy infrastructure. Debian really needs to change it's Java and Groovy policies to enable multiple versions of artefacts. To be honest the current situation means most people ignore the Debian packaging system for Java and Groovy (and indeed Scala, Ceylon, Kotlin, Clojure, etc.) and use the language specific installations. For Groovy this means using GVM, which is a Bash based package installer which just requires some Java install at JAVA_HOME. Most people use the Oracle distribution, particularly those of us using Java 8 – which cannot be packaged by Debian for Unstable for sensible reasons. This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669715: dvb-apps: Channel/frequency/etc. data needs updating for London transmitters
Package: dvb-apps Version: 1.1.1+rev1457-4 Severity: critical Tags: upstream Justification: breaks unrelated software Dear Maintainer, The digital switch over (DSO) -- closing of analogue television transmision -- has involved quite a convoluted rearrangement of the multiplexes and channels. The DSO completed for London, and in my case Crystal Palace, 2012-04-18. The channel data distributed with dvb-apps is now incorrect. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=str=こんにちわ世界, bytes_read=21, bytes_written=21) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dvb-apps depends on: ii libc6 2.13-30 ii libpng12-0 1.2.49-1 ii libx11-62:1.4.99.901-1 ii libzvbi00.2.33-5 ii udev175-3.1 ii zlib1g 1:1.2.6.dfsg-2 dvb-apps recommends no packages. dvb-apps 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#669718: gnome-dvb-client: gnome-dvb-setup fails to scan uk-CrystalPalace since DSO
Package: gnome-dvb-client Version: 1:0.2.8-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, The digital switch over (DSO) -- closing of analogue television transmision -- has involved quite a convoluted rearrangement of the multiplexes and channels. The DSO completed for London, and in my case Crystal Palace, 2012-04-18. The channel data distributed with dvb-apps is now incorrect, but that is a separate bug report. I calculated the relevant data from the OfCom documents and can see all the SD channels at the calculated frequencies using vlc. I created a variant of the /usr/share/dvb/dvb-t/uk-CrystalPalace datafile, but using this, gnome-dvb-setup failed to find any channels when scanning. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=str=こんにちわ世界, bytes_read=21, bytes_written=21) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gnome-dvb-client depends on: ii gir1.2-gtk-3.03.4.1-2 ii gnome-dvb-daemon 1:0.2.8-1 ii gnome-icon-theme 3.4.0-2 ii python2.7.2-10 ii python-gobject3.2.0-3 ii python2.7 2.7.3~rc2-2 Versions of packages gnome-dvb-client recommends: ii dvb-apps 1.1.1+rev1457-4 gnome-dvb-client 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#669715: dvb-apps: Channel/frequency/etc. data needs updating for London transmitters
The representative of the Amalgamated Union of Philosophers, Sages, Luminaries, and other professional thinking persons quoth: On Sun, 2012-04-22 at 03:16 +0100, Darren Salt wrote: I demand that Russel Winder may or may not have written... The digital switch over (DSO) -- closing of analogue television transmision -- has involved quite a convoluted rearrangement of the multiplexes and channels. The DSO completed for London, and in my case Crystal Palace, 2012-04-18. The channel data distributed with dvb-apps is now incorrect. You should use w_scan to gather the new information. It would be useful if you attach the new tuning information to this bug report. Not sure about w_scan, I have scan. It doesn't generate a channel list. I calculated the following replacement for the uk-CrystalPalace file: # UK, Crystal Palace # # Manually calculated by RLW 2012-04-21T10:20+01:00 # # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy # # BBC A — 23 T 49000 8MHz 2/3 NONE QAM64 2k 1/32 NONE # D34 — 26 T 51400 8MHz 2/3 NONE QAM64 2k 1/32 NONE # BBC B — 30- T 545833000 8MHz 2/3 NONE QAM256 2k 1/32 NONE # SDN — 25 T 50600 8MHz 3/4 NONE QAM64 2k 1/32 NONE # Arqiva A — 22 T 48200 8MHz 3/4 NONE QAM64 2k 1/32 NONE # Arqiva B — 28- # ITV4 T 529833000 8MHz 3/4 NONE QAM64 2k 1/32 NONE The BBC A, D34, SDN, Arqiva A, and Arqiva B frequencies all work fine with vlc, I get all the channels on the multiplex. BBC B seems to fail but I have a suspicion that may be that the TerraTec USB unit I have does not handle HD. I am not sure what the NONE entries are, and I am not sure if the 1/32 is correct. All other entries come straight from the OfCom document -- which I assume is definitive. Running scan I get: | scan uk-CrystalPalace_RLW scanning uk-CrystalPalace_RLW using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' initial transponder 49000 0 2 9 3 0 0 0 initial transponder 51400 0 2 9 3 0 0 0 initial transponder 545833000 0 2 9 5 0 0 0 initial transponder 50600 0 3 9 3 0 0 0 initial transponder 48200 0 3 9 3 0 0 0 initial transponder 529833000 0 3 9 3 0 0 0 tune to: 49000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 49000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 51400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 51400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 545833000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_256:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 545833000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_256:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 48200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 48200:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! tune to: 529833000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE WARNING: tuning failed!!! tune to: 529833000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed) WARNING: tuning failed!!! ERROR: initial tuning failed dumping lists (0 services) Done. Also, as of 26 September, it'll also be incorrect for Pontop Pike... Is that the last to go? -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@winder.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Bug#661253: nvidia-glx: NVIDIA 295.20 causes random and unexpected X termination and hence logout
Andreas, On Wed, 2012-02-29 at 15:21 +0100, Andreas Beckmann wrote: [...] did you have a look at the nvidia forum to see whether this probelm has been reported there? http://www.nvnews.net/vbulletin/forumdisplay.php?f=14order=desc There is also an issue with 295.20 segfaulting in libnvidia-tls: http://bugs.debian.org/660189 - does this math your problem? I had not checked with the forum. I am not really a forum type person don't go to them unless pushed...I'll see if I can do a search for something this weekend. Immediate reaction to the above is that I do use Chrome but not Chromium. Russel, can you confirm that the machine becomes unresponsive after this crash? Or can you just relogin and continue to work? For me X just dies and then GDM3 kicks in and shows a login screen. The machine is generally fine as far as I can tell. I upgraded this morning after a few days gap and there was a new kernel so I tried the machine again. Sadly there was a X termination fail so I have stopped using that machine until there is another kernel or NVIDIA driver update. [...] -- Russel. = Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.win...@ekiga.net 41 Buckmaster Roadm: +44 7770 465 077 xmpp: rus...@russel.org.uk London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder signature.asc Description: This is a digitally signed message part
Bug#631289: iwlagn: Kernel 2.6.39-2-amd64 in Debian Testing causes Lenovo X201 and T500 wifi to crash Netgear DGN3500 ADSL router/Wifi access point
Package: linux-2.6 Version: 2.6.39-2 Severity: grave File: iwlagn Justification: renders package unusable I am running Debian Testing generally updated each morning. Kernel 2.6.38-2-amd64 was working fine with my configuration of Lenovo X201 and T500 laptops connecting to my Netgear DGN3500 ADSL router/wifi access point. On upgrading to kernel 2.6.39-2-amd64 the other day, I find that any use of wifi with the laptops causes the router to crash unrecoverably within about 2mins. The wifi works for a short while and then the router just stops, including the control page accessed via separate computer connected via wired Ethernet, so the Netgear crash is total requiring a power cycle. I have tested as much as I can but there appears no way of obtaining any useful debug information from the Netgear, at least with my current state of knowledge. The laptops just see a wifi connection termination, and the workstation monitoring the router status page just sees an HTTP connection termination. -- Package-specific info: ** Version: Linux version 2.6.39-2-amd64 (Debian 2.6.39-2) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Wed Jun 8 11:01:04 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.39-2-amd64 root=UUID=27d9c2a7-aa99-4bab-9ebf-029425ff40d6 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [26902.816232] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b7, writing 0x2b00407) [26902.816303] intel ips :00:1f.6: restoring config space at offset 0xf (was 0x400, writing 0x40b) [26902.816326] intel ips :00:1f.6: restoring config space at offset 0x1 (was 0x10, writing 0x12) [26902.816411] iwlagn :02:00.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100506) [26902.816543] PM: early resume of devices complete after 28.720 msecs [26902.816725] i915 :00:02.0: power state changed by ACPI to D0 [26902.816781] pci :00:1e.0: setting latency timer to 64 [26902.816790] e1000e :00:19.0: wake-up capability disabled by ACPI [26902.816797] e1000e :00:19.0: PME# disabled [26902.816828] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [26902.816854] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [26902.816867] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [26902.816871] i915 :00:02.0: power state changed by ACPI to D0 [26902.816875] HDA Intel :00:1b.0: setting latency timer to 64 [26902.816884] i915 :00:02.0: setting latency timer to 64 [26902.816940] HDA Intel :00:1b.0: irq 40 for MSI/MSI-X [26902.823805] ahci :00:1f.2: setting latency timer to 64 [26902.823903] e1000e :00:19.0: irq 44 for MSI/MSI-X [26902.823932] sd 0:0:0:0: [sda] Starting disk [26902.823992] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [26902.823999] ehci_hcd :00:1a.0: PCI INT D - GSI 23 (level, low) - IRQ 23 [26902.824005] ehci_hcd :00:1a.0: setting latency timer to 64 [26902.824052] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [26902.824061] ehci_hcd :00:1d.0: PCI INT D - GSI 19 (level, low) - IRQ 19 [26902.824067] ehci_hcd :00:1d.0: setting latency timer to 64 [26902.826498] thinkpad_acpi: EC reports that Thermal Table has changed [26903.075440] usb 1-1.3: reset full speed USB device number 3 using ehci_hcd [26903.151047] ata5: SATA link down (SStatus 0 SControl 300) [26903.159010] ata2: SATA link down (SStatus 0 SControl 300) [26903.167024] ata6: SATA link down (SStatus 0 SControl 300) [26903.426497] usb 1-1.1: reset low speed USB device number 8 using ehci_hcd [26903.777651] usb 1-1.6: reset high speed USB device number 5 using ehci_hcd [26904.707095] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [26904.959932] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [26904.959938] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [26904.959942] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [26904.963943] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [26904.963949] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [26904.963953] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [26904.965712] ata1.00: configured for UDMA/100 [26905.006974] PM: resume of devices complete after 2195.935 msecs [26905.007034] PM: Finishing wakeup. [26905.007035] Restarting tasks ... done. [26905.014716] video LNXVIDEO:00: Restoring backlight state [26905.353699] e1000e :00:19.0: irq 44 for MSI/MSI-X [26905.409319] e1000e :00:19.0: irq 44 for MSI/MSI-X [26905.409669] ADDRCONF(NETDEV_UP): eth0: link is not ready [26905.506710] ADDRCONF(NETDEV_UP): wlan0: link is not ready [26906.087919] usb 1-1.4: new full speed USB device number 9 using ehci_hcd [26906.183820] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=217f [26906.183825] usb 1-1.4: New USB device strings: Mfr=1, Product=2,
Bug#335512: courier-imap-ssl: 2004-10-24 Testing update causes imap ssl to cease working
On Mon, 2005-10-24 at 20:42 +0200, Stefan Hornburg wrote: This in fact a problem with courier-ssl, already reported. Presumably it is caused by libssl0.9.7 / libssl0.9.8 transition. Bye Racke On Mon, 2005-10-24 at 15:41 -0700, Steve Langasek wrote: Yes, this error has been reported against several other packages already, and appears to be a regression in libssl0.9.8. Apologies for not catching this before it reached testing. There were so many related changes in yesterday's update of testing it was hard to know where to start with thinking about the problem! It is good in a sense that other packages have the problem so it is clearly the libssl upgrade that is at the heart of it. It means that there may be nothing at all wrong with Courier. A lot of people use Testing far fewer use Unstable so some things will only get caught on the move to Testing -- that's why it is Testing! However, I do have to admit that this one is rather surprising not to have been caught in Unstable. Hopefully the libssl people will find the problem quickly. At least they know it is in the 0.9.7 - 0.9.8 change. Thanks for the prompt responses. This is much appreciated. And thanks for all your efforts on making Debian so easy to work with. -- Russel. Dr Russel Winder+44 20 7585 2200 41 Buckmaster Road +44 7770 465 077 London SW11 1EN, UK [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Bug#335512: courier-imap-ssl: 2004-10-24 Testing update causes imap ssl to cease working
Package: courier-imap-ssl Version: 3.0.8-11 Severity: grave Justification: renders package unusable I run Debian GNU/Linux Testing. My courier IMAP SSL system was working fine. I upgraded this morning 2005-10-24 and now for every attempted connection, I get: Oct 24 12:26:44 dimen imapd-ssl: couriertls: /etc/courier/imapd.pem: error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library I am hoping that this is just a dependency problem relating to the upgrade of libssl but... In any event it completely stops the installation working. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Versions of packages courier-imap-ssl depends on: ii courier-imap 3.0.8-11 Courier Mail Server - IMAP server ii courier-ssl 0.47-11Courier Mail Server - SSL/TLS Supp ii openssl 0.9.8a-2 Secure Socket Layer (SSL) binary a courier-imap-ssl recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
