Am Montag, dem 17.03.2025 um 12:28 -0300 schrieb Santiago Ruano Rincón:
> My plan is to remove the /usr/include/opentelemetry/proto/ files from
> opentelemetry-cpp-dev. Looking into tango (the main opentelemetry
> reverse dependency), it only includes/need the header files from the
> C++
> client l
We just bricked a SSH-only accessible machine by installing the gdm3
package.
Why is that possible? As the OP already said even an active SSH
connection does not stop suspension.
This is a prime example of bad defaults.
Am Freitag, dem 08.11.2024 um 10:46 -0300 schrieb Santiago Ruano
Rincón:
[resending to bug, as the original mail only went to Santiago]
> Control: found -1 tango/9.3.4+dfsg1-2
>
> El 27/10/24 a las 12:28, Thomas Braun escribió:
> > > Santiago Ruano Rincón hat am 25.10.202
Am Donnerstag, dem 14.11.2024 um 22:59 +0100 schrieb Santiago Ruano
Rincón:
[...]
> > Thomas, may I ask you if omniorb should ship that configuration
file?
Yes i think this should be shipped.
> > If yes, is the library the correct binary package for that,
> > or should it be omniorb?
I think i
> Santiago Ruano Rincón hat am 25.10.2024 20:15 CEST
> geschrieben:
> Sorry for the noise. I can confirm there is an issue in bookworm, and it
> is present even without upgrading from bullseye. Which makes sense with
> https://gitlab.com/tango-controls/TangoDatabase/-/issues/69
>
> I will propos
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.
I'm also hitting a wall here as the cmake files are not present.
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'), (50
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 th
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 (GC
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!
Mainboa
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.
-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: +
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
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
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
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 a
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
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
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 prot
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 ol
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
But I'm using debian stable, so how can a transition in unstable break that?
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 ha
ain.
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,
> >
>
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 1
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 (loopbac
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
>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
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
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=rev&revision=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
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
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
On Mon, 24 Aug 2009 10:04:28 +0200, Fathi Boudra 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 KD
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 alternat
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
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
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
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...@li
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 s
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
: 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-spe
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
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
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
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 "un
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
sing 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 Compu
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
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
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:8183
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]
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
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]
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]
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
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 "unsubs
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]
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]
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
m
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 kons
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
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:
> > > > - D
mb, 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 accordin
r 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 U
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:
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
(memb
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]
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
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 "unsubs
Already fixed in kile 1.9.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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 subje
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
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
intained 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')
Architectur
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, 'uns
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')
Arc
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]
/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]
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"
+
# s
s 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_C
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]
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
orig.ko.old. So not ending upon .ko and there ignored by the
kernel. I don't know if the loop-aes modul has any disadvantages
compared to the original.
I didn't wanted to use a higher severity, because often the mistake is
in front of the monitor, but feel free to raise it.
Greetings Th
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]
85 matches
Mail list logo
