Bug#1027876: protobuf: package is missing CMake files

[Thomas Braun]

Am Sonntag, dem 14.01.2024 um 13:48 +0100 schrieb László Böszörményi
(GCS):

> It will take a while to make it to Sid, but please report back if you
> find any issues.

Works here, thanks for the update.

Bug#1027876: Missing cmake files

[Thomas Braun]

I'm also hitting a wall here as the cmake files are not present.

Bug#1042758: Please update to 4.3.0

[Thomas Braun]

Source: omniorb-dfsg
X-Debbugs-Cc: thomas.br...@byte-physics.de
Version: 
Severity: normal

Dear Maintainer,

please update to 4.3.0. See also https://omniorb.sourceforge.io.

-- System Information:
Debian Release: 11.7
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-23-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1030320: tango: New version 9.4.1 available

[Thomas Braun]

Package: tango
Severity: normal

We would really like to have 9.4.1 [0] in upcoming debian bookworm
instead of the old 9.3.x.

I've already tested if our tests pass on debian testing on amd64, yes
they do [1].

The changes compared to 9.3.x are listed at [2]. Packaging wise the
biggest change is that we now only support cmake.

As you are using the TangoSourceDistribution we have some info posted
at [3] wrt to the cmake options.

Thanks,
Thomas

[0]: https://gitlab.com/tango-controls/cppTango/-/releases/9.4.1
[1]: https://gitlab.com/tango-controls/cppTango/-/merge_requests/1044
[2]:
https://gitlab.com/tango-controls/cppTango/-/blob/main/RELEASE_NOTES.md
[3]:
https://gitlab.com/tango-controls/TangoSourceDistribution/-/tree/main/assets#installation

Bug#1020056:

[Thomas Braun]

The reason for the build breakage can be found in

https://tracker.debian.org/media/packages/z/zeromq3/changelog-4.3.4-3

which has

zeromq3 (4.3.4-3) unstable; urgency=medium

  * Remove zmq{,_addon}.hpp as these provided by cppzmq-dev from now on
(closes: #972785).

 -- Laszlo Boszormenyi (GCS)   Mon, 15 Aug 2022
18:40:34 +0200

so I think it should be as easy as adding cppzmq-dev to the build
dependencies.

 $diff -Nur control control.new
--- control 2022-10-13 16:19:07.384578078 +0200
+++ control.new 2022-10-13 16:19:03.972578004 +0200
@@ -7,6 +7,7 @@
default-libmysqlclient-dev,
libcos4-dev,
libzmq5-dev | libzmq3-dev,
+   cppzmq-dev,
omniidl,
po-debconf
 Build-Depends-Indep: doxygen,

Bug#992637: same here

[Thomas Braun]

I've experienced a similiar issue. After an upgrade to debian bullseye most of 
the USB ports stopped working. Whenever I used a USB device the PC crashed. As 
they work on Windows it is not a hardware issue.

Removing the power saving with powertop did the trick!

Thanks for posting that!

Mainboard: Asus P9X79

Bug#993755: Comment

[Thomas Braun]

I just upgraded from buster to bullseye (so no jumping releases) and 
encountered this bug as well.

Thanks for Otto for the workaround. This worked without issues.

Bug#989981: python3-tango: New version 9.3.3 available

[Thomas Braun]

Package: python3-tango
Severity: normal

See https://gitlab.com/tango-controls/pytango/-/tags/v9.3.3.

-- System Information:
Debian Release: 10.9
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-16-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-tango depends on:
ii  libboost-python1.67.0   1.67.0-13+deb10u1
ii  libc6   2.28-10
ii  libcos4-2   4.2.2-0.9+b1
ii  libgcc1 1:8.3.0-6
pn  liblog4tango5v5 
ii  libomniorb4-2   4.2.2-0.9+b1
ii  libomnithread4  4.2.2-0.9+b1
ii  libstdc++6  8.3.0-6
pn  libtango9   
ii  libzmq5 4.3.1-4+deb10u2
ii  python3 3.7.3-1
ii  python3-numpy [python3-numpy-abi9]  1:1.16.2-1
ii  python3-six 1.12.0-1

python3-tango recommends no packages.

python3-tango suggests no packages.

-- 
() byte physics
   Thomas Braun
   Schwarzastraße 9
   12055 Berlin
   Germany

Web:   www.byte-physics.de
Telephone: +49 (0)30/52 68 23 22
Fax:   +49 (0)30/52 68 43 26
USt-IdNr:  DE276717536

Bug#985007: Fixed upstream

[Thomas Braun]

Upstream has a fix in main for it, see
https://gitlab.com/tango-controls/pytango/-/commit/1ef452496c42d0773a8d6299bf3669166b25dc5d

-- 
() byte physics
   Thomas Braun
   Schwarzastraße 9
   12055 Berlin
   Germany

Web:   www.byte-physics.de
Telephone: +49 (0)30/52 68 23 22
Fax:   +49 (0)30/52 68 43 26
USt-IdNr:  DE276717536

Bug#628406: Updated patch?

[Thomas Braun]

In case this issue needs fixing for tango 9.3.4 as well, please submit a 
new patch so that it builds on kFreeBSD. You can also directly submit it 
to upstream at https://gitlab.com/tango-controls/cppTango.


Thanks,
Thomas

Bug#948496: 4.2.4 available

[Thomas Braun]

4.2.4 also removed the C++ throw specifications which makes it now
possible to compile applications using C++17 against omniORB.
-- 
() byte physics
   Thomas Braun
   Schwarzastraße 9
   12055 Berlin
   Germany

Web:   www.byte-physics.de
Telephone: +49 (0)30/52 68 23 22
Fax:   +49 (0)30/52 68 43 26
USt-IdNr:  DE276717536

Bug#965219: Recipe for reproduction

[Thomas Braun]

I can reproduce the problem when upgrading the tango-db package from
unstable to the one from experimental.

Unstable is up to date.

The failing line is 

/usr/sbin/dbconfig-generate-include: 246: cannot create /tmp/dbconfig-
generate-include.FaUbJB: Permission denied

I'm attaching the full log as well.

root@debian:/home/thomas# apt remove --purge "tango*"
[...]
The following packages will be REMOVED:
  libtango-tools* libtango9* tango-common* tango-db* tango-starter*
tango-test*
0 upgraded, 0 newly installed, 6 to remove and 1 not upgraded.
After this operation, 9,363 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 311392 files and directories currently
installed.)
Removing tango-test (9.3.4~rc6+dfsg1-1~exp1) ...
Removing tango-starter (9.3.4~rc6+dfsg1-1~exp1) ...
Removing tango-db (9.3.4~rc6+dfsg1-1~exp1) ...
Determining localhost credentials from /etc/mysql/debian.cnf:
succeeded.
dbconfig-common: dumping mysql database tango to /var/tmp/tango-
db.tango.2020-09-10-12.46.mysql.aNGXXT.
dbconfig-common: dropping mysql database tango.
dropping database tango: success.
verifying database tango was dropped: success.
dbconfig-common: revoking privileges for user tango on tango.
revoking access to database tango from tango@localhost: success.
Removing libtango-tools (9.3.4~rc6+dfsg1-1~exp1) ...
Removing libtango9:amd64 (9.3.4~rc6+dfsg1-1~exp1) ...
Removing tango-common (9.3.4~rc6+dfsg1-1~exp1) ...
Processing triggers for libc-bin (2.31-3) ...
(Reading database ... 311344 files and directories currently
installed.)
Purging configuration files for tango-common (9.3.4~rc6+dfsg1-1~exp1)
...
dpkg: warning: while removing tango-common, directory '/var/lib/tango'
not empty so not removed
Purging configuration files for tango-starter (9.3.4~rc6+dfsg1-1~exp1)
...
insserv: Script sysstat has overlapping Default-Start and Default-Stop
runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
Purging configuration files for tango-db (9.3.4~rc6+dfsg1-1~exp1) ...
insserv: Script sysstat has overlapping Default-Start and Default-Stop
runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
Processing triggers for systemd (246.4-1) ...
root@debian:/home/thomas# rm /var/tmp/tango-db.tango.*
root@debian:/home/thomas# apt install tango-db
[...]
The following additional packages will be installed:
  libtango-tools libtango9 tango-common
The following NEW packages will be installed:
  libtango-tools libtango9 tango-common tango-db
0 upgraded, 4 newly installed, 0 to remove and 1 not upgraded.
Need to get 1,852 kB of archives.
After this operation, 7,932 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.de.debian.org/debian unstable/main amd64 tango-common
all 9.2.5a+dfsg1-2 [8,568 B]
Get:2 http://ftp.de.debian.org/debian unstable/main amd64 libtango9
amd64 9.2.5a+dfsg1-2+b2 [1,613 kB]
Get:3 http://ftp.de.debian.org/debian unstable/main amd64 libtango-
tools amd64 9.2.5a+dfsg1-2+b2 [29.2 kB]
Get:4 http://ftp.de.debian.org/debian unstable/main amd64 tango-db
amd64 9.2.5a+dfsg1-2+b2 [202 kB]
Fetched 1,852 kB in 1s (2,633 kB/s)
Preconfiguring packages ...
Selecting previously unselected package tango-common.
(Reading database ... 311341 files and directories currently
installed.)
Preparing to unpack .../tango-common_9.2.5a+dfsg1-2_all.deb ...
Unpacking tango-common (9.2.5a+dfsg1-2) ...
Selecting previously unselected package libtango9:amd64.
Preparing to unpack .../libtango9_9.2.5a+dfsg1-2+b2_amd64.deb ...
Unpacking libtango9:amd64 (9.2.5a+dfsg1-2+b2) ...
Selecting previously unselected package libtango-tools.
Preparing to unpack .../libtango-tools_9.2.5a+dfsg1-2+b2_amd64.deb ...
Unpacking libtango-tools (9.2.5a+dfsg1-2+b2) ...
Selecting previously unselected package tango-db.
Preparing to unpack .../tango-db_9.2.5a+dfsg1-2+b2_amd64.deb ...
Unpacking tango-db (9.2.5a+dfsg1-2+b2) ...
Setting up tango-common (9.2.5a+dfsg1-2) ...
usermod: no changes
Setting up libtango9:amd64 (9.2.5a+dfsg1-2+b2) ...
Setting up libtango-tools (9.2.5a+dfsg1-2+b2) ...
Setting up tango-db (9.2.5a+dfsg1-2+b2) ...
Determining localhost credentials from /etc/mysql/debian.cnf:
succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/tango-db.conf

Creating config file /etc/dbconfig-common/tango-db.conf with new
version

Creating config file /var/lib/tango/.my.cnf with new version
checking privileges on database tango for tango@localhost: user
creation needed.
granting access to database tango for tango@localhost: success.
verifying access for tango@localhost: success.
creating database tango: success.
verifying database tango exists: success.
populating database via sql...  done.
dbconfig-common: flushing administrative password
insserv: Script sysstat has overlapping Default-Start and Default-Stop
runlevels (2 3 4 5) and (2 3 4 5). This should be fixed.
Processing triggers for systemd (246.4-1) ...
Processing triggers for libc-bin (2.31-3) ...
root@debian:/home/thomas# 

Bug#949549: Not fixed

[Thomas Braun]

Am Montag, den 24.08.2020, 12:11 + schrieb PICCA Frederic-Emmanuel:

Hello Frederic,

yes I think this is a false positive indeed. The flags are correctly
passed.

Thanks for digging,
Thomas

> Hello Thomas,
> 
> I am wondering if this is not a false positive.
> 
> all the code is compiled with -D_FORTIFY_SOURCE=2
> 
> https://salsa.debian.org/science-team/tango/-/jobs/954394/raw
> 
> Can you confirm that it is a false positive ?
> 
> I am not that confident when it comes to hardening flags.
> 
> for the record I checked also the Database and it is also affected by
> this.

Bug#949549: Not fixed

[Thomas Braun]

In [1] I still have

I: tango-accesscontrol: hardening-no-fortify-functions
usr/lib/tango/TangoAccessControl.

and checking with hardening-check gives the same output as before.

[1]: https://salsa.debian.org/science-team/tango/-/jobs/808832

Bug#949549: tango-accesscontrol: Does not use hardening flags for compilation

[Thomas Braun]

Package: tango-accesscontrol
Version: 9.3.4~rc2+dfsg2-1~exp3
Severity: normal

Dear Maintainer,

according to the lintian output and my own testing the hardening flags
are not set correctly for TangoAccessControl.

/usr/lib/tango/TangoAccessControl:
 Position Independent Executable: yes
 Stack protected: yes
 Fortify Source functions: no, only unprotected functions found!
 Read-only relocations: yes
 Immediate binding: yes
 Stack clash protection: unknown, no -fstack-clash-protection
instructions found
 Control flow integrity: unknown, no -fcf-protection instructions
found!

They seems to be set correctly for DatabaseDS and Starter.

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

Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tango-accesscontrol depends on:
ii  init-system-helpers  1.57
ii  libc62.29-9
ii  libgcc1  1:9.2.1-23
ii  libmariadb3  1:10.3.21-2
ii  libomniorb4-24.2.2-0.9+b1
ii  libomnithread4   4.2.2-0.9+b1
ii  libstdc++6   9.2.1-23
ii  libtango-tools   9.3.4~rc2+dfsg2-1~exp3
ii  libtango99.3.4~rc2+dfsg2-1~exp3
ii  lsb-base 11.1.0
ii  tango-db 9.2.5a+dfsg1-2+b2
ii  tango-starter9.2.5a+dfsg1-2+b2

tango-accesscontrol recommends no packages.

tango-accesscontrol suggests no packages.

-- no debconf information

Bug#949540: libtango-tools: Move tango_admin into a directory in $PATH

[Thomas Braun]

Package: libtango-tools
Version: 9.3.4~rc2+dfsg2-1~exp3
Severity: normal

Dear Maintainer,

please move tango_admin into a directory which is in $PATH so that the
user can call it without having to figure out where it is.

Thanks,
Thomas

-- System Information:
Debian Release: 9.11
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-0.bpo.6-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libtango-tools depends on:
ii  libc6 2.24-11+deb9u4
ii  libcos4-1 4.1.6-2.1+b1
ii  libgcc1   1:6.3.0-18+deb9u1
pn  liblog4tango5v5   
ii  libomniorb4-1 4.1.6-2.1+b1
ii  libomnithread3c2  4.1.6-2.1+b1
ii  libstdc++66.3.0-18+deb9u1
pn  libtango9 
ii  libzmq5   4.2.1-4+deb9u2

libtango-tools recommends no packages.

libtango-tools suggests no packages.

Bug#948496: libomniorb4-dev: New upstream version (4.2.3) available

[Thomas Braun]

Package: libomniorb4-dev

Version: 4.1.6-2.1+b1

Severity: normal


Dear Maintainer,


please upgrade to the new upstream release, see also 
https://sourceforge.net/projects/omniorb/files/omniORB/omniORB-4.2.3.


Thanks,
Thomas

-- System Information:

Debian Release: 9.11

  APT prefers oldstable

  APT policy: (500, 'oldstable')

Architecture: amd64 (x86_64)

Foreign Architectures: i386



Kernel: Linux 4.19.0-0.bpo.6-amd64 (SMP w/12 CPU cores)

Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE= (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash

Init: systemd (via /run/systemd/system)



Versions of packages libomniorb4-dev depends on:

ii  libomniorb4-1   4.1.6-2.1+b1

ii  libomnithread3-dev  4.1.6-2.1+b1

ii  libssl1.0-dev   1.0.2u-1~deb9u1

ii  pkg-config  0.29-4+b1



libomniorb4-dev recommends no packages.



libomniorb4-dev suggests no packages.



-- no debconf information

Bug#875626: closed by Adrian Bunk <b...@debian.org> (This was a temporary issue during the opencv transition)

[Thomas Braun]

But I'm using debian stable, so how can a transition in unstable break that?

Bug#875626: marble: Unsatisfied build-deps

[Thomas Braun]

Package: marble
Version: 4:16.08.3-1
Severity: normal

Dear Maintainer,

executing `apt-get build-dep` gives

Reading package lists... Done
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:
 builddeps:marble : Depends: libopencv-highgui-dev but it is not going
 to be installed
 E: Unable to correct problems, you have held broken packages.

I would have expected that this command works.

Thanks,
Thomas

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages marble depends on:
ii  kio 5.28.0-2
ii  libc6   2.24-11+deb9u1
ii  libgcc1 1:6.3.0-18
ii  libkf5configcore5   5.28.0-2
ii  libkf5configgui55.28.0-2
ii  libkf5configwidgets55.28.0-2
ii  libkf5coreaddons5   5.28.0-2
ii  libkf5i18n5 5.28.0-2
ii  libkf5kiowidgets5   5.28.0-2
ii  libkf5newstuff5 5.28.0-1
ii  libkf5parts55.28.0-1
ii  libkf5runner5   5.28.0-1
ii  libkf5widgetsaddons55.28.0-3
ii  libkf5xmlgui5   5.28.0-1
ii  libmarblewidget-qt5-25  4:16.08.3-1
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5network5  5.7.1+dfsg-3+b1
ii  libqt5printsupport5 5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libqt5xml5  5.7.1+dfsg-3+b1
ii  libstdc++6  6.3.0-18
ii  marble-data 4:16.08.3-1
ii  marble-plugins  4:16.08.3-1

marble recommends no packages.

Versions of packages marble suggests:
pn  gosmore   
pn  monav-routing-daemon  
pn  routino   

-- no debconf information

Bug#843618: [debian-mysql] Bug#843618: mysql-server-5.5: Fails to start after recent security update

[Thomas Braun]

> Lars Tangvald <lars.tangv...@oracle.com> hat am 8. November 2016 um 12:28
> geschrieben:

Hi Lars,

thanks for the quick reply.

> It's probably something with your setup the upgrade logic can't handle 
> correctly.
> In 5.5.53, MySQL changes the inbuilt secure-file-priv (determined where 
> the server can read/write data for import/export operations) default 
> setting from blank, meaning the server has read/write access anywhere, 
> to /var/lib/mysql-files, which should be automatically created by the 
> postinst. This is a fairly big change, but it was felt the old behavior 
> was a big enough security risk to justify it.
> Do you have a special setup (partition, symlink, etc) for your /var/lib 
> folders, so the default directory might not be possible to create/access?
> 
> Finally, setting secure-file-priv to your datadir is very strongly 
> recommended against, as it pretty much gives any database user full 
> database access.
> We recommend either setting it to a separate location, or to NULL (only 
> available in 5.5.53+), which will disable import/export operations for 
> the server.

I've investigated and indeed /var/lib/mysql-files did not exist.

The reason was that another third-party (gitlab-ee) package depending on the
mysql-server package broke the apt-get upgrade, 
leaving mysql-server's postinst script not executed. 

I've reinstalled the mysql-server package, removed my hack and now it works
again.

Thanks again, especially about mentioning the security implications about my
hack, 
Thomas

> On 11/08/2016 11:58 AM, Thomas Braun wrote:
> > Package: mysql-server-5.5
> > Version: 5.5.53-0+deb8u1
> > Severity: important
> >
> > Dear Maintainer,
> >
> > after tonights security update my mysql server does not start anymore.
> >
> > Looking in /var/log/mysql/error.log gives:
> > 161108 11:18:02 mysqld_safe Starting mysqld daemon with databases from
> > /var/lib/mysql
> > 161108 11:18:02 [Warning] Using unique option prefix key_buffer instead of
> > key_buffer_size is deprecated and will be removed in a future release.
> > Please
> > use the full name instead.
> > /usr/sbin/mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2)
> > 161108 11:18:02 [ERROR] Failed to access directory for --secure-file-priv.
> > Please make sure that directory exists and is accessible by MySQL Server.
> > Supplied value : /var/lib/mysql-files
> > 161108 11:18:02 [ERROR] Aborting
> >
> > So it looks like that the new secure-file-priv option defaults to a
> > different
> > folder than specified as datadir in my config.
> > I've not touched the mysql settings manually.
> >
> > I've fixed the bug by adding the file
> > /etc/mysql/conf.d/fix-security-update-bug.cnf with contents
> >
> > [mysqld]
> > secure_file_priv=/var/lib/mysql
> >
> > Thanks for your work on the mysql packages,
> > Thomas
> >
> > -- System Information:
> > Debian Release: 8.6
> >APT prefers stable
> >APT policy: (500, 'stable')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
> > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> >
> > Versions of packages mysql-server-5.5 depends on:
> > ii  adduser3.113+nmu3
> > ii  debconf [debconf-2.0]  1.5.56
> > ii  initscripts2.88dsf-59
> > ii  libc6  2.19-18+deb8u6
> > ii  libdbi-perl1.631-3+b1
> > ii  libgcc11:4.9.2-10
> > ii  libstdc++6 4.9.2-10
> > ii  lsb-base   4.1+Debian13+nmu1
> > iu  mysql-client-5.5   5.5.53-0+deb8u1
> > ii  mysql-common   5.5.53-0+deb8u1
> > iu  mysql-server-core-5.5  5.5.53-0+deb8u1
> > ii  passwd 1:4.2-3+deb8u1
> > ii  perl   5.20.2-3+deb8u6
> > ii  psmisc 22.21-2
> > ii  zlib1g 1:1.2.8.dfsg-2+b1
> >
> > Versions of packages mysql-server-5.5 recommends:
> > ii  libhtml-template-perl  2.95-1
> >
> > Versions of packages mysql-server-5.5 suggests:
> > ii  heirloom-mailx [mailx]  12.5-4
> > pn  tinyca  
> >
> > -- debconf information:
> >mysql-server-5.5/postrm_remove_databases: false
> >mysql-server-5.5/start_on_boot: true
> >mysql-server/error_setting_password:
> >mysql-server-5.5/nis_warning:
> >mysql-server/password_mismatch:
> >mysql-server-5.5/really_downgrade: false
> >mysql-server/no_upgrade_when_using_ndb:
> >
> > ___
> > pkg-mysql-maint mailing list
> > pkg-mysql-ma...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint
> 
> 

Bug#843618: mysql-server-5.5: Fails to start after recent security update

[Thomas Braun]

Package: mysql-server-5.5
Version: 5.5.53-0+deb8u1
Severity: important

Dear Maintainer,

after tonights security update my mysql server does not start anymore.

Looking in /var/log/mysql/error.log gives:
161108 11:18:02 mysqld_safe Starting mysqld daemon with databases from
/var/lib/mysql
161108 11:18:02 [Warning] Using unique option prefix key_buffer instead of
key_buffer_size is deprecated and will be removed in a future release. Please
use the full name instead.
/usr/sbin/mysqld: Error on realpath() on '/var/lib/mysql-files' (Error 2)
161108 11:18:02 [ERROR] Failed to access directory for --secure-file-priv.
Please make sure that directory exists and is accessible by MySQL Server.
Supplied value : /var/lib/mysql-files
161108 11:18:02 [ERROR] Aborting

So it looks like that the new secure-file-priv option defaults to a different
folder than specified as datadir in my config.
I've not touched the mysql settings manually.

I've fixed the bug by adding the file
/etc/mysql/conf.d/fix-security-update-bug.cnf with contents

[mysqld]
secure_file_priv=/var/lib/mysql

Thanks for your work on the mysql packages,
Thomas

-- System Information:
Debian Release: 8.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mysql-server-5.5 depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.56
ii  initscripts2.88dsf-59
ii  libc6  2.19-18+deb8u6
ii  libdbi-perl1.631-3+b1
ii  libgcc11:4.9.2-10
ii  libstdc++6 4.9.2-10
ii  lsb-base   4.1+Debian13+nmu1
iu  mysql-client-5.5   5.5.53-0+deb8u1
ii  mysql-common   5.5.53-0+deb8u1
iu  mysql-server-core-5.5  5.5.53-0+deb8u1
ii  passwd 1:4.2-3+deb8u1
ii  perl   5.20.2-3+deb8u6
ii  psmisc 22.21-2
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages mysql-server-5.5 recommends:
ii  libhtml-template-perl  2.95-1

Versions of packages mysql-server-5.5 suggests:
ii  heirloom-mailx [mailx]  12.5-4
pn  tinyca  

-- debconf information:
  mysql-server-5.5/postrm_remove_databases: false
  mysql-server-5.5/start_on_boot: true
  mysql-server/error_setting_password:
  mysql-server-5.5/nis_warning:
  mysql-server/password_mismatch:
  mysql-server-5.5/really_downgrade: false
  mysql-server/no_upgrade_when_using_ndb:

Bug#672435: x11vnc: Option -localhost seems to fail to restrict ipv6 access

[Thomas Braun]

tags 672435 security
thanks

On Fri, 11 May 2012 11:12:46 +0900 Ryo IGARASHI  wrote:
> Today I found that the option -localhost does not restrict ipv6 access to 
> ::1(localhost).
> Looking at the -localhost option section of 'man x11vnc', the ipv6 access 
> seems to
> be restricted to ::1 (loopback) as well. However, the output of 'netstat -ln' 
> shows:
> 
> $ netstat -ln
> Proto Recv-Q Send-Q Local Address   Foreign Address State
> ...
> tcp6   0  0 :::5900 :::*LISTEN
> ...

I've just verified that bug with the current version in jessie.

x11vnc -localhost -create

netstat -lntp | grep 5900

tcp0  0 127.0.0.1:5900  0.0.0.0:*   LISTEN  
-
tcp6   0  0 :::5900 :::*LISTEN  
-

The manpage states 

-localhost
[...]
IPv6: if IPv6 is supported, this option automatically implies the IPv6 loopback 
address '::1' as well.

This bug should be treated as a SECURITY relevant bug. Offering VNC services on 
the network interface while claiming that it is only accessible via loopback is 
really bad.

Thomas

Bug#790236: openssh-server: sshd segfaults afer many unsuccesfull login attempts

[Thomas Braun]

Package: openssh-server
Version: 1:6.0p1-4+deb7u2
Severity: normal

Dear Maintainer,
yesterday my ssh server segfaulted with the following message:
[4868342.681831] sshd[3996]: segfault at 7fa8c721c6a0 ip
7faac7259ddb sp 7ffc696e59d0 error 4 in sshd[7faac7249000+7c000]

This happened never before and the machine is on 24/7 with a public
accessible ssh port.

Immediately before I have 10k entries in sshd.log which say
 Jun 26 23:04:30 localhost sshd[7994]: User root from XXX not allowed
because not listed in AllowUsers
 Jun 26 23:04:30 localhost sshd[7994]: input_userauth_request: invalid
user root [preauth]
 Jun 26 23:04:30 localhost sshd[7994]: Received disconnect from XXX: 11:
Bye Bye [preauth]

At that time neither the memory nor the disk was full.

My sshd.conf says
[...]
AllowUsers ... root@127.0.0.1 ...
PermitRootLogin without-password
[...]

Please tell me if I should provide more information.

-- System Information:
Debian Release: 7.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages openssh-server depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.49
ii  dpkg   1.16.16
ii  libc6  2.13-38+deb7u8
ii  libcomerr2 1.42.5-1.1+deb7u1
ii  libgssapi-krb5-2   1.10.1+dfsg-5+deb7u3
ii  libkrb5-3  1.10.1+dfsg-5+deb7u3
ii  libpam-modules 1.1.3-7.1
ii  libpam-runtime 1.1.3-7.1
ii  libpam0g   1.1.3-7.1
ii  libselinux12.1.9-5
ii  libssl1.0.01.0.1e-2+deb7u17
ii  libwrap0   7.6.q-24
ii  lsb-base   4.1+Debian8+deb7u1
ii  openssh-client 1:6.0p1-4+deb7u2
ii  procps 1:3.3.3-3
ii  zlib1g 1:1.2.7.dfsg-13

Versions of packages openssh-server recommends:
ii  ncurses-term 5.9-10
ii  openssh-blacklist0.4.1+nmu1
ii  openssh-blacklist-extra  0.4.1+nmu1
ii  xauth1:1.0.7-1

Versions of packages openssh-server suggests:
pn  molly-guard   none
pn  monkeysphere  none
pn  rssh  none
pn  ssh-askpass   none
pn  ufw   none

-- debconf information:
  ssh/vulnerable_host_keys:
  ssh/new_config: true
* ssh/use_old_init_script: true
  ssh/disable_cr_auth: false
  ssh/encrypted_host_key_but_no_keygen:


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

Bug#712719: Downgrade procedure

[Thomas Braun]

From my three printers one, a UTAX CD1120, stopped working after the
squeeze-wheezy dist-upgrade.

The printer uses a lpd queue, port 9100, so the IPP changes can not be
the culprit.

I solved the problem by downgrading the cups packages to the squeeze
version.

Just in case someone wants to do that also the procedure is:
1.) add the following to /etc/apt/preferences
---
Package: cups cups-common libcups* cups-client cups-driver-gutenprint
Pin: release n=squeeze 
Pin-Priority: 1010
---
2.) apt-get install --reinstall cups
3.) /etc/init.d/cups stop
4.) Replace the contents of /etc/cups of a backup of your old squeeze
config files.
5.) /etc/init.d/cups start

Hope that helps
Thomas


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

Bug#561931: Fixed upstream

[Thomas Braun]

I just encountered the same bug on debian lenny.

Looks like this is already fixed upstream, see e.g.
http://sources.redhat.com/git/gitweb.cgi?p=lvm2.git;a=commit;h=16d385ac6a3c96e40c2a0022ab83377cb116f7d9.

Judging from the commit comment using a physical volume name explicitly 
works around this problem.


Bye,
thomas



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

Bug#605518: Fixed upstream

[Thomas Braun]

This bug is fixed upstream in k3b 2.0.1, see also 
https://bugs.kde.org/show_bug.cgi?id=236466 and 
http://websvn.kde.org/?view=revrevision=1144817.

Any chance to get this fix cherry picked for sqeeze?

Thanks,
Thomas



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

Bug#567126: (kein Betreff)

[Thomas Braun]

Hello Ric,

can you provide a testcase for this bug?
Looking at the latex syntax file only showed that both $ and \( should
behave equivalently. And my short testing also didn't help.
Are you using the current (1.41) version of the syntax file?



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

Bug#551394: loop-aes-utils: loop-aes-keygen should use --s2k-count option for gpg recommended by loop-aes.readme

[Thomas Braun]

Package: loop-aes-utils
Version: 2.13.1-4
Severity: normal
Tags: patch

*** Please type your report below this line ***

Hi,

the loop-aes.readme suggests to use the option --s2k-count 8388608 for
generating gpg keys. In short this improves the resitance to dictionary 
attacks.

The attached patch adds this option to the gpg call. This commandline
option is available in gpg 1.4.6 or later.

Thanks for your time,
Thomas

-- System Information:
Debian Release: 5.0.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages loop-aes-utils depends on:
ii  gnupg 1.4.9-3+lenny1 GNU privacy guard - a free PGP 
rep
ii  libblkid1 1.41.3-1   block device id library
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  libselinux1   2.0.65-5   SELinux shared libraries
ii  libuuid1  1.41.3-1   universally unique id library
ii  mount 2.13.1.1-1 Tools for mounting and 
manipulatin

Versions of packages loop-aes-utils recommends:
ii  sharutils 1:4.6.3-1  shar, unshar, uuencode, uudecode

loop-aes-utils suggests no packages.

-- no debconf information
--- loop-aes-keygen	2009-10-18 00:57:56.640026751 +0200
+++ loop-aes-keygen.modified	2009-10-18 01:06:16.576326458 +0200
@@ -157,7 +157,7 @@
 {
 	version=$1
 	keyfile=$2
-	gpgargs=$3
+	gpgargs=--s2k-count 8388608 $3
 
 	# These are the known loop-AES key formats:
 	#  v1.x1 45 bytes   AES key 

Bug#539252: [Pkg-kde-extras] Bug#539252: viewpdf: could not find the libkghostviewpart library

[Thomas Braun]

On Mon, 24 Aug 2009 10:04:28 +0200, Fathi Boudra f...@debian.org wrote:

Hi Fathi,

 I tend to disagree on this one:
 You should install kpdf, kghostview and kdvi then all standard view
tools
 should work.
 
 these applications are KDE3 pdf viewer.
 Current Kile package recommends okular, which is the KDE 4 pdf viewer.
 The user has okular installed. It should be able to view his pdf.

sorry my mistake. I read the report too sloppy. Prior to kile 2.1 beta2 the
tools were not upgraded automatically
Starting with 2.1beta2 the user will be asked once if he wants to upgrade
the tools, and these tools now will have all the proper KDE4 apps.
This tool upgrading can be also done by hand in the configure
kile-tools-Reload default tools.


bye,
thomas



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

Bug#543282: kile: Please include new beta release 2.1beta2

[Thomas Braun]

Package: kile
Severity: normal

*** Please type your report below this line ***

Hi,

we just released a new beta version of kile namely 2.1beta2. Would be nice to 
have it in debian.

Thanks,
Thomas

PS: I hope this kind of bug reports are okay. If not I would be glad to hear
from you for alternative ways.


-- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'unstable'), (10, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kile depends on:
ii  kdelibs4c2a  4:3.5.10.dfsg.1-0lenny1 core libraries and binaries for 
al
ii  konsole  4:3.5.9.dfsg.1-6X terminal emulator for KDE
ii  libc62.7-18  GNU C Library: Shared libraries
ii  libgcc1  1:4.3.2-1.1 GCC support library
ii  libqt3-mt3:3.3.8b-5+b1   Qt GUI Library (Threaded runtime 
v
ii  libstdc++6   4.3.2-1.1   The GNU Standard C++ Library v3
ii  texlive-base-bin 2007.dfsg.2-4   TeX Live: Essential binaries

Versions of packages kile recommends:
ii  kdvi4:3.5.9-3+lenny1 dvi viewer for KDE
ii  kghostview  4:3.5.9-3+lenny1 PostScript viewer for KDE
pn  tetex-doc   none   (no description available)
pn  tetex-extra none   (no description available)

Versions of packages kile suggests:
pn  gbib   none(no description available)
pn  kile-i18n  none(no description available)
pn  latex2html none(no description available)
ii  pybliographer  1.2.11-1  tool for manipulating 
bibliographi
ii  xfig   1:3.2.5-rel-3 Facility for Interactive 
Generatio



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

Bug#539252: (no subject)

[Thomas Braun]

You should install kpdf, kghostview and kdvi then all standard view tools 
should work.

bye,
thomas



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

Bug#536297: Not reproducible with Kile 2.1 beta1

[Thomas Braun]

Hi,

I can not reproduce the bug with the current beta version of kile 2.1
beta1 which is based on KDE4.

bye,
Thomas



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

Bug#533204: kile: Please update svn snapshot to 2.1 beta1 release

[Thomas Braun]

Package: kile
Severity: normal

Two days ago we released the beta1 version of kile 2.1. This version
could need some broader testing and is also considered worth a try and also 
more stable than the current svn snapshot in debian.

Thanks,
Thomas Braun

PS:
The bugs
#519905
#528831
#358863
#359873
can also be closed I think. They are already fixed in the current
svn snapshot avaiblable in debian or by KDE4.


*** Please type your report below this line ***


-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable'), (100, 'unstable'), (10, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-2-686 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kile depends on:
ii  kdelibs4c2a  4:3.5.10.dfsg.1-0lenny1 core libraries and binaries for 
al
ii  konsole  4:3.5.9.dfsg.1-6X terminal emulator for KDE
ii  libc62.7-18  GNU C Library: Shared libraries
ii  libgcc1  1:4.3.2-1.1 GCC support library
ii  libqt3-mt3:3.3.8b-5+b1   Qt GUI Library (Threaded runtime 
v
ii  libstdc++6   4.3.2-1.1   The GNU Standard C++ Library v3
ii  texlive-base-bin 2007.dfsg.2-4   TeX Live: Essential binaries

Versions of packages kile recommends:
ii  kdvi4:3.5.9-3+lenny1 dvi viewer for KDE
ii  kghostview  4:3.5.9-3+lenny1 PostScript viewer for KDE
pn  tetex-doc   none   (no description available)
pn  tetex-extra none   (no description available)

Versions of packages kile suggests:
pn  gbib   none(no description available)
pn  kile-i18n  none(no description available)
pn  latex2html none(no description available)
ii  pybliographer  1.2.11-1  tool for manipulating 
bibliographi
ii  xfig   1:3.2.5-rel-3 Facility for Interactive 
Generatio



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

Bug#519746: not fixed

[Thomas Braun]

Hi,

I think might have been some kind of misunderstanding.
This bug is not closed.

I've tested upstream revision 966017.

bye,
thomas (member of kile dev team)



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

Bug#514404: also for lvm2 devices

[Thomas Braun]

The same is true if your encrypted root partition is on a LVM2 volume group.
Then one also has to add lvm2 by hand 
to /usr/share/initramfs-tools/scripts/local-top/loopaes and regenerate the 
initramfs.

This bug is escpecially on new installs where you can in this way happily 
create unbootable systems.

In my case it was the combination of loop-aes/LVM2/RAID which created an 
unbootable system.



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

Bug#526582: fixed upstream, please package new svn snapshot

[Thomas Braun]

Hi,

this bug is already fixed in upstream svn.

@Debian KDE Extras Team: It would be good to update the svn snapshot as we 
currently get quite some complaints about this bug.
Thanks :)

bye,
thomas (kile developer)



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

Bug#526704: initramfs-tools: Add config options as explained in /usr/share/doc/loop-aes-utils/README

[Thomas Braun]

Package: initramfs-tools
Version: 0.92o
Severity: minor
Tags: patch

*** Please type your report below this line ***

The option INITRAMFS_LOOPAES for mkinitramfs is explained in the file
/usr/share/doc/loop-aes-utils/README. I think it would be more appropriate to 
include a short explanation in the initram-tools config files. So that one 
can spot the information more easily.

A starting point could be a file
/etc/initramfs-tools/conf.d/loopaes with the following content:
##
# Support for encrypted root using loop-aes
#
# INITRAMFS_LOOPAES : [ auto | no | yes ]
#
# auto : Determine from /etc/fstab if the root device is encrypted and
#add support for it if needed
# yes  : Add support for encrypted root device
# no   : Don't add support for encrypted root device
#
INITRAMFS_LOOPAES=auto
##

Thanks for your time,
Thomas Braun

-- Package-specific info:
-- /proc/cmdline
root=LABEL=lenny ro 

-- /proc/filesystems
ext3
fuseblk
xfs

-- lsmod
Module  Size  Used by
ppdev   6500  0 
lp  8164  0 
vmnet  33632  15 
vmblock11652  3 
vmci   44052  1 
vmmon  60400  6 
nls_utf81760  5 
cifs  208692  5 
nls_base6820  2 nls_utf8,cifs
ipv6  235364  23 
xfs   457976  1 
fuse   42908  1 
dm_snapshot14340  0 
dm_mirror  15104  0 
dm_log  8484  1 dm_mirror
dm_mod 46184  3 dm_snapshot,dm_mirror,dm_log
eepro100   25168  0 
mii 4896  1 eepro100
snd_emu10k1_synth   5664  0 
snd_emux_synth 27904  1 snd_emu10k1_synth
snd_seq_virmidi 4896  1 snd_emux_synth
snd_seq_midi_emul   5376  1 snd_emux_synth
snd_emu10k1   114976  3 snd_emu10k1_synth
firmware_class  6816  1 snd_emu10k1
snd_ac97_codec 88484  1 snd_emu10k1
ac97_bus1728  1 snd_ac97_codec
snd_pcm_oss32832  0 
snd_mixer_oss  12320  2 snd_pcm_oss
snd_pcm62596  3 snd_emu10k1,snd_ac97_codec,snd_pcm_oss
snd_page_alloc  7816  2 snd_emu10k1,snd_pcm
snd_util_mem4032  2 snd_emux_synth,snd_emu10k1
snd_hwdep   6212  2 snd_emux_synth,snd_emu10k1
k8temp  4064  0 
snd_seq_dummy   2660  0 
parport_pc 22500  1 
parport30988  3 ppdev,lp,parport_pc
snd_seq_oss24992  0 
snd_seq_midi5728  0 
i2c_viapro  6836  0 
pcspkr  2432  0 
snd_rawmidi18528  3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi
i2c_core   19828  1 i2c_viapro
snd_seq_midi_event  6432  3 snd_seq_virmidi,snd_seq_oss,snd_seq_midi
snd_seq41456  9 
snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer  17800  3 snd_emu10k1,snd_pcm,snd_seq
snd_seq_device  6380  8 
snd_emu10k1_synth,snd_emux_synth,snd_emu10k1,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd45604  15 
snd_emux_synth,snd_seq_virmidi,snd_emu10k1,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_hwdep,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
emu10k1_gp  2688  0 
gameport   10700  2 emu10k1_gp
shpchp 25528  0 
pci_hotplug23460  1 shpchp
soundcore   6368  2 snd
button  6096  0 
amd64_agp   8772  1 
agpgart28776  1 amd64_agp
evdev   8000  3 
usbhid 35904  0 
hid33184  1 usbhid
ff_memless  4392  1 usbhid
ext3  105512  1 
jbd39444  1 ext3
mbcache 7108  1 ext3
ide_disk   10496  0 
ide_cd_mod 27652  0 
cdrom  30176  1 ide_cd_mod
sd_mod 22200  4 
floppy 47748  0 
uhci_hcd   18672  0 
ehci_hcd   28396  0 
usbcore   118224  4 usbhid,uhci_hcd,ehci_hcd
via82cxxx   6948  0 [permanent]
ohci1394   24944  0 
sata_via6980  3 
ata_generic 4676  0 
libata140416  2 sata_via,ata_generic
scsi_mod  129324  2 sd_mod,libata
dock8304  1 libata
ieee1394   75800  1 ohci1394
ide_pci_generic 3908  0 [permanent]
ide_core   96136  4 ide_disk,ide_cd_mod,via82cxxx,ide_pci_generic
r8169  23684  0 
thermal15228  0 
processor  32544  1 thermal
fan 4164  0 
thermal_sys10856  3 thermal,processor,fan
loop   55372  1 

-- /etc/kernel-img.conf
do_symlinks = no
relative_links = yes
do_bootloader = no
do_bootfloppy

Bug#523477: kile: syntax highlighting disappears when a file is reload

[Thomas Braun]

On Freitag, 10. April 2009, Petr Břeň wrote:
 Package: kile
 Verson: 1:2.1.0~svn949704-1

 When I edit a latex source file in Kile and I reload that file (by pressing
 F5), syntax highlighting for that file is disabled and has to be reenabled
 (by selecting it in tools - highlighting). This began after upgrade to
 this version. (The previous version, 1:2.0.3-1, was okay.)

 I use Qt 4.5.0-2 from experimental. My system is sid/experimental with
 2.6.29-1-amd64.

Hi,

This is a known kate bug. See https://bugs.kde.org/show_bug.cgi?id=179857.

bye,
thomas (member of kile dev team)



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

Bug#522599: [kile] Inverse dvi search causes status bar corruption

[Thomas Braun]

This is already fixed upstream in r943403.




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

Bug#519746: [kile] Opening Configure Shortcuts window pins CPU at 100%

[Thomas Braun]

Hi,

as upstream I can confirm this bug.
You can track the upstream bug at http://bugs.kde.org/show_bug.cgi?id=187342.

thanks for the reminder,
thomas



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

Bug#513234: kile: Imperfect figure environment generation

[Thomas Braun]

Hi,

I can't reproduce your bug here and looking at the code also gives no clue
where the error lies.

So please give a step by step instruction how to reproduce the bug.

Thanks,
Thomas (kile dev team)




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

Bug#489447: got also hit by this bug

[Thomas Braun]

Hi,

first of all I'm not a DD but a regular user.
Two days ago I also got hit by this bug and lost something like 30min of work.
Of course I could reproduce it, but reproducing it is not the problem.

It is the discouragement.

If you decide as a regular user to submit a bugreport (which is not so common 
for a user) and decide to invest some time to write the problem up, you don't 
want to get screwed up afterwards.
And if the user, after loosing his report, decides to not report the problem 
(which I would say is more than likely), the project itself looses.

IMHO this bug should be grave and therefore should be fixed for lenny.

Thanks for considering and happy holidays,
Thomas



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

Bug#509639: grub: splashimage shows stripe pattern and shifted colors in boot menu with correct xpm image

[Thomas Braun]

Package: grub
Version: 0.97-47
Severity: normal

*** Please type your report below this line ***
Hi,

yesterday I installed debian lenny from RC1 installer CDs from scratch. After 
fiddeling with the system a bit, I wanted to have this nice fancy splashimage 
feature from grub.

So I added a splashimage line to menu.lst (shown below).
In the boot menu it was displayed with stripe patterns on the 640x480 image.

With a closer look you see that there are dashes (8x1 pixels) displayed in 
wrong colors. These wrong dahes appear mostly in line 1, 16, 31, 46, ... 
(that means 1+n*15). Some of these lines conincide with the horizontal 
borders of grub's cursor bar.

The resulting stripe pattern remains always the same (even after several after 
reboots), but changes when a pixels is touched by grub's cursor bar.

There seems to be some kind of color shift happening to the wrong displayed 
dashes. The wrong displayed color is one of the 14 colors of the XPM image 
(or the foreground color or the background color as it is set in menu.lst). 
Mostly it's the next brighter color, but not always.

This color shifting can to some degree corrected by manual tweaking the colors 
of the xpm image with gimp.
This is of course not the way to proceed for the whole image.

I can attach a photograph of the boot screen if it helps to triage the bug.
Or do I have to blame the graphic card vendor only?

The problem occured also with different monitors (4:3 and 16:9 aspect ratios).
Using xpm images from grub-splashimages didn't change anything.


Thanks for your time and Happy Holidays,
Thomas Braun


lspci -vv output:
01:00.0 VGA compatible controller: ATI Technologies Inc RV635 PRO AGP
[Radeon HD 3650] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device 0028
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
TAbort- MAbort+ SERR- PERR- INTx-
Latency: 32 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: Memory at b000 (32-bit, prefetchable) [size=256M]
Region 1: I/O ports at b800 [size=256]
Region 2: Memory at cfef (32-bit, non-prefetchable) [size=64K]
Expansion ROM at cfec [disabled] [size=128K]
Capabilities: [50] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [58] AGP version 3.0
Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64-
HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW-
Rate=none



-- Package-specific info:

*** BEGIN /boot/grub/device.map
(hd0)   /dev/hda
*** END /boot/grub/device.map

*** BEGIN /proc/mounts
/dev/hda3 / ext3 rw,errors=remount-ro,data=ordered 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/menu.lst
# menu.lst - See: grub(8), info grub, update-grub(8)
#grub-install(8), grub-floppy(8),
#grub-md5-crypt, /usr/share/doc/grub
#and /usr/share/doc/grub-legacy-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not change this entry to 'saved' or your
# array will desync and will not let you boot your system.
default 1

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default 
entry
# (normally the first entry defined).
timeout 5

# Pretty colours
# color light-blue/black white/blue
splashimage=(hd0,2)/boot/grub/newimage.xpm.gz
# background = 0a090d
# foreground = 456a98


### PASSWORD LINE REMOVED ###
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line)  and entries protected by the
# command 'lock'
### PASSWORD LINE REMOVED ###
### PASSWORD LINE REMOVED ###
### PASSWORD LINE REMOVED ###

#
# examples
#
# title Windows 95/98/NT/2000
# root  (hd0,0)
# makeactive
# chainloader   +1
#
# title Linux
# root  (hd0,1)
# kernel/vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/hda1
title   Windows XP Professional
root(hd0,0)
savedefault
makeactive
chainloader +1


# This is a divider, added to separate the menu items below from the Debian
# ones.
title   
root


### BEGIN

Bug#509093: Kile autocompletion bug

[Thomas Braun]

tags 509093 upstream
thanks

Hi Arash,

this bug should be solved in the new 2.0.3 version of kile.
To verify that you can compile kile from source. 
Get it from kile.sf.net. Some compile help is available from 
http://kile.sourceforge.net/help.php.
If this doesn't resolve the issue, please tell me.

Hope that helps,
Thomas (member of kile dev team)



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

Bug#489618: branches/extragear/kde3/office/kile/kile

[Thomas Braun]

SVN commit 829223 by tbraun:

explicitly use bash as shell as we use quite a few non-standard commands
will be part of upcoming kile 2.0.2

CCMAIL: [EMAIL PROTECTED]


 M  +1 -1  configtester.cpp  
 M  +1 -1  test/runTests.sh  


--- branches/extragear/kde3/office/kile/kile/configtester.cpp #829222:829223
@@ -168,7 +168,7 @@
KILE_DEBUG()  Tester::runTests: destdir =   destdir  endl;
m_resultsFile = destdir + results.rc;
 
-   QString shellname = KGlobal::dirs()-findExe(sh);
+   QString shellname = KGlobal::dirs()-findExe(bash);
KILE_DEBUG()  Tester::runTests: shellname =   shellname  endl;
m_process = new KShellProcess(QFile::encodeName( shellname ));
if (! KileConfig::teXPaths().isEmpty())
--- branches/extragear/kde3/office/kile/kile/test/runTests.sh #829222:829223
@@ -1,4 +1,4 @@
-#!/bin/sh
+#!/bin/bash
 echo Kile System Check script...
 
 outfile=$1



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

Bug#484146: branches/extragear/kde3/office/kile

[Thomas Braun]

SVN commit 818345 by tbraun:

CCMAIL: [EMAIL PROTECTED]

re-establish the possibility of creating new files from the structure view, bug 
introduced in r791271


 M  +1 -0  ChangeLog  
 M  +18 -17kile/kilestructurewidget.cpp  


--- branches/extragear/kde3/office/kile/ChangeLog #818344:818345
@@ -3,6 +3,7 @@
 Fixes:
  - insert \item[] in description environments for smart newline (#161658),
  reported and fixed by Job Noorman
+ - fix regression in 2.0.1 inside structure view with opening files (debian 
#484146)
 
 Features:
  -
--- branches/extragear/kde3/office/kile/kile/kilestructurewidget.cpp 
#818344:818345
@@ -697,27 +697,28 @@
else
emit(fileOpen(url, QString::null));
}
-   else if( item-type() == KileStruct::Bibliography ){
-   fname = 
m_ki-checkOtherPaths(fi.dirPath(),fi.fileName(),KileInfo::bibinputs);
-   fi.setFile(fname);
-   url.setPath(fname);
-   if(fi.isReadable()){
-   emit(fileOpen(url, QString::null));
+   else{
+   QString otherFilename;
+
+   if( item-type() == KileStruct::Bibliography ){
+   otherFilename = 
m_ki-checkOtherPaths(fi.dirPath(),fi.fileName(),KileInfo::bibinputs);
}
-   }
-   else if( item-type() == KileStruct::Input ){
-   fname = 
m_ki-checkOtherPaths(fi.dirPath(),fi.fileName(),KileInfo::texinputs);
-   fi.setFile(fname);
-   url.setPath(fname);
+   else if( item-type() == KileStruct::Input ){
+   otherFilename = 
m_ki-checkOtherPaths(fi.dirPath(),fi.fileName(),KileInfo::texinputs);
+   }
+
+   fi.setFile(otherFilename);
+
if(fi.isReadable()){
+   url.setPath(otherFilename);
emit(fileOpen(url, QString::null));
}
-   }
-   else{
-   if ( KMessageBox::warningYesNo(this, 
i18n(Cannot find the included file. The file does not exist, is not readable 
or Kile is unable to determine the correct path to it. The filename causing 
this error was: %1.\nDo you want to create this file?).arg(fname), 
i18n(Cannot Find File))
-   == KMessageBox::Yes)
-   {
-   emit(fileNew(url));
+   else{
+   if ( KMessageBox::warningYesNo(this, 
i18n(Cannot find the included file. The file does not exist, is not readable 
or Kile is unable to determine the correct path to it. The filename causing 
this error was: %1.\nDo you want to create this file?).arg(fname), 
i18n(Cannot Find File))
+   == KMessageBox::Yes) {
+   url.setPath(fname);
+   emit(fileNew(url));
+   }
}
}
}



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

Bug#471441: upstream link

[Thomas Braun]

here is a link to the upstream bug:  
https://bugs.kde.org/show_bug.cgi?id=159127




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

Bug#471441: workaround

[Thomas Braun]

Hi,

this is a kate bug, and you get the same behaviour in kate. I will open a bug 
report against kate and reference it here.

You can (somehow) work around that you activate double quotes in 
configure-latex-general.

Now if you type  you get ` and from the next  you get ` in this way you 
can write and easy form of \glqq and \grqq and also use the auto brackets.



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

Bug#458512: syntax highlightning

[Thomas Braun]

Hello,

I committed some additions to the syntax highlightning concerning tabular-like 
environments.

They will be part of the next minor release.

Bye,
Thomas

PS: The best place to file these kind of ditribution independent bugs is 
bugs.kde.org.



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

Bug#448752: fixed for version 2.0

[Thomas Braun]

Hello,

this bug is due to the fact that version 1.9.x does not support texlive paths 
for the help.
This is fixed in the upcoming version 2.0.

Regards,
Thomas Braun



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

Bug#428706: Please add the latex package of linux-libertine

[Thomas Braun]

Package: linux-libertine
Version: 2.5.9-1
Severity: wishlist

Hello,

since version 2.5.9 there is a latex package available to use the fonts also in
latex.

But currently these files are missing from the debian package.

Thanks
Thomas Braun


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

Bug#260642: Don't use latex -src as default

[Thomas Braun]

tags 260642 wontfix upstream
thanks

Hello,

1.) latex -src does nasty things with the spacing and there can also be 
sensitive information in the DVI file.
So we won't make latex -src as default.

2.) The inverse search and forward dvi stuff is better documented now.

Thanks,
Thomas Braun
member of kile dev team


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

Bug#358863: syntax files

[Thomas Braun]

Hello,

we discussed the problem of the syntax files a while ago, with Fathi Boudra, 
and concluded that we as kile devs ensure that kde/trunk, kde/branch/3.5, 
kile/trunk and kile/branch/1.9 always have the same version of latex.xml.

So any update of kdelibs on your side should include the newest latex.xml from 
the kde svn.

But in the last update of kdelibs-data, version: 4:3.5.5a.dfsg.1-8 (Debian 
sid) is latex.xml v1.23 included and not the newest version of the kde 3.5 
branch (which is v1.25 and was committed 5 weeks) ago.

So how can we ensure in the future that users get the newest syntax files?

Thanks
Thomas Braun
member of kile dev team


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

Bug#317266: version too old

[Thomas Braun]

Hello,

version 1.7.1 is way too old and not supported by us anymore.
If you can reproduce the bug with 1.9.x please report back.

Thanks
Thomas Braun
member of kile dev team



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

Bug#314404: fixed in svn

[Thomas Braun]

tags 314404 fixed-upstream
thanks

Hello,

in the kile-svn we have included an approach which avoids this confusion.
It will be included in the 2.0 release of kile.

Thanks
Thomas Braun
member of kile dev team


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

Bug#406470: patch for openafs FIFO problem

[Thomas Braun]

On Friday 02 March 2007 11:10, Alexander Klauer wrote:
 I've patched and rebuilt the package (kile_1.9.3-1_i386.deb); it works both
 for me and the user who reported the problem to me: when the option is
 checked, kile no longer consumes all CPU time and an error message is
 printed to the konsole from which kile is started. Thank you very much.

Hello Alexander,

I'm glad to hear that. :)

@DD-responsible-for-kile:
I've spoken with other kile devs and we propose to include this patch into 
debian version of kile. What do you think?

 Unfortunately I can't give you AFS access, only the people from our
 university computing centre can do that.

No problem, if you try the patch it is enough.

Regards,
Thomas


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

Bug#406470: patch for openafs FIFO problem

[Thomas Braun]

On Tuesday 27 February 2007 10:46, Alexander Klauer wrote:
 1. Kile tries to create a FIFO and when this fails, it creates a regular
 file instead:

[snip]
 The regular file messes up the usual select/pipe semantics. It would be
 better (as a short term solution) to show the user a clean error message
 instead, something like Sorry, but this functionality is unavailable
 because the file system of your home directory does not support FIFOs.

Hello Alexander,

attached is a patch which should stop kile from making bullshit if there are 
no FIFOs.
It would be nice if you could try the patch, because I don't have an openafs 
filesystem here.
Or if I could get access to an openafs filesystem I can try it myself.

Thanks
Thomas
Index: kilelyxserver.cpp
===
--- kilelyxserver.cpp	(Revision 637808)
+++ kilelyxserver.cpp	(Arbeitskopie)
@@ -17,6 +17,7 @@
 #include sys/types.h
 #include stdlib.h //getenv
 #include unistd.h //read
+#include fcntl.h
 
 #include kilelyxserver.h
 #include kileactions.h
@@ -70,7 +71,7 @@ bool KileLyxServer::start()
 kdDebug()  Created notifier for   (*it)-name()  endl;
 			}
 			else
-kdDebug()  No notifier created fro   (*it)-name()  endl;
+kdDebug()  No notifier created for   (*it)-name()  endl;
 			++it;
 		}
 		m_running=true;
@@ -81,43 +82,61 @@ bool KileLyxServer::start()
 
 bool KileLyxServer::openPipes()
 {
+	kdDebug()  ===bool KileLyxServer::openPipes()===  endl;
+	
 	bool opened = false;
 	QFileInfo info;
 	QFile *file;
+	struct stat buf;
+	struct stat *stats = buf;
+	mode_t perms = S_IRUSR | S_IWUSR | S_IRGRP| S_IROTH;
 
 	for (uint i=0; i  m_pipes.count(); ++i)
 	{
 		info.setFile(m_pipes[i]);
-		if ( ! info.exists() )
+		if ( !info.exists() )
 		{
-			mode_t perms = S_IRUSR | S_IWUSR | S_IRGRP| S_IROTH;
 			//create the dir first
 if ( ! QFileInfo(info.dirPath(true)).exists() )
-if (mkdir(QFile::encodeName( info.dirPath() ), perms | S_IXUSR) == -1)
-	perror( Could not create directory for pipe );
+if ( mkdir(QFile::encodeName( info.dirPath() ), perms | S_IXUSR) == -1 )
+{
+	kdError()  Could not create directory for pipe  endl;
+	continue;
+}
 else
 	kdDebug()  Created directory   info.dirPath()  endl;
 
-			if (mkfifo(QFile::encodeName( m_pipes[i] ), perms) == -1)
-   perror( Could not create pipe );
+			if ( mkfifo(QFile::encodeName( m_pipes[i] ), perms) != 0 )
+			{
+kdError()  Could not create pipe:   m_pipes[i]  endl;
+continue;
+			}
 			else
-kdDebug()  Created pipe   m_pipes[i]  endl;
+kdDebug()  Created pipe:   m_pipes[i]  endl;
 		}
 
 		file  = new QFile(info.absFilePath());
-		if (!file-open(IO_ReadWrite))
+		info.refresh();
+		if( info.exists()  file-open(IO_ReadWrite) ) // in that order we don't create the file if it does not exist
 		{
-			kdError()  Could not open   info.absFilePath()  endl;
+			kdDebug()  Opened file:   info.absFilePath()  endl;
+			fstat(file-handle(),stats);
+			if( !S_ISFIFO(stats-st_mode) )
+			{
+kdError()  The file we just created is not a FIFO, perhaps we are on some strange filesystem!?  endl;
+file-close();
+continue;
 		}
 		else
-		{
-			kdDebug()  Opened   info.absFilePath()  endl;
+			{	// everything is correct :)
 			m_pipeIn.append(file);
 			m_file.insert(file-handle(),file);
 			opened=true;
 		}
 	}
-
+		else
+			kdError()  Could not open   info.absFilePath()  endl;
+	}
 	return opened;
 }
 

Bug#406470: not reproducible here

[Thomas Braun]

On Tuesday 27 February 2007 10:46, Alexander Klauer wrote:
 Hi Thomas,


 (no reply-to was set; do you need CC:'s in the future?)

Hi Alexander,

no I don't need CC:'s because I'm subscribed to all kile bugs in debian.

 Thomas Braun:
- Do you have this behjavour always (or only after a start and stop
cycle of kile)?
  
   What do you mean by start and stop cycle? Anyway, when I check the
   option, kile immediately starts hogging, when I uncheck it, kile
   immediately behaves normally again.
 
  With start stop cycle I meant, quitting kile and then restarting kile.

 I see. Nope, a start-stop cycle is not required.

thanks.

- Do you have your home on a local device, or some remote stuff (nfs,
openafs, smb, or similiar)
  
   The home dirs are in OpenAFS.
 
  I think we found the culprit :)
 
  Kile is using a fifo to be able to insert tags from lyx-compliant apps
  (This means e.g. gbib writes a bibtex reference to .lyxpipe.in and then
  kile gets notified and inserts the reference).
  But according to
  http://www.dementia.org/twiki/bin/view/AFSLore/UsageFAQ#2_13_Can_I_create
 _a _fifo_aka_nam Fifos are not supported by OpenAFS :(
 
  Currently I don't know a solution but I will ask some other kile devs for
  help.

 Well, that explains things. If I may make two suggestions:

 1. Kile tries to create a FIFO and when this fails, it creates a regular
 file instead:

 [pid  4968] 09:58:11.419907 mknod(/afs/.../home/xxx/.lyxpipe.in, S_IFIFO|
 0644) = -1 EPERM (Operation not permitted)
 [pid  4968] 09:58:11.419981 dup(2)  = 13
 [pid  4968] 09:58:11.420047 fcntl64(13, F_GETFL) = 0x8001 (flags O_WRONLY|
 O_LARGEFILE)
 [pid  4968] 09:58:11.420102 close(13)   = 0
 [pid  4968] 09:58:11.420138 write(2, Could not create pipe : Operatio...,
 48Could not create pipe : Operation not permitted) = 48
 [pid  4968] 09:58:11.420257 open(/afs/.../home/xxx/.lyxpipe.in, O_RDWR|
 O_LARGEFILE) = -1 ENOENT (No such file or directory)
 [pid  4968] 09:58:11.420326 open(/afs/.../home/xxx/.lyxpipe.in, O_RDWR|
 O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 13

Well actually kile really creates a regular file but due to some unfortunate 
testing after the creation of the fifo.
I try to prepare a short term fix and add point two to the kile 2.0 TODO 
list :)

 The regular file messes up the usual select/pipe semantics. It would be
 better (as a short term solution) to show the user a clean error message
 instead, something like Sorry, but this functionality is unavailable
 because the file system of your home directory does not support FIFOs.

 2. (long-term solution) Place the FIFO somewhere where they are supported
 for sure, e.g. in /tmp/kde-username/.

Thanks a lot,
Thomas


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

Bug#406470: not reproducible here

[Thomas Braun]

On Monday 26 February 2007 11:44, Alexander Klauer wrote:
 Hi Thomas,

Hi Alexander,

 sorry for answering so late. I haven't received your answer by mail, only
 just saw it in the BTS.

no problem, I only thought we got rid of this problem ;)

 copy  paste:
  I would need some further information:
  - Do you have this behjavour always (or only after a start and stop cycle
  of kile)?

 What do you mean by start and stop cycle? Anyway, when I check the
 option, kile immediately starts hogging, when I uncheck it, kile
 immediately behaves normally again.

With start stop cycle I meant, quitting kile and then restarting kile.

  - Or only after having other programs used this feature?

 What feature? The user in question does not use LyX or latex directly.

Yes this was the question :)

  - Can you give the output of ls -la .lyx .lyxpipe.* in your home
  directory of the user issuing kile.ls -la .lyx .lyxpipe.*

 In my home dir:
 $ ls: .lyxpipe.*: No such file or directory
 .lyx:
 total 10
 drwxr--r--  2 xxx xxx 2048 2007-02-26 11:38 .
 drwxr-xr-x 82 xxx xxx 8192 2007-02-26 11:38 ..

 In the user's home dir:
 $ ls -la .lyx .lyxpipe.*
 ls: .lyxpipe.*: No such file or directory
 .lyx:
 total 77
 drwxr-xr-x 15   xxx xxx  2048 2007-01-11 17:47 .
 drwxrwxr-x 61 xxx xxx  6144 2007-02-23 16:15 ..
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 bind
 -rw-r--r--  1   xxx xxx  2960 2006-01-09 12:45 bstFiles.lst
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 clipart
 -rw-r--r--  1   xxx xxx  2310 2006-01-09 12:45 clsFiles.lst
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:46 doc
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 examples
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 help
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 images
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 kbd
 -rw-r--r--  1   xxx xxx35 2006-10-10 16:01 lastfiles
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 layouts
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 reLyX
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 scripts
 -rw-r--r--  1   xxx xxx 36262 2006-01-09 12:45 styFiles.lst
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 templates
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:43 ui
 drwxr-xr-x  2   xxx xxx  2048 2006-01-09 12:46 xfonts

 (Note that the problem is reproducible for both me and the user.)

  - Do you have your home on a local device, or some remote stuff (nfs,
  openafs, smb, or similiar)

 The home dirs are in OpenAFS.

I think we found the culprit :)

Kile is using a fifo to be able to insert tags from lyx-compliant apps (This 
means e.g. gbib writes a bibtex reference to .lyxpipe.in and then kile gets 
notified and inserts the reference).
But according to 
http://www.dementia.org/twiki/bin/view/AFSLore/UsageFAQ#2_13_Can_I_create_a_fifo_aka_nam
Fifos are not supported by OpenAFS :(

Currently I don't know a solution but I will ask some other kile devs for 
help.

Thanks
Thomas Braun


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

Bug#406470: not reproducible here

[Thomas Braun]

Hello,

I had a look on the affected code but I didn't sav any obvious errors.
I also can't confirm the bug here on debian testing.

I would need some further information:
- Do you have this behjavour always (or only after a start and stop cycle of 
kile)?
- Or only after having other programs used this feature?
- Can you give the output of ls -la .lyx .lyxpipe.* in your home directory 
of the user issuing kile.
- Do you have your home on a local device, or some remote stuff (nfs, openafs, 
smb, or similiar)

Thanks,
Thomas Braun (member of the kile team)


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

Bug#359872: solution for unstable

[Thomas Braun]

Hi,

this bug is a distribution specific one.

We have hardcoded the help path in kile.kcfg with /usr/share/texmf/doc.

This works for some distributions, for others not.

For debian unstable one should change this to /usr/share/doc/tetex-doc and 
have tetex-doc installed.

My suggested patch is:

Index: kile.kcfg
===
--- kile.kcfg   (Revision 595301)
+++ kile.kcfg   (Arbeitskopie)
@@ -207,7 +207,7 @@
group name=Help
entry name=location type=String
labelLocation of the TeX documentation./label
-   default/usr/share/texmf/doc/default
+   default/usr/share/doc/tetex-doc/default
/entry
entry name=use type=Int
labelUse the system's TeX reference for the 
contextual help./label


Regards,
Thomas


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

Bug#325588: works here

[Thomas Braun]

Hello Tobias,

can you give an detailed step by step guide how to get kile crash (or loose 
data).
Including all opened documents,projects, modified, unmodified docs etc. pp.

I've tried here with 1.9.2 (selfcompiled on debian unstable) but didn't 
succeeded.

Thanks
Thomas Braun
(member of kile dev team)


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

Bug#358251: Fixed

[Thomas Braun]

Already fixed in kile 1.9.


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

Bug#319409: Known problem in all kile versions

[Thomas Braun]

tags 319409 fixed-upstream

Hello,

the problem you described is known to apply to all versions of kile.
It is fixed in our subversion repository in the HEAD branch only.

Thanks,
Thomas Braun (member of kile-dev team)


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

Bug#344842: applies not to kile 1.9 anymore

[Thomas Braun]

The scrltx check is obsolete for latex distributions newer than Tetex 2.0 (so 
all that kile compiles on)
To use the package you have to add the path $HOME/.TeX to your TEXINPUTS 
variable.

regards,
Thomas Braun (member of kile-dev team)


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

Bug#325618: Already fixed in kile 1.9.

[Thomas Braun]

Fixed in kile version 1.9.
If you can still reproduce the error be sure to report back.

regards,
Thomas Braun (member of kile-dev team)


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

Bug#337550: bug is not fixed

[Thomas Braun]

Hello,

due to some reason I don't know this bug still applies to 1.9.1.
I just found it again and now have really commited a fix.

So this bug can be considered fixed-upstream.

Sorry for the inconvenience,
Thomas Braun


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

Bug#361375: tetex-base: [dvips] Unable to create fonts for commands from the textcomp package

[Thomas Braun]

Am Saturday 08 April 2006 16:43 schrieb Hilmar Preusse:
  [EMAIL PROTECTED]:~$ls -dl /var/cache/fonts/pk/ljfour/jknappen/tc/
  drwxrwsr-t 2 root users 4096 2006-04-08
  13:06 /var/cache/fonts/pk/ljfour/jknappen/tc/

 Well, the dir is only writeable as normal user if you're a member of
 the group users. Unfortunately this is not the default in Debian.
 During upgrading of tex-common you should have been informed about
 that. If not, please call back.
 Further: getting a member of group users should fix that bug.

Hello,

okay I added myself to the users group and now it works.

Because of the getting informed.
I issued apt-get install --reinstall tex-common and got nothing which said 
that I can expect problems.
In /usr/share/doc/tex-common/README.Debian is this explicitly written down, 
but some message from postinst or a mail to the system account would be 
better.

Thanks
Thomas


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

Bug#361375: tetex-base: [dvips] Unable to create fonts for commands from the textcomp package

[Thomas Braun]

Package: tetex-base
Version: 3.0-17
Severity: normal

Hello,

I compiled a latex file with arrow symbols from the textcomp package.
The font generation stuff for dvips failed and the log message stated that it 
could not write to
/var/cache/fonts/pk/ljfour/jknappen/tc/ and therefore I only had black
boxes in the ps file.
I then exectued the commands in missfont.log as root and I finally had
the fonts (but this is really not the way one should do it).
Btw, I upgraded from sarge (with tetex3 backports) to unstable, so this
can be also an upgrade problem.

Thanks for your good work

Thomas Braun

directory info:
[EMAIL PROTECTED]:~$ls -dl /var/cache/fonts/pk/ljfour/jknappen/tc/
drwxrwsr-t 2 root users 4096 2006-04-08 
13:06 /var/cache/fonts/pk/ljfour/jknappen/tc/


##
minimal input file

\documentclass[a4paper,10pt]{article}
\usepackage{textcomp}
\usepackage[T1]{fontenc}

\begin{document}

\textdownarrow
\textrightarrow
\textleftarrow
\textuparrow


\end{document}

##

other files

log file (from within kile)

*
* LaTeX output: 
* cd '/home/thomas/devel/svn/office-trunk/kile/kile/symbols'
* latex -src -interaction=nonstopmode 'arrows.tex'
*
This is pdfeTeXk, Version 3.141592-1.21a-2.2 (Web2C 7.5.4)
 Source specials enabled.
 entering extended mode
 (./arrows.tex
 LaTeX2e 2003/12/01
 Babel v3.8d and hyphenation patterns for american, french, german,
 ngerman, b
 ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch,
 esperanto, e
 stonian, finnish, greek, icelandic, irish, italian, latin, magyar,
 norsk, polis
 h, portuges, romanian, russian, serbian, slovak, slovene, spanish,
 swedish, tur
 kish, ukrainian, nohyphenation, loaded.
 (/usr/share/texmf-tetex/tex/latex/base/article.cls
 Document Class: article 2004/02/16 v1.4f Standard LaTeX document class
 (/usr/share/texmf-tetex/tex/latex/base/size10.clo))
 (/usr/share/texmf-tetex/tex/latex/amsfonts/amssymb.sty
 (/usr/share/texmf-tetex/tex/latex/amsfonts/amsfonts.sty))
 (/usr/share/texmf-tetex/tex/latex/base/textcomp.sty
 (/usr/share/texmf-tetex/tex/latex/base/ts1enc.def))
 (/usr/share/texmf-tetex/tex/latex/base/fontenc.sty
 (/usr/share/texmf-tetex/tex/latex/base/t1enc.def)) (./definitions.tex)
 (./arrows.aux) (/usr/share/texmf-tetex/tex/latex/base/ts1cmr.fd)
 (/usr/share/texmf-tetex/tex/latex/amsfonts/umsa.fd)
 (/usr/share/texmf-tetex/tex/latex/amsfonts/umsb.fd) [1] (./arrows.aux)
 )
 Output written on arrows.dvi (1 page, 536 bytes).
 Transcript written on arrows.log.
 *
 * DVItoPS output: 
 * cd '/home/thomas/devel/svn/office-trunk/kile/kile/symbols'
 * dvips -o 'arrows.ps' 'arrows.dvi'
 *
 This is dvips(k) 5.95a Copyright 2005 Radical Eye Software
 (www.radicaleye.com)
 ' TeX output 2006.04.08:1123' - arrows.ps
 kpathsea: Running mktexpk --mfmode ljfour --bdpi 600 --mag 1+0/600
 --dpi 600 tcrm1000
 mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600;
 nonstopmode; input tcrm1000
 This is METAFONT, Version 2.71828 (Web2C 7.5.4)
 (/usr/share/texmf-tetex/fonts/source/jknappen/tc/tcrm1000.mf
 (/usr/share/texmf-tetex/fonts/source/jknappen/ec/exbase.mf)
 (/usr/share/texmf-tetex/fonts/source/jknappen/tc/tcrm.mf
 (/usr/share/texmf-tetex/fonts/source/jknappen/tc/txsymb.mf
  Ok (/usr/share/texmf-tetex/fonts/source/jknappen/ec/exaccess.mf
   Ok) (/usr/share/texmf-tetex/fonts/source/jknappen/tc/txpseudo.mf
Ok) (/usr/share/texmf-tetex/fonts/source/jknappen/tc/txaccent.mf
 Ok [0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [27]
 [29])
 (/usr/share/texmf-tetex/fonts/source/jknappen/tc/txgen.mf
  Ok [100] [109] [98] [99] [108])
  (/usr/share/texmf-tetex/fonts/source/jknappen/tc/txsymbol.mf
   Ok [13] [18] [21] [22] [23] [24] [25] [26] [28] [31] [32] [36]
   [39] [44]
   [45] [46] [42] [47] [60] [61] [62] [77] [79] [87] [110] [91] [93]
   [94] [95]
   [96] [126] [127] [128] [129] [130] [131] [132] [133] [134] [135]
   [136] [137]
   [138] [139] [140] [141] [142] [143] [144] [145] [146] [147] [148]
   [149]
   [150] [151] [152] [153] [154] [155] [156] [157] [158] [159] [160]
   [161]
   [162] [163] [164] [165] [166] [167] [168] [169] [171] [172] [173]
   [174]
   [175] [177] [176] [180] [181] [182] [183] [184] [187] [191] [214]
   [246])
   (/usr/share/texmf-tetex/fonts/source/jknappen/tc/txromod.mf
Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57])
(/usr/share/texmf-tetex/fonts/source/jknappen/tc/txrsuper.mf
 Ok [185] [178] [179] [170] [186])
 (/usr/share/texmf-tetex/fonts/source/jknappen/tc/txrfract.mf
  Ok [188] [189] [190]) ) ) )
  (some charht values had to be adjusted by as much as
  0.06943pt)
  Font metrics written on tcrm1000.tfm.
  Output written on tcrm1000.600gf (128 characters, 23728
  bytes).
  Transcript written on tcrm1000.log

Bug#358857: kile: new upstream version

[Thomas Braun]

Package: kile
Version: 1:1.7.1-3
Severity: wishlist

Hi,

since a few days kile 1.9 is out, http://kile.sourceforge.net/download.php.
Would be nice to have it in unstable :)

Thanks
Thomas Braun


-- System Information:
Debian Release: 3.1
  APT prefers stable
  APT policy: (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.15-1-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages kile depends on:
ii  kdelibs4  4:3.3.2-6.4KDE core libraries
ii  konsole   4:3.3.2-1sarge1KDE X terminal emulator
ii  libart-2.0-2  2.3.17-1   Library of functions for 2D 
graphi
ii  libc6 2.3.2.ds1-22   GNU C Library: Shared libraries 
an
ii  libfam0c102   2.7.0-6sarge1  client library to control the FAM
ii  libgcc1   1:3.4.3-13 GCC support library
ii  libice6   6.9.0.dfsg.1-3bpo1 Inter-Client Exchange library
ii  libidn11  0.5.13-1.0 GNU libidn library, 
implementation
ii  libjpeg62 6b-10  The Independent JPEG Group's JPEG
ii  libpcre3  4.5-1.2sarge1  Perl 5 Compatible Regular 
Expressi
ii  libpng12-01.2.8rel-1 PNG library - runtime
ii  libqt3c102-mt 3:3.3.4-3  Qt GUI Library (Threaded runtime 
v
ii  libsm66.9.0.dfsg.1-3bpo1 X Window System Session 
Management
ii  libstdc++51:3.3.5-13 The GNU Standard C++ Library v3
ii  libx11-6  6.9.0.dfsg.1-3bpo1 X Window System protocol client 
li
ii  libxext6  6.9.0.dfsg.1-3bpo1 X Window System miscellaneous 
exte
ii  libxrender1   1:0.9.0.2-0bpo1X Rendering Extension client 
libra
ii  tetex-bin 3.0-14bpo1 The teTeX binary files
ii  xlibs 6.9.0.dfsg.1-3bpo1 X Window System client libraries 
m
ii  zlib1g1:1.2.2-4.sarge.2  compression library - runtime

-- no debconf information


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

Bug#358863: kile: don't delete the shipped syntax files

[Thomas Braun]

Package: kile
Version: 1:1.7.1-3
Severity: wishlist

Hi,

I'm mailing on the behalf of the kile dev team.
We had some discussion on the mailinglist about if or not kile's own syntax 
files (latex.xml and bibtex.xml) should be used instead of the ones in 
kdelibs (see 
http://sourceforge.net/mailarchive/forum.php?thread_id=9874362forum_id=34317)
Because the syntax files of kile are usually newer and also work for every KDE 
between 3.2.x and 3.5.x, we concluded that it would be best if they got 
installed and not removed as it is now.
The syntax files in kdelibs are also maintained by us, but because of our own 
release cylces we are not able to keep both versions the same.

Please think about this suggestion.

Thanks
Thomas Braun  The Kile dev team

-- System Information:
Debian Release: 3.1
  APT prefers stable
  APT policy: (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.15-1-k7
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages kile depends on:
ii  kdelibs4  4:3.3.2-6.4KDE core libraries
ii  konsole   4:3.3.2-1sarge1KDE X terminal emulator
ii  libart-2.0-2  2.3.17-1   Library of functions for 2D 
graphi
ii  libc6 2.3.2.ds1-22   GNU C Library: Shared libraries 
an
ii  libfam0c102   2.7.0-6sarge1  client library to control the FAM
ii  libgcc1   1:3.4.3-13 GCC support library
ii  libice6   6.9.0.dfsg.1-3bpo1 Inter-Client Exchange library
ii  libidn11  0.5.13-1.0 GNU libidn library, 
implementation
ii  libjpeg62 6b-10  The Independent JPEG Group's JPEG
ii  libpcre3  4.5-1.2sarge1  Perl 5 Compatible Regular 
Expressi
ii  libpng12-01.2.8rel-1 PNG library - runtime
ii  libqt3c102-mt 3:3.3.4-3  Qt GUI Library (Threaded runtime 
v
ii  libsm66.9.0.dfsg.1-3bpo1 X Window System Session 
Management
ii  libstdc++51:3.3.5-13 The GNU Standard C++ Library v3
ii  libx11-6  6.9.0.dfsg.1-3bpo1 X Window System protocol client 
li
ii  libxext6  6.9.0.dfsg.1-3bpo1 X Window System miscellaneous 
exte
ii  libxrender1   1:0.9.0.2-0bpo1X Rendering Extension client 
libra
ii  tetex-bin 3.0-14bpo1 The teTeX binary files
ii  xlibs 6.9.0.dfsg.1-3bpo1 X Window System client libraries 
m
ii  zlib1g1:1.2.2-4.sarge.2  compression library - runtime

-- no debconf information


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

Bug#337550: fixed already in svn

[Thomas Braun]

Hi,

this bug doesn't apply to current svn version.
So there is no need to forward the bug.

Regards
Thomas Braun


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

Bug#338807: dvipng: please package new version 1.7

[Thomas Braun]

Package: dvipng
Version: 1.5-2
Severity: wishlist

Hi,

with version 1.7 one now gets transparent pngs. This doensn't work with
the current version in debian.

Thanks
Thomas Braun

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.12-sc
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages dvipng depends on:
ii  libc6  2.3.2.ds1-22  GNU C Library: Shared libraries 
an
ii  libfreetype6   2.1.7-2.4 FreeType 2 font engine, shared 
lib
ii  libgd2-noxpm   2.0.33-1.1GD Graphics Library version 2 
(wit
ii  libkpathsea3   2.0.2-30  path search library for teTeX 
(run
ii  libpng12-0 1.2.8rel-1PNG library - runtime
ii  libt1-55.0.2-3   Type 1 font rasterizer library - 
r
ii  zlib1g 1:1.2.2-4.sarge.2 compression library - runtime

-- no debconf information


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

Bug#318606: works for me

[Thomas Braun]

Hi,

I did the following:

apt-get source mldonkey-server (from unstable of course)
cd mldonkey-2.5.28.1
dpkg-buildpackage -us -uc -b -rfakeroot
su
dpkg -i ../mldonkey-server_2.5.28.1-1_i386.deb

answered the questions.

/etc/init.d/mldonkey-server stop
cd mldonkey-2.6.4-CVS-09-18-05
cp mlnet /usr/bin/
/etc/init.d/mldonkey-server start

and everything works fine.

So this sould have been somekind of temporary bug somewhere.

Greetings
Thomas Braun





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

Bug#330083: update-grub should ensure that the default $number line is updated

[Thomas Braun]

Package: grub
Version: 0.95+cvs20040624-17
Severity: wishlist
Tags: patch

Hi,

I modified the update-grub script to ensure that the next booted kernel
is the one with default $number choosen. At the moment if you install
a new kernel, you have to adjust the number yourself.
With this patch it is possible, that this will be done automatically.

Greetings
Thomas Braun

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (50, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.12-sc
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages grub depends on:
ii  libc6   2.3.2.ds1-22 GNU C Library: Shared libraries 
an
ii  libncurses5 5.4-4Shared libraries for terminal
hand

-- no debconf information


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

Bug#330083: attachement forgotten

[Thomas Braun]

Here is the diff.
--- /sbin/update-grub	2005-04-19 02:38:00.0 +0300
+++ update-grub.final-1	2005-09-25 17:58:59.0 +0300
@@ -301,6 +301,9 @@
 # should grub create a memtest86 entry
 	memtest86=true
 
+# should update-grub remember the default entry
+	keepdefaultentry=false
+
 # stores the command line arguments
 	command_line_arguments=$1
 
@@ -556,6 +559,14 @@
 	echo  $buffer
 }
 
+set_default_value() {
+
+value=$1
+newmenu=$(tempfile)
+sed -e s/^[[:blank:]]*default[[:blank:]]*[[:digit:]]*\(.*\)/default ${value}\1/;b $menu  $newmenu
+mv $newmenu $menu # not nice
+unset newmenu
+}
 
 echo -n Testing for an existing GRUB menu.list file... 
 
@@ -594,6 +605,10 @@
 	esac
 fi
 
+# Extract the keepdefaultentry option
+keepdefaultentry=$(GetMenuOpt keepdefaultentry $keepdefaultentry)
+#echo keepdefaultentry is $keepdefaultentry
+
 # Extract the kernel options to use
 kopt=$(GetMenuOpt kopt $kopt)
 
@@ -651,6 +666,11 @@
 echo # alternative=$alternative  $buffer
 echo  $buffer
 
+echo ## should update-grub adjust the value of the default booted system  $buffer
+echo ## can be true or false  $buffer
+echo # keepdefaultentry=$keepdefaultentry  $buffer
+echo  $buffer
+
 echo ## should update-grub lock alternative automagic boot options  $buffer
 echo ## e.g. lockalternative=true  $buffer
 echo ##  lockalternative=false  $buffer
@@ -728,6 +748,22 @@
 	kernel_dir=
 fi
 
+if test $keepdefaultentry = true ; then
+	defaultEntryNumber=$(sed -ne 's/^[[:blank:]]*default[[:blank:]]*\([[:digit:]]*\).*/\1/p' $menu)
+#	echo Default entry is \$defaultEntryNumber\
+	if test -n $defaultEntryNumber; then
+#		echo Restoring old entry
+		defaultEntryNumberPlusOne=$(expr $defaultEntryNumber \+ 1);
+		defaultEntry=$(grep ^[[:blank:]]*title $menu | sed -ne ${defaultEntryNumberPlusOne}p | sed -ne ;s/^[[:blank:]]*title[[:blank:]]*//p)
+		defaultEntry=$(echo $defaultEntry | sed -e s/[[:blank:]]*$//) # don't trust trailing blanks
+#		echo Default entry title is \$defaultEntry\
+	else
+		notChangeDefault=yes
+	fi
+else
+		notChangeDefault=yes
+fi
+
 ## heres where we start writing out the kernel entries
 counter=0
 for kern in $sortedKernels ; do
@@ -824,5 +860,28 @@
 	cat $menu.new  $menu
 	rm -f $buffer $menu.new
 fi
+
+if test -z $notChangeDefault; then
+	echo
+	newDefaultNumberPlusOne=$(grep ^[[:blank:]]*title[[:blank:]]* $menu | grep -n ${defaultEntry} | cut -f1 -d : | sed -ne 1p)
+#	echo newDefaultNumberPlusOne is \$newDefaultNumberPlusOne\
+	if test -z $newDefaultNumberPlusOne; then
+		echo Previous default entry removed, resetting to 0
+		set_default_value 0
+	elif test -z $defaultEntry; then
+		echo Value of default value matches no entry, resetting to 0
+		set_default_value 0
+	else
+		if test $newDefaultNumberPlusOne = 1; then
+			newDefaultNumber=0
+		else
+			newDefaultNumber=$(expr $newDefaultNumberPlusOne - 1)
+		fi
+#		echo newDefaultNumber is $newDefaultNumber
+#		echo Adjusting default entry to $newDefaultNumber
+		set_default_value $newDefaultNumber
+	fi
+fi
+
 echo done
 echo

Bug#310381: loop-aes-source: leaves diversion in place on purge

[Thomas Braun]

Max Vozeler schrieb:
 Are you still seeing the leftover loop.ko-orig problem? That one was
 worrying me a bit, since it could mean that the system and diversions
 are left in an inconsistent state.

Hello,

I have tried to reproduce it  and have neither suceeded. So I would blame some 
kind of local misconfiguration/etc. pp.
In my eyes this bug can be closed. If I get the same error again I will 
certainly report it to this bug :)

Greetings
Thomas Braun


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

Bug#302324: loop-aes-source: initrd complains about missing module loop.ko_orig

[Thomas Braun]

Max Vozeler schrieb:
 Hi Thomas,

Hi Max,

 What happens here is that mkinitrd does not ignore non-.o/.ko/.gz
 modules as it probably should. The warning is just annoying though,
 it makes no difference for the initrd build in any way.

Not really:

inspecting the initrd (installation without error) gives me:

thomas:/mnt/no.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# ls
cciss.ko  cpqarray.ko  cryptoloop.ko  DAC960.ko  floppy.ko  loop.ko  
pktcdvd.ko  sx8.ko  umem.ko  xd.ko
thomas:/mnt/no.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# ls -l
insgesamt 372
-rw-r--r--  1 root root 52420 1970-01-01 01:00 cciss.ko
-rw-r--r--  1 root root 29880 1970-01-01 01:00 cpqarray.ko
-rw-r--r--  1 root root  5340 1970-01-01 01:00 cryptoloop.ko
-rw-r--r--  1 root root 84937 1970-01-01 01:00 DAC960.ko
-rw-r--r--  1 root root 79175 1970-01-01 01:00 floppy.ko
-rw-r--r--  1 root root 20745 1970-01-01 01:00 loop.ko
-rw-r--r--  1 root root 39039 1970-01-01 01:00 pktcdvd.ko
-rw-r--r--  1 root root 22584 1970-01-01 01:00 sx8.ko
-rw-r--r--  1 root root 20230 1970-01-01 01:00 umem.ko
-rw-r--r--  1 root root 23989 1970-01-01 01:00 xd.ko
thomas:/mnt/no.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# modinfo 
loop.ko
filename:   loop.ko
license:GPL
alias:  block-major-7-*
vermagic:   2.6.10-knoelk preempt K7 gcc-3.3
depends:
parm:   max_loop:Maximum number of loop devices (1-256)
thomas:/mnt/no.error/lib/modules/2.6.10-knoelk/kernel/drivers/block#

So I have the original kernel loop modul. (how sould mkinitrd know that one 
adds the loop-aes-modul package afterwards)

Installation with error:

thomas:/mnt/with.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# ls -l
total 440
-rw-r--r--  1 root root 84937 Jan  1  1970 DAC960.ko
-rw-r--r--  1 root root 52420 Jan  1  1970 cciss.ko
-rw-r--r--  1 root root 29880 Jan  1  1970 cpqarray.ko
-rw-r--r--  1 root root  5340 Jan  1  1970 cryptoloop.ko
-rw-r--r--  1 root root 79175 Jan  1  1970 floppy.ko
-rw-r--r--  1 root root 69611 Jan  1  1970 loop.ko
-rw-r--r--  1 root root 20745 Jan  1  1970 loop.ko-orig
-rw-r--r--  1 root root 39039 Jan  1  1970 pktcdvd.ko
-rw-r--r--  1 root root 22584 Jan  1  1970 sx8.ko
-rw-r--r--  1 root root 20230 Jan  1  1970 umem.ko
-rw-r--r--  1 root root 23989 Jan  1  1970 xd.ko
thomas:/mnt/with.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# modinfo 
loop.ko
filename:   loop.ko
license:GPL
alias:  block-major-7-*
vermagic:   2.6.10-knoelk preempt K7 gcc-3.3
depends:
parm:   lo_nice:Loop thread scheduler nice (0 ... -20)
parm:   lo_prealloc:Number of pre-allocated pages [,index,pages]...
parm:   max_loop:Maximum number of loop devices (1-256)
thomas:/mnt/with.error/lib/modules/2.6.10-knoelk/kernel/drivers/block# modinfo 
loop.ko-orig
filename:   loop.ko-orig
license:GPL
alias:  block-major-7-*
vermagic:   2.6.10-knoelk preempt K7 gcc-3.3
depends:
parm:   max_loop:Maximum number of loop devices (1-256)
thomas:/mnt/with.error/lib/modules/2.6.10-knoelk/kernel/drivers/block#   

So I have a different initrd. The latter one has the loop-aes loop modul.
Perhaps one should document this feature.


  These seems to be the consequence of the last bugfix.
  Going to $MODULDIR/block/drivers and issuing
  laptop:/lib/modules/2.6.10-nb/kernel/drivers/block# ls -l loop*
  -rw-r--r--  1 root root 20597 Mar 29 20:25 loop.ko-orig

 This one is confusing me.

 Just so I understand, when you purged the kernel image, was
 loop-aes installed? Did you purge loop-aes as well? Was loop-aes
 installed at the time you did ls above?

Now I got a method to show the error.

- Installed latest loop-aes-source 2.2d-5

- Clean /lib/modules
thomas:/lib/modules# ls -l
insgesamt 20
drwxr-xr-x  4 root root 4096 2005-04-03 18:46 2.4.27-grsec
drwxr-xr-x  5 root root 4096 2005-02-03 18:16 2.6.10-1-k7
drwxr-xr-x  5 root root 4096 2005-04-04 15:14 2.6.10-sc
drwxr-xr-x  4 root root 4096 2005-04-03 18:45 2.6.8-1-k7
drwxr-xr-x  4 root root 4096 2005-04-03 18:45 2.6.8-sc

The desired kernel will have version 2.6.10-knoelk.

- Installing the compiled kernel ( make-kpkg kernel_image --append-to-version 
\-knoelk modules_image --initrd ) and loop-aes-modules.
( I have these packages completly purged from the system before )

thomas:/usr/src# dpkg -i kernel-image-2.6.10-knoelk_10.00.Custom_i386.deb 
loop-aes-2.6.10-knoelk_2.2d-5+10.00.Custom_i386.deb
Selecting previously deselected package kernel-image-2.6.10-knoelk.
(Reading database ... 158381 files and directories currently installed.)
Unpacking kernel-image-2.6.10-knoelk (from 
kernel-image-2.6.10-knoelk_10.00.Custom_i386.deb) ...
Selecting previously deselected package loop-aes-2.6.10-knoelk.
Unpacking loop-aes-2.6.10-knoelk (from 
loop-aes-2.6.10-knoelk_2.2d-5+10.00.Custom_i386.deb) ...
Adding `diversion of /lib/modules/2.6.10-knoelk/kernel/drivers/block/loop.ko 
to 

Bug#281323: works with grub from sarge

[Thomas Braun]

Hello,

I'm using debian sarge with grub 0.95+cvs20040624-12.

The behavour of savedefault --once --default=N

is as expected. It boots the next time the N entry (starting from 0).

The way I achieved it:

run grub as root:

savedefault --once --default=N
quit

rebooted

worked

after the next reboot I had the default value from my menu.lst.

Greetings Thomas Braun

PS: I think #254475 is about the same issue.


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