Package: lxpanel
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: linus.luess...@c0d3.blue
Dear Maintainer,
On a Debian Sid system with "task-lxqt-desktop" and "task-lxde-desktop"
installed
an "apt-get dist-upgrade" has removed these packages and by that a large
list of
On Thu, Aug 31, 2017 at 11:39:17AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libreoffice-core package:
>
> #873443: terminate called after throwing an instance of
> com::sun::star::uno::DeploymentException
On Sat, Mar 04, 2017 at 07:37:36PM -0300, Felipe Sateler wrote:
> > Not really familiar with how binaries get created or uploaded in
> > Debian, but is it possible to determine the gcc + binutils
> > versions with which libsbc 1.3-1 and 1.3-1+b2 were created? Just
> > to double check whether the
> Are you sure it's definitely related to the gcc version? Did you actually
> try rebuilding with gcc-4.9 on the target machine?
>
> The thing is that assembly code is not interpreted by gcc but by the assembler
> which is part of the binutils package. Since binutils is updated
> in Debian very
On Fri, Mar 03, 2017 at 01:14:56PM -0300, Felipe Sateler wrote:
> It has been pointed out to me that this may be unrelated to PIE, but
> just caused by a newer GCC version. Could you check if disabling PIE
> makes the binary work again? To do so:
>
> apt-get source sbc
> sudo apt-get build-dep
On Thu, Nov 12, 2015 at 06:24:10PM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the torus-trooper package:
>
> #803216: torus-trooper: segfault on startup in src/abagames/tt/barrage.d:111
>
> It has been closed
Btw., if I simply remove the crashing line, the check, then
everything starts fine. Can it actually happen that this API
returns the same file name more than once for a specific
directory listing? Could this check be unnecessary, maybe?
Cheers, Linus
PS: I also don't understand why the
Package: torus-trooper
Version: 0.22.dfsg1-9
Severity: grave
Justification: renders package unusable
Hi,
I am currently unable to start torus-trooper as it crashes with a segmentation
fault. I have downloaded the source package (apt-get source torus-trooper),
rebuilt it (dpkg-buildpackage) and
Package: qgo
Version: 2.0~git-20131123-1
Severity: grave
Justification: renders package unusable
Hi,
Since the upgrade of qgo a couple of days ago, version
2.0~git-20130914-1 to 2.0~git-20131123-1, I'm not able to connect to any
Go server anymore. After clicking on Connect the list of servers is
Ok, I figured that it's not actually the servers having vanished.
Instead the layout of the Connect menu changed.
However, my credentials on IGS were deleted in qgo and I had to
readd them manually in the new menu (luckily I could still
remember them).
A migration path would have been nicer.
On Wed, Jan 01, 2014 at 10:01:05PM -0500, Ari Pollak wrote:
It seems unlikely that pidgin is at fault here, given that it hasn't
been updated in almost a year. Do you happen to have
gstreamer0.10-buzztard installed? Does this still happen if you remove it?
Yes, I had it installed and removing
Package: pidgin
Version: 2.10.7-2+b1
Severity: grave
Justification: renders package unusable
Hi,
Since my last dist-upgrade two days ago I'm not able to start pidgin
anymore, the console returns the following:
---
$ pidgin
zsh: illegal hardware instruction pidgin
---
And dmesg says:
---
Package: tor
Version: 0.2.3.25-1
Severity: grave
Justification: renders package unusable
Hi,
When trying to start Tor with this command, so starting it with the
Debian default torrc:
$ tor --defaults-torrc /usr/share/tor/tor-service-defaults-torrc
... then I'm getting the following error
Package: wine-unstable
Version: 1.5.6-1
Followup-For: Bug #677416
Hi,
I can't install wine-unstable either. Most issues seem to be conflicts
with the wine package (1.4.1-1) I'm having installed, too. But
libsasl2*:i386 seems to yield conflicts (with its *:amd64 counter parts,
maybe?), too.
See
Package: cryptsetup
Version: 2:1.0.7-2
Severity: normal
Yes, I'm having the same problem here. I updated cryptsetup yeseterday to
2:1.07-2 and now I can't boot my usual 2.6.30-1-amd64 anymore.
My other kernels on this machine seem unaffected, just my usual
kernel-image does not boot. So I can
15 matches
Mail list logo
