Bug#723050: can't log in

2013-09-20 Thread spikethehobbitmage.excite
I see you also pulled in the libc and pam updates.  During the libc upgrade 
there should have been a dialog requesting service restarts for ssh and cupsd 
as the upgrade breaks authentication.  The wall of text explaining the upgrade 
should have stated that X (and therefore kdm) needs to be restarted manually 
after the upgrade, as restarting X logs out any active sessions and would 
therefore kill the upgrade.  ssh works because it can be restarted safely.

This happens every time libc and pam are updated and is due to a limitation in 
pam.

TLDR;  Any time you upgrade libc or pam, you /must/ log out and restart kdm.

/not maintainer


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#708049: Can't install

2013-06-21 Thread spikethehobbitmage.excite
I'm not the original submitter, but I'm having what appears to be the same 
problem.
I did not get a 'gdbm fatal' message.
I do not have libnss-mysql* installed.
I believe this is a clean install of mysql, but I can't guarantee that old 
files may be present from an ancient install.

# ls -l /var/log/mysql*
-rw-r- 1 mysql adm0 Jun 21 01:31 /var/log/mysql.err
-rw-r- 1 mysql adm0 Jun 21 01:31 /var/log/mysql.log

/var/log/mysql:
total 0

nothing in dmesg

/var/log/debug contained
/etc/init.d/mysql[31956]: 0 processes alive and '/usr/bin/mysqladmin 
--defaults-file=/etc/mysql/debian.cnf ping' resulted in
/etc/init.d/mysql[31956]: ^G/usr/bin/mysqladmin: connect to server at 
'localhost' failed
/etc/init.d/mysql[31956]: error: 'Can't connect to local MySQL server through 
socket '/var/run/mysqld/mysqld.sock' (2)'
/etc/init.d/mysql[31956]: Check that mysqld is running and that the socket: 
'/var/run/mysqld/mysqld.sock' exists!

# su mysql
# mysqld

130621  1:36:01 [Note] Plugin 'FEDERATED' is disabled.
130621  1:36:01 InnoDB: The InnoDB memory heap is disabled
130621  1:36:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130621  1:36:01 InnoDB: Compressed tables use zlib 1.2.7
130621  1:36:01 InnoDB: Using Linux native AIO
130621  1:36:01 InnoDB: Initializing buffer pool, size = 128.0M
130621  1:36:01 InnoDB: Completed initialization of buffer pool
130621  1:36:01 InnoDB: highest supported file format is Barracuda.
130621  1:36:02  InnoDB: Error: trying to access tablespace 1 page no. 2,
InnoDB: but the tablespace does not exist or is just being dropped.
..repeated many times..
130621  1:36:02  InnoDB: Error: trying to access tablespace 1 page no. 2,
InnoDB: but the tablespace does not exist or is just being dropped.
InnoDB: Error: Unable to read tablespace 1 page no 2 into the buffer pool after 
100 attempts
InnoDB: The most probable cause of this error may be that the table has been 
corrupted.
InnoDB: You can try to fix this problem by using innodb_force_recovery.
InnoDB: Please see reference manual for more details.
InnoDB: Aborting...
130621  1:36:02  InnoDB: Assertion failure in thread 140655213950784 in file 
buf0buf.c line 2346
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:36:02 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
thread_count=0
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346682 K  
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x3
mysqld(my_print_stacktrace+0x29)[0x7fecd8678569]
mysqld(handle_fatal_signal+0x3d8)[0x7fecd8560748]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf210)[0x7fecd7d10210]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7fecd6505295]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fecd6508438]
mysqld(+0x5b73b4)[0x7fecd86f83b4]
mysqld(+0x5f0d83)[0x7fecd8731d83]
mysqld(+0x58932e)[0x7fecd86ca32e]
mysqld(+0x589a6b)[0x7fecd86caa6b]
mysqld(+0x58c50e)[0x7fecd86cd50e]
mysqld(+0x578e40)[0x7fecd86b9e40]
mysqld(+0x54543f)[0x7fecd868643f]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fecd8562ad1]
mysqld(+0x330e31)[0x7fecd8471e31]
mysqld(_Z11plugin_initPiPPci+0xa43)[0x7fecd8473dc3]
mysqld(+0x2b3f85)[0x7fecd83f4f85]
mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fecd83f9d4b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fecd64f1a55]
mysqld(+0x2b0199)[0x7fecd83f1199]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#708049: mysql doesn't like old tables

2013-06-21 Thread spikethehobbitmage.excite
It seems I did have some old mysql files floating around from several years 
ago.  Moving them out of the way and reconfiguring produced this:

Setting up mysql-server-5.5 (5.5.31+dfsg-1) ... 
[ ok ] Stopping MySQL database server: mysqld.  
130621  1:54:08 [Note] Plugin 'FEDERATED' is disabled.  
130621  1:54:08 InnoDB: The InnoDB memory heap is disabled
130621  1:54:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130621  1:54:08 InnoDB: Compressed tables use zlib 1.2.7
130621  1:54:08 InnoDB: Using Linux native AIO
130621  1:54:08 InnoDB: Initializing buffer pool, size = 128.0M
130621  1:54:08 InnoDB: Completed initialization of buffer pool
130621  1:54:09 InnoDB: highest supported file format is Barracuda.
130621  1:54:09  InnoDB: Waiting for the background threads to start
130621  1:54:10 InnoDB: 5.5.31 started; log sequence number 1595675
130621  1:54:10  InnoDB: Starting shutdown...
130621  1:54:11  InnoDB: Shutdown completed; log sequence number 1595675
[ ok ] Starting MySQL database server: mysqld ..
[info] Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly..
Setting up mysql-server (5.5.31+dfsg-1) ...


# /etc/inid.d stop
[ ok ] Stopping MySQL database server: mysqld.

# /etc/inid.d start
[ ok ] Starting MySQL database server: mysqld ..
[info] Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly..

Some of those old tables date back to 2005.  I even see a debian-4.1.flag file, 
and that isn't the oldest.  The newest files date to 2010.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#708049: mysql doesn't like old tables

2013-06-21 Thread spikethehobbitmage.excite
It seems I did have some old mysql files floating around from several years 
ago.  Moving them out of the way and reconfiguring produced this:

Setting up mysql-server-5.5 (5.5.31+dfsg-1) ... 
[ ok ] Stopping MySQL database server: mysqld.  
130621  1:54:08 [Note] Plugin 'FEDERATED' is disabled.  
130621  1:54:08 InnoDB: The InnoDB memory heap is disabled
130621  1:54:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
130621  1:54:08 InnoDB: Compressed tables use zlib 1.2.7
130621  1:54:08 InnoDB: Using Linux native AIO
130621  1:54:08 InnoDB: Initializing buffer pool, size = 128.0M
130621  1:54:08 InnoDB: Completed initialization of buffer pool
130621  1:54:09 InnoDB: highest supported file format is Barracuda.
130621  1:54:09  InnoDB: Waiting for the background threads to start
130621  1:54:10 InnoDB: 5.5.31 started; log sequence number 1595675
130621  1:54:10  InnoDB: Starting shutdown...
130621  1:54:11  InnoDB: Shutdown completed; log sequence number 1595675
[ ok ] Starting MySQL database server: mysqld ..
[info] Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly..
Setting up mysql-server (5.5.31+dfsg-1) ...


# /etc/inid.d stop
[ ok ] Stopping MySQL database server: mysqld.

# /etc/inid.d start
[ ok ] Starting MySQL database server: mysqld ..
[info] Checking for tables which need an upgrade, are corrupt or were 
not closed cleanly..

Some of those old tables date back to 2005.  I even see a debian-4.1.flag file, 
and that isn't the oldest.  The newest files date to 2010.


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#605870: pdnsd: crashes on heavy load

2013-06-12 Thread spikethehobbitmage.excite
I can reproduce this.  pdnsd isn't actually crashing, but it does effectively 
stop serving requests.  If I set the server to 'down', pdnsd quickly starts 
responding again.  Setting the server to 'up' again stops DNS again.

If the queue time exceeds the client timeout limit, the client can no longer 
resolve names, even if pdnsd is responding.  If upstream silently drops 
requests, queue time becomes ~2 min minimum.  Some routers also add a 2 min 
delay to all DNS requests when loaded.  Client timeout seems to be around 5 
seconds for most programs, with 3 attempts made, so 15 seconds max.

There are 3 factors involved.
1) All requests must pass the queue before the cache is checked.  This is a 
bug, and the main problem.
2) pdnsd cannot have a server timeout longer than its client timeout, but most 
clients only listen for about 5 seconds, while servers can take  120s to reply 
under load.  Some routers are especially bad for this.
3) pdnsd does not merge duplicate requests.  A bug in and of itself, and it 
compounds the problem by making 1 and 2 worse.

What needs to be done:
1) If a fresh cache entry is available, pdnsd should respond immediately, even 
if there is a queue, and even if the queue is full.  That is, the queue should 
only be used for cache misses and stale entries.
2) It should be possible to set the client timeout shorter than the server 
timeout.  In particular, pdnsd should be able to send a stale record, or even 
SERVFAIL while still listening for a reply from upstream, or even if the 
request is in queue.  That is, the client timeout clock should start when a 
request is received, but the server timeout should not start until a request is 
sent.  There are 3 situations that could have different timeouts:
2a) On a cache miss, pdnsd could time out the client and reply SERVFAIL before 
the server connection times out.  If enabled, this should even time out while 
the request is in queue.  If the request was in queue, it should be queued at 
low priority, or dropped. eg: client timeout could be 110s, while server 
timeout is 150s.
2b)  On a stale cache entry, but no queue, it should be possible to set the 
client timeout shorter than the server timeout.  That is, pdnsd would reply 
from stale cache while still listening for the server response.  eg:  Reply 
from stale cache in 4 sec, but still listen 150 sec for the server to respond.
2c) On a stale cache entry and a queue, it should be possible to tell pdnsd to 
reply from cache instantly, and queue the name at low priority, or drop it.
3) If a request comes in for a name that is already active, or in the queue, 
pdnsd should only send one request upstream, and then give the reply to all 
requesters.  pdnsd should handle its own retries, as long as any client is 
waiting for the name.  If all clients timed out while a request is in queue, it 
should be handled at lower priority, or even dropped.

My setup:
My ISP uses some really flakey DNS servers that often silently drop ~50% of 
requests.  Some servers are better than others.
I'm also using a Linksys router that suffers from DNS loading issues.  When 
overloaded, its response time exceeds 120 seconds, and it starts silently 
dropping requests too.  This happens every time upstream acts up, as the router 
starts queuing.
I have pdnsd on each machine on my network.  They all exhibit this problem.


Package: pdnsd
Version: 1.2.9a-par-1

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-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 pdnsd depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.50
ii  libc6  2.17-3

Versions of packages pdnsd recommends:
pn  resolvconf  none

pdnsd suggests no packages.

global {
perm_cache=2048;
cache_dir=/var/cache/pdnsd;
run_as=pdnsd;
server_ip = 127.0.0.1;  // Use eth0 here if you want to allow other
// machines on your network to query pdnsd.
status_ctl = on;
paranoid=on;
min_ttl=3600;   // Retain cached entries at least 1 hour.
max_ttl=2419200;// One month.
timeout=10; // Global timeout option (10 seconds).
}

server {
label=router;
ip=192.168.1.1;
interface=eth0;
purge_cache=off;
timeout=150;
}

source {
owner=localhost;
file=/etc/hosts;
}


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#697495: libqt4-script: segfault in multiple programs

2013-01-05 Thread spikethehobbitmage.excite
Package: libqt4-script
Version: 4:4.8.2+dfsg-2
Severity: normal

After upgrading my system, plasma-desktop and kwrite segfault on startup.  Both 
faults occur in exactly the same place in libqt4-script, so I am assigning here.
Downgrading back to 4:4.8.2+dfsg-2 fixes.

I believe the problem is the huge (2GB) allocation done at this point.  This 
fails on my system, even with 3G swap available, as I have memory overcommit 
disabled.
Is there any way to change this amount or (better) force dynamic allocation?

Attached backtrace from plasma-desktop.


-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-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/bash

Versions of packages libqt4-script depends on:
ii  libc6  2.13-37
ii  libgcc11:4.7.2-4
ii  libqt4-dbus4:4.8.2+dfsg-8
ii  libqtcore4 4:4.8.2+dfsg-8
ii  libstdc++6 4.7.2-4
ii  multiarch-support  2.13-37

libqt4-script recommends no packages.

libqt4-script suggests no packages.

-- no debconf information
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f943b271780 (LWP 7881))]

Thread 2 (Thread 0x7f941f251700 (LWP 7882)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at 
../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x7f9434d7ae77 in QTWTF::TCMalloc_PageHeap::scavengerThread 
(this=0x7f9435088640) at 
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x7f9434d7aea9 in QTWTF::TCMalloc_PageHeap::runScavengerThread 
(context=optimized out) at 
../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x7f942f98ab50 in start_thread (arg=optimized out) at 
pthread_create.c:304
#4  0x7f943ab7fa7d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x in ?? ()

Thread 1 (Thread 0x7f943b271780 (LWP 7881)):
[KCrash Handler]
#6  0x7f9434c97c5e in FixedVMPoolAllocator (totalHeapSize=2147483648, 
commonSize=optimized out, this=0x2613c60) at 
../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:310
#7  QTJSC::ExecutablePool::systemAlloc (size=16384) at 
../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocatorFixedVMPool.cpp:443
#8  0x7f9434d1c629 in ExecutablePool (n=optimized out, 
this=0x7f941e960960) at 
../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:258
#9  create (n=optimized out) at 
../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:97
#10 ExecutableAllocator (this=0x7f941e95a9c8) at 
../3rdparty/javascriptcore/JavaScriptCore/jit/ExecutableAllocator.h:150
#11 QTJSC::JSGlobalData::JSGlobalData (this=0x7f941e959800, isShared=optimized 
out) at ../3rdparty/javascriptcore/JavaScriptCore/runtime/JSGlobalData.cpp:146
#12 0x7f9434d1cdec in QTJSC::JSGlobalData::create () at 
../3rdparty/javascriptcore/JavaScriptCore/runtime/JSGlobalData.cpp:205
#13 0x7f9434dbd380 in QScriptEnginePrivate::QScriptEnginePrivate 
(this=0x2614740) at api/qscriptengine.cpp:979
#14 0x7f9434dbe2fe in QScriptEngine::QScriptEngine (this=0x7fff81442430, 
parent=0x0) at api/qscriptengine.cpp:1976
#15 0x7f9439857d9a in 
WorkspaceScripting::ScriptEngine::ScriptEngine(Plasma::Corona*, QObject*) () 
from /usr/lib/libplasmagenericshell.so.4
#16 0x7f943ae61abb in ?? () from 
/usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#17 0x7f943ae69173 in ?? () from 
/usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#18 0x7f943ae69531 in ?? () from 
/usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#19 0x7f943a6be6dc in Plasma::Corona::initializeLayout (this=0x25a5cc0, 
configName=...) at ../../plasma/corona.cpp:184
#20 0x7f943ae89ea3 in ?? () from 
/usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#21 0x7f943ae8a1ed in ?? () from 
/usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#22 0x7f943ae8b67a in ?? () from 
/usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#23 0x7f9437d21a2e in QObject::event (this=0x2483e10, e=optimized out) at 
kernel/qobject.cpp:1195
#24 0x7f94370b8814 in QApplication::event (this=0x2483e10, e=0x25c1c30) at 
kernel/qapplication.cpp:2538
#25 0x7f94370b670c in QApplicationPrivate::notify_helper 
(this=this@entry=0x2488850, receiver=receiver@entry=0x2483e10, 
e=e@entry=0x25c1c30) at kernel/qapplication.cpp:4556
#26 0x7f94370bab8a in QApplication::notify (this=0x2483e10, 
receiver=0x2483e10, e=0x25c1c30) at kernel/qapplication.cpp:4417
#27 0x7f9438a15886 in KApplication::notify (this=0x2483e10, 
receiver=0x2483e10, event=0x25c1c30) at ../../kdeui/kernel/kapplication.cpp:311
#28 0x7f9437d0cb5e in 

Bug#666262: steps to reproduce bug

2012-03-31 Thread spikethehobbitmage.excite
As you say, it isn't clear, and apt seems to be the only program rejecting it.  
In any case empty fields are poor form.  Perhaps this bug should be 
cross-posted against apt as well?

The following script should reproduce the bug.  Total download for the video 
driver should be about 6MB.  WARNING: THIS BREAKS APT.

as root run:
apt-get install reprepro
apt-get build-dep xserver-xorg-video-ati

as a normal user run this script:

#!/bin/bash
git clone git://anongit.freedesktop.org/xorg/driver/xf86-video-ati builddir
pushd builddir
git checkout xf86-video-ati-6.14.4
./autogen.sh  make  fakeroot checkinstall --install=no 
--pkgname=xserver-xorg-video-ati --pkgversion=`git describe | sed 's/.*ati-//'` 
--provides=xorg-driver-video --nodoc --pakdir=.. -y make install
popd
mkdir -p repo/conf
cat  EOF  repo/conf/distributions
Codename: local
Components: main
Architectures: `dpkg-architecture -qDEB_HOST_ARCH`
Description: test archive
EOF
reprepro -b repo includedeb local *deb

as root:
add deb file:/path/to/repo local main to /etc/apt/sources.list
apt-get update
watch apt-get die

Notes:
the bad Packages file will need to be manually removed from /var/lib/apt/lists/ 
before any apt* program will run again:
  rm -- /var/lib/apt/lists/_home_*Packages /var/lib/apt/lists/_home_*Release
the patch could be tightened to:
  cat  EOF | sed s/[ \t]+$// | egrep -v ^[^:]*:$  
$BUILD_DIR/DEBIAN/control



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#666685: Please update to new upstream 4.7.0.2

2012-03-31 Thread spikethehobbitmage.excite
Package: vuze
Version: 4.3.0.6-5
Severity: wishlist
Tags: patch

Vuze 4.3.0.6 is over 2 years out of date.

I am attaching a patch against debian/patches to work with the current version 
of vuze
the file org/eclipse/swt/widgets/Tree2.java from upstream also needs to be 
deleted to build, as it is a Windows specific patch not needed on Linux

tested against
http://sourceforge.net/projects/azureus/files/vuze/Vuze_4702/Vuze_4702_source.zip/download
sha1sum:
59b518117181fe9d6e6b99683addce6ada73e464 *Vuze_4702_source.zip

diff --git a/debian/patches/debian/no-auto-update.patch b/debian/patches/debian/no-auto-update.patch
index c4275fe..35d02b3 100644
--- a/debian/patches/debian/no-auto-update.patch
+++ b/debian/patches/debian/no-auto-update.patch
@@ -5,9 +5,9 @@ Index: azureus/org/gudy/azureus2/core3/config/impl/ConfigurationDefaults.java
 ===
 --- azureus.orig/org/gudy/azureus2/core3/config/impl/ConfigurationDefaults.java	2011-06-07 22:07:05.588553689 +0100
 +++ azureus/org/gudy/azureus2/core3/config/impl/ConfigurationDefaults.java	2011-06-07 22:07:57.567719664 +0100
-@@ -231,9 +231,9 @@
- 		File f = new File(docPath, Azureus Downloads);
- 		def.put(Default save path, f.getAbsolutePath());
+@@ -255,9 +255,9 @@
+ 	
+ 	def.put(Default save path, f.getAbsolutePath());
  
 -def.put(update.start,TRUE);
 -def.put(update.periodic,TRUE);
@@ -18,9 +18,9 @@ Index: azureus/org/gudy/azureus2/core3/config/impl/ConfigurationDefaults.java
  def.put(update.autodownload, FALSE);
  
  def.put(Send Version Info, TRUE);
-@@ -430,7 +430,7 @@
+@@ -451,7 +451,7 @@
+ def.put( locale, Locale.getDefault().toString() );
  def.put( locale.set.complete.count, ZERO);
- def.put( Confirm Data Delete, TRUE );
  def.put( Password Confirm, null );
 -def.put( Auto Update, TRUE );
 +def.put( Auto Update, FALSE );
diff --git a/debian/patches/debian/update-disable.diff b/debian/patches/debian/update-disable.diff
index cd058e0..8513203 100644
--- a/debian/patches/debian/update-disable.diff
+++ b/debian/patches/debian/update-disable.diff
@@ -17,7 +17,7 @@ diff --git a/com/aelitis/azureus/ui/swt/Initializer.java b/com/aelitis/azureus/u
 index 8a959c4..9069f3d 100644
 --- a/com/aelitis/azureus/ui/swt/Initializer.java
 +++ b/com/aelitis/azureus/ui/swt/Initializer.java
-@@ -44,9 +44,10 @@ import org.gudy.azureus2.ui.swt.networks.SWTNetworkSelection;
+@@ -50,9 +50,10 @@ import org.gudy.azureus2.ui.swt.networks.SWTNetworkSelection;
  import org.gudy.azureus2.ui.swt.pluginsinstaller.InstallPluginWizard;
  import org.gudy.azureus2.ui.swt.progress.ProgressWindow;
  import org.gudy.azureus2.ui.swt.update.UpdateMonitor;
@@ -27,8 +27,8 @@ index 8a959c4..9069f3d 100644
 -
 +*/
  import com.aelitis.azureus.core.*;
- import com.aelitis.azureus.core.cnetwork.ContentNetwork;
  import com.aelitis.azureus.core.messenger.ClientMessageContext;
+ import com.aelitis.azureus.core.messenger.PlatformMessenger;
 @@ -358,12 +359,15 @@ public class Initializer
  	}
  	
@@ -46,38 +46,6 @@ index 8a959c4..9069f3d 100644
  	UpdateMonitor.getSingleton(core); // setup the update monitor
  	
  	//Tell listeners that all is initialized :
-diff --git a/org/gudy/azureus2/ui/swt/mainwindow/Initializer.java b/org/gudy/azureus2/ui/swt/mainwindow/Initializer.java
-index 620829f..d9e4478 100644
 a/org/gudy/azureus2/ui/swt/mainwindow/Initializer.java
-+++ b/org/gudy/azureus2/ui/swt/mainwindow/Initializer.java
-@@ -45,9 +45,10 @@ import org.gudy.azureus2.ui.swt.networks.SWTNetworkSelection;
- import org.gudy.azureus2.ui.swt.pluginsinstaller.InstallPluginWizard;
- import org.gudy.azureus2.ui.swt.progress.ProgressWindow;
- import org.gudy.azureus2.ui.swt.update.UpdateMonitor;
-+/* --- Adrian Perez: Don't initialize SWTUpdateChecker in Debian.
- import org.gudy.azureus2.ui.swt.updater2.PreUpdateChecker;
- import org.gudy.azureus2.ui.swt.updater2.SWTUpdateChecker;
--
-+*/
- import com.aelitis.azureus.core.*;
- import com.aelitis.azureus.core.util.CopyOnWriteList;
- import com.aelitis.azureus.launcher.Launcher;
-@@ -253,11 +254,14 @@ Initializer
- 	
- 		if (finalLogListener != null)
- 			Logger.removeListener(finalLogListener);
--	
-+/*
-+ * Adrian Perez: Don't initialize SWTUpdateChecker in Debian.
-+ *
- 		SWTUpdateChecker.initialize();
- 	
- 		PreUpdateChecker.initialize( core, COConfigurationManager.getStringParameter(ui));
- 	
-+*/
- 		UpdateMonitor.getSingleton(core); // setup the update monitor
- 	
- 		//Tell listeners that all is initialized :
 diff --git a/org/gudy/azureus2/update/CorePatchChecker.java b/org/gudy/azureus2/update/CorePatchChecker.java
 index 82fd9ae..b87f55a 100644
 --- a/org/gudy/azureus2/update/CorePatchChecker.java
diff --git a/debian/patches/fixes/platform.diff b/debian/patches/fixes/platform.diff
index 32fafbd..60f0f07 100644
--- a/debian/patches/fixes/platform.diff
+++ b/debian/patches/fixes/platform.diff
@@ -46,40 

Bug#666262: checkinstall: Empty fields choke apt*

2012-03-29 Thread spikethehobbitmage.excite
Package: checkinstall
Version: 1.6.2-2
Severity: normal
Tags: patch

checkinstall generates debian/control files with empty fields.
dpkg accepts these packages OK, but apt and friends choke on them.  This means 
that although these packages can be installed manually, they cannot be added to 
a repository.
The a href=http://www.debian.org/doc/debian-policy/ch-controlfields.html; 
spec/a isn't clear if empty fields are allowed or not.


if line 2566 is changed from:
cat  EOF  $BUILD_DIR/DEBIAN/control
to:
cat  EOF | sed s/ $// | egrep :   $BUILD_DIR/DEBIAN/control
empty fields will be stripped

Alternatively, this bug could be refiled against apt-get to support empty 
fields.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-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/bash

Versions of packages checkinstall depends on:
ii  dpkg-dev  1.16.1.2
ii  file  5.11-1
ii  libc6 2.13-27

ersions of packages checkinstall recommends:
ii  make  3.81-8.1

Versions of packages checkinstall suggests:
ii  gettext  0.18.1.1-5

-- no debconf information




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#663159: dummy package does not remove diversions, which breaks initramfs-tools

2012-03-08 Thread spikethehobbitmage.excite
Package: module-init-tools
Version: 6-1.1

I recently updated 2 machines, but only one was affected.

Upgrade was from 3.16-1 in both cases

The affected machine is not updated often, so I suspect this was hotfixed in a 
previous version that this machine skipped. If so, users who keep their systems 
up to date likely will not be affected.

update-initramfs failure can render the machine unbootable

this appears to be related to #304690

the following diversions remained after package upgrade:

diversion of /usr/share/man/man8/insmod.8.gz to 
/usr/share/man/man8/insmod.modutils.8.gz by module-init-tools
diversion of /sbin/update-modules to /sbin/update-modules.modutils by 
module-init-tools
diversion of /usr/share/man/fr/man8/rmmod.8.gz to 
/usr/share/man/fr/man8/rmmod.modutils.8.gz by module-init-tools
diversion of /usr/share/man/fr/man8/modinfo.8.gz to 
/usr/share/man/fr/man8/modinfo.modutils.8.gz by module-init-tools
diversion of /usr/share/man/fr/man8/update-modules.8.gz to 
/usr/share/man/fr/man8/update-modules.modutils.8.gz by module-init-tools
diversion of /usr/share/man/man8/modinfo.8.gz to 
/usr/share/man/man8/modinfo.modutils.8.gz by module-init-tools
diversion of /sbin/insmod to /sbin/insmod.modutils by module-init-tools
diversion of /usr/share/man/fr/man8/modprobe.8.gz to 
/usr/share/man/fr/man8/modprobe.modutils.8.gz by module-init-tools
diversion of /usr/share/man/man8/depmod.8.gz to 
/usr/share/man/man8/depmod.modutils.8.gz by module-init-tools
diversion of /usr/share/man/man8/lsmod.8.gz to 
/usr/share/man/man8/lsmod.modutils.8.gz by module-init-tools
diversion of /usr/share/man/man8/update-modules.8.gz to 
/usr/share/man/man8/update-modules.modutils.8.gz by module-init-tools
diversion of /usr/share/man/man8/modprobe.8.gz to 
/usr/share/man/man8/modprobe.modutils.8.gz by module-init-tools
diversion of /usr/share/man/fr/man8/insmod.8.gz to 
/usr/share/man/fr/man8/insmod.modutils.8.gz by module-init-tools
diversion of /sbin/rmmod to /sbin/rmmod.Lmodutils by module-init-tools
diversion of /sbin/kallsyms to /sbin/kallsyms.modutils by module-init-tools
diversion of /usr/share/man/man8/rmmod.8.gz to 
/usr/share/man/man8/rmmod.modutils.8.gz by module-init-tools
diversion of /sbin/lsmod to /sbin/lsmod.Lmodutils by module-init-tools
diversion of /usr/share/man/fr/man8/lsmod.8.gz to 
/usr/share/man/fr/man8/lsmod.modutils.8.gz by module-init-tools
diversion of /sbin/modprobe to /sbin/modprobe.Lmodutils by module-init-tools
diversion of /sbin/modinfo to /sbin/modinfo.modutils by module-init-tools
diversion of /usr/share/man/fr/man8/depmod.8.gz to 
/usr/share/man/fr/man8/depmod.modutils.8.gz by module-init-tools
diversion of /sbin/ksyms to /sbin/ksyms.modutils by module-init-tools

please have the dummy package remove all diversions in its init script

dpkg-divert --list | grep module-init-tools | awk '{print $3}' | while read ; 
do dpkg-divert --remove $REPLY ; done



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#583274: Bug occurs when drawing an empty string

2011-06-29 Thread spikethehobbitmage.excite
This bug occurs with ruby-sdl when trying to draw an empty string

a simple fix is to add 
 if text != ''
at the end of lines 317 and 321, so instead of
  font.drawBlendedUTF8(@screen,text,x,y,255,255,255)
you have
  font.drawBlendedUTF8(@screen,text,x,y,255,255,255) if text != ''

Personally I consider it a bug in ruby-sdl, for not checking inputs, but anyway.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#575348: problem still exists

2011-03-11 Thread spikethehobbitmage.excite
full xorg stack updated to experimental
gnome produces fully garbage 2nd monitor instead of a black bar

xserver-xorg-core 2:1.9.99.903-1
xserver-xorg-radeon 1:6.14.0-1+exp2

kernel 2.6.32-5-amd64 and 2.6.35-1~experimental.3
will try kernel 2.6.38~rc6-1~experimental.1 and report back



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#569542: video-radeon: DVI outputs swapped in KMS

2010-03-24 Thread spikethehobbitmage.excite
appears fixed in 1:6.12.192-2
kernel 2.6.33-1~experimental.4
KMS enabled



Improve your career health. Click now to study nutrition!
Nutrition
http://tagline.excite.com/c?cp=T3084xcF5Dw9oStSEG5gwQAAKZTf6gdozGulHdIMciQBawvXAAYAAADNAAASQwA=

Bug#575348: xrandr --scale no longer works

2010-03-24 Thread spikethehobbitmage.excite
Package: xserver-xorg-video-radeon
Version: 1:6.12.162-2

After upgrading kernel and radeon driver, xrandr --scale no longer works.
Instead of scaling screen output, display is corrupted.
There is additional incorrect behaviour if compositing is enabled.

--

Kernel: linux-image-2.6.33-2-amd64
Version: 2.6.33-1~experimental.4
KMS enabled with radeon driver
both free and non-free firmware is present

KDE 4.3.4
x11-xserver-utils version:  7.5+1

--

Previous versions:
radeon 1:6.12.99+git20100201.a887818f-1
kernel 2.6.33-1~experimental.3

--

To reproduce:
xrandr --output DVI-0 --scale .5x.5

Actual behaviour:
The desktop is reduced to 1/2 its original size, however the window manager 
does not seem to be notified.  Mouse movement is restricted to the new size.
No scaling of output image occurs, so right and bottom 1/2 of screen are blank.

If compositing is enabled:
Window contents are no longer updated unless a redraw is forced.
A strip across the top of the desktop no longer renders (old content remains).  
Mouse displays correctly in this area.
A smaller strip across the top of all windows is no longer rendered at all.

Expected behaviour:
The image on the monitor should be scaled (expanded) without changing the 
screen mode.
The underlying desktop should not be affected.

Note: I may be incorrect about the desktop not being resized as that has always 
been offscreen before, however the mouse was still able to enter that area.  
This is no longer the case.

--

Running xrandr --output DVI-0 --scale 1x1 restores normal state.

--

I do not believe xrandr is at fault as it was not upgraded, and it worked 
before.



Reach your goals of being healthier and happier. Click here for diet tips and 
solutions.
Diet Help
http://tagline.excite.com/c?cp=cTNFUOXleLZ4MbWLiZHyGwAAKZSpMaTyvuSNMb6e8igpKalCAAYAAADNAAAYQEpvY-w=

Bug#568028: slow scrolling due to disabled acceleration

2010-02-01 Thread spikethehobbitmage.excite
I had the same problem.  It means acceleration is disabled.

--snip--
(EE) RADEONHD(0): [dri] CP_INIT failed
(EE) RADEONHD(0): RHDDRIFinishScreenInit: RHDDRIKernelInit Failed.
--snip--

the kernel driver needs a firmware blob to run. (basically a video bios update 
that runs on the card)

to fix:
sudo apt-get install firmware-linux

then reboot

xserver-xorg-video-radeonhd suggests firmware-linux, but apt doesn't pull it in 
automatically.  perhaps a recommends would be more appropriate?



Best Weight Loss Program - Click Here!
Weight Loss Program
http://tagline.excite.com/c?cp=ZajGKTRNI12HpFY3BMO7HgAAKZQPmgh4_K8N3im05Ieqi7tEAAYAAADNAAAEUgA=

Bug#568028: duplicate 536581

2010-02-01 Thread spikethehobbitmage.excite
this bug is also a duplicate of 536581


Cheap Diet Help Tips. Click here.
Diet Help
http://tagline.excite.com/c?cp=Dz00OEJpbd9vOrSuAyPH9QAAKZQPmgh4_K8N3im05Ieqi7tEAAYAAADNAAAYQAA=

Bug#496863: merge with 457859

2008-08-28 Thread spikethehobbitmage.excite
np, Drew.

I've been running with the patch with no problems so far (except for dying a 
lot) so it seems to be OK.

my oops was supposed to say 'merge with 457859'

/never been able to get the hang of bugzilla

cheers.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#496863: zangband: RNG broken on AMD64

2008-08-27 Thread spikethehobbitmage.excite
Package: zangband
Version: 1:2.7.5pre1-3
Severity: important
Tags: patch

RNG does not detect 64 bit with GCC.  It does detect 64 bit Visual Studio.  
Character generator takes 40+ min to generate a character, or about 2 weeks if 
using autoroller.


insert the following code in src/h-type.h at line 106 to fix

--- snip ---

/* detect 64 bit GCC */
#ifdef _LP64
#define L64 1
#define USE_64B 1
#endif

--- snip ---


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-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/bash

Versions of packages zangband depends on:
ii  libc6  2.7-13GNU C Library: Shared libraries
ii  libglib1.2ldbl 1.2.10-19 The GLib library of C routines
ii  libgtk1.2  1.2.10-18.1   The GIMP Toolkit set of widgets fo
ii  libice62:1.0.4-1 X11 Inter-Client Exchange library
ii  libncurses55.6+20080804-1shared libraries for terminal hand
ii  libsm6 2:1.0.3-2 X11 Session Management library
ii  libx11-6   2:1.1.4-2 X11 client-side library
ii  libxaw72:1.0.4-2 X11 Athena Widget library
ii  libxext6   2:1.0.4-1 X11 miscellaneous extension librar
ii  libxi6 2:1.1.3-1 X11 Input extension library
ii  libxmu62:1.0.4-1 X11 miscellaneous utility library
ii  libxpm41:3.5.7-1 X11 pixmap library
ii  libxt6 1:1.0.5-3 X11 toolkit intrinsics library
ii  tcl8.4 8.4.19-2  Tcl (the Tool Command Language) v8
ii  tk8.4  8.4.19-2  Tk toolkit for Tcl and X11, v8.4 -
ii  zangband-data  1:2.7.5pre1-3 A single-player, text-based, rogue
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

zangband recommends no packages.

zangband suggests no packages.

-- no debconf information



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#496863: merge with 457859

2008-08-27 Thread spikethehobbitmage.excite
oops :(



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]