Bug#552994: mbrowse: Input handling prevents typing some characters

Package: mbrowse Version: 0.3.1-8 Severity: grave Justification: renders package unusable Since the GTK 2.x upgrade, mbrowse has become totally unusable - typing certain characters into the text input fields is impossible. This prevents me from entering certain hostnames or community strings.

Bug#566208: linux-image-2.6.26-2-486: e_powersaver causes constant lockups

Package: linux-image-2.6.26-2-486 Version: 2.6.26-19lenny2 Severity: critical Justification: breaks the whole system After upgrading linux-image-2.6.26-2-486 from 17lenny1 to 19lenny2, I started experiencing 100% reproducable system lockups on a VIA C7 system. No errors in the logs, no oops, no

Bug#571962: azureus: Fails to start with Azureus core already instantiated

-gtk-3.5-java fixed me up. Thanks for the info! Ross -- Ross Vandegrift r...@kallisti.us If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher. --Woody Guthrie signature.asc Description: Digital signature

Bug#560238: netbase: racoon is also broken by net.ipv6.bindv6only change

Package: netbase Version: 4.40 Severity: normal Hello, I recently had a VPN break and have traced it back to the net.ipv6.bindv6only change. When racoon initiates IKE, I can see the response packet from the IPSec responder but racoon never receives it. I disabled net.ipv6.bindv6only and

Bug#539752: emacs installs, but installs emacs23-nox

Package: emacs Version: 23.1+1-2 Severity: normal I updated my installation yesterday. I've had the emacs and emacs22 packages installed. The following happened: malaclypse:~# grep emacs /var/log/aptitude [INSTALL, DEPENDENCIES] emacs23-bin-common [INSTALL, DEPENDENCIES] emacs23-common

Bug#613752: Registers itself to open PDF and PostScript; ends up as the default

I recently hit this bug after an upgrade pulled in Gnome 3. Very annoying. Though I agree that this should be changed, see here for a workaround that's better than nothing: http://lists.debian.org/debian-user/2011/12/msg01372.html Ross signature.asc Description: This is a digitally signed

Bug#760038: [Pkg-e-devel] Bug#760038: minor problem subsists

On 10/08/2014 09:44 AM, Curtis Dean Smith wrote: Well, I've given up on e17 for the short term, although I went from stable to testing specifically for e17. I try once a week to see if something changed, but no luck. Have you tried disabling the login splash screen on the first login? This

Bug#878572: exactimage: FTBFS in experimental: gfx/X11Helper.hh:33:10: fatal error: Evas_Engine_Software_X11.h: No such file or directory

Source: exactimage Version: 1.0.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Control: affects -1 + edisplay Hello, exactimage fails to build against EFL 1.20 from experimental: In file included from gfx/X11Helper.cc:36:0:

Bug#878584: [Pkg-e-devel] Bug#878584: [libevas-dev] Missing dependency for libecore-dev

On Sun, Oct 15, 2017 at 01:20:05PM +0200, Andreas Metzler wrote: > Ross, could you apply and push the attached patch? Hmm, two concerns about this solution: 1) lintian finds a circular dependency libecore-dev libector-dev libeet-dev libeeze-dev libeina-dev libemile-dev libevas-dev I don't

Bug#877180: [Pkg-e-devel] Bug#877180: libector-dev: missing Depends: libector1 (= ${binary:Version})

On Sun, Oct 01, 2017 at 04:02:32PM +0200, Andreas Metzler wrote: > Control: tags -1 patch > > On 2017-09-29 Andreas Beckmann wrote: > > Package: libector-dev > > Version: 1.18.4-1 > > Severity: serious > > User: debian...@lists.debian.org > > Usertags: piuparts > > > > Hi, > >

Bug#881155: [Pkg-e-devel] Bug#881155: e17: Won't start correctly any longer, corrupted windows shown

Control: severity -1 important I'm not able to reproduce. This could be related to your video drivers. But since Enlightenment in buster is old an unmaintained, nothing can be done to fix it. The current Enlightenment release is available in Debian experimental - I'd encourage you to try that

Bug#884019: [Pkg-e-devel] Bug#884019: terminology: FTBFS if $HOME is not writable

Control: tags -1 pending On Sun, Dec 10, 2017 at 03:48:30PM +0100, Andreas Beckmann wrote: > same problem as in e17: Thanks, I've applied the fix from e17. Ross

Bug#883833: [Pkg-e-devel] Bug#883833: e17: FTBFS if $HOME is not writable

Control: tags -1 pending Looks good, patch applied. Ross On Fri, Dec 08, 2017 at 08:07:31AM +0100, Andreas Metzler wrote: > Control: tags -1 patch > > On 2017-12-08 Andreas Beckmann wrote: > > Source: e17 > > Version: 0.22.1-1 > > Severity: serious > > Justification: fails to

Bug#878584: [Pkg-e-devel] Bug#878584: [libevas-dev] Missing dependency for libecore-dev

On Mon, Oct 16, 2017 at 07:55:07PM +0200, Andreas Metzler wrote: > I have not yet read over the patch in detail, I just have three quick > notes: Thanks for the feedback. I've fixed these issues, but kept the transitional package for libelementary-dev. stable & sid have it, but it comes from

Bug#898384: terminology: focus weirdness in 1.2.0

Package: terminology Version: 1.2.0-1 Severity: serious terminology 1.2.0 easily gets stuck in a state where it doesn't receive keyboard events. This is triggered by switching keyboard focus away from terminology, and then back. Upstream discussion:

Bug#900460: ephoto: fails to start

Control: tags -1 moreinfo Hello, Can you provide the output of "dpkg -l | grep libevas1-engine"? It looks like ephoto can't find a working evas engine. Probably you're using X11 but the dependencies only installed the wayland engine, or vice versa. Thanks, Ross On Thu, May 31, 2018 at

Bug#900460: ephoto: fails to start

Control: clone -1 -2 Control: reassign -2 libevas1 Control: severity -2 normal Control: retitle -2 libevas1: adjust Depends to prefer X11 engine Control: block -1 by -2 On Fri, Jun 01, 2018 at 09:06:57AM +0900, Norbert Preining wrote: > > Can you provide the output of "dpkg -l | grep

Bug#878572: Bug#895511: exactimage FTBFS with libevas-dev 1.20.7

On Thu, Apr 12, 2018 at 10:38:55AM +0200, Sven Eckelmann wrote: > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/exactimage.html > > Thanks for bringing this up again. This is a long standing bug in > libevas-dev. > Increasing the severity for the libevas-dev bug now

Bug#895809: enlightenment: Fails to start

Control: severity -1 normal Control: tags -1 moreinfo > ESTART: 0.17880 [0.00119] - Compositor Init > Enlightenment Error > Enlightenment cannot initialize Ecore_X! Is X running? How are you starting enlightenment? Ross

Bug#895809: enlightenment: Fails to start

On Mon, Apr 16, 2018 at 06:09:27PM +0200, Manolo Díaz wrote: > On Monday, 16 Apr 2018 at 15:43 UTC > Ross Vandegrift wrote: > > > Control: severity -1 normal > > Control: tags -1 moreinfo > > > > > ESTART: 0.17880 [0.00119] - Compositor

Bug#916630: terminology: Remote execution via special escape codes that handle unknown media types

Package: terminology Version: 1.3.0-1 Severity: grave Tags: security upstream Justification: user security hole Owner: r...@kallisti.us Forwarded: https://phab.enlightenment.org/T7504 Terminology 1.3.1 has been released to fix a remote code execution vulnerability in special escape handling.

Bug#923889: google-compute-image-packages - DoS via serial console write

On Fri, Mar 08, 2019 at 10:59:33AM +0100, Bastian Blank wrote: > In normal operation, the rate limit of journald might make sure it does > not come to really blocking. Ahh, that would do it, thanks. > What happens for use cases where you need to disable this rate limit? > Mail servers which

Bug#923889: google-compute-image-packages - DoS via serial console write

On Wed, Mar 06, 2019 at 07:49:38PM +0100, Bastian Blank wrote: > This package instructs journald to duplicate everything sent to the > journal to the serial console. The serial console is a pretty rate > limited log output device and blocking there will make all software with > any log output

Bug#922669: sqlalchemy: CVE-2019-7164 CVE-2019-7548 (SQL injection)

On Mon, May 06, 2019 at 10:20:25AM +0200, Thomas Goirand wrote: > On 5/6/19 5:09 AM, Ross Vandegrift wrote: > > Source: sqlalchemy > > Version: 1.2.18+ds1 > > Followup-For: Bug #922669 > > > > I've confirmed that 1.2.18+ds1 is affected despite the description

Bug#922669: sqlalchemy: CVE-2019-7164 CVE-2019-7548 (SQL injection)

@@ -1,3 +1,10 @@ +sqlalchemy (1.2.18+ds1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add upstream patch for CVE-2019-7164, CVE-2019-7548 + + -- Ross Vandegrift Sun, 05 May 2019 19:46:35 -0700 + sqlalchemy (1.2.18+ds1-1) unstable; urgency=medium * New upstream release

Bug#927993: xinit: Cannot load NVIDIA drivers, doesn't connect to X server. No screens found.

Control: -1 tags moreinfo Hi Sebastian, Could you send the output of: dpkg -l '*nouveau*'? Probably the X server output would also be useful. That should be the output of xinit/startx if you use it directly, otherwise check ~/.local/xorg/ or /var/log/. Ross

Bug#931669: ephoto doesn't even start up

Control: severity -1 normal Hi Michael, I bet there's no rendering engine package installed. You can check with: dpkg -l libevas1-engines*. If so, installing libevas1-engines-x should fix the issue. Currently, ephoto Depends on libevas1, which Recommends libevas1-engines*. That can't be

Bug#951117: libecore1: .xsession-errors eats all disk space

Control: severity -1 normal Control: reassign -1 enlightenment 0.23.1-4 Control: retitle -1 eo logs in .xsession-errors eat all disk space On Tue, Feb 11, 2020 at 01:31:28PM +0300, sergio wrote: > Package: libecore1 > Version: 1.23.3-6 > Severity: critical > Justification: breaks unrelated

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

On Thu, May 07, 2020 at 07:52:31PM +0200, Julien Cristau wrote: > On Thu, May 07, 2020 at 09:48:34PM +1000, Dmitry Smirnov wrote: > > On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote: > > > This use of Provides is not acceptable. The systemctl package does not > > > in any way provide

Bug#968030: e17: FTBFS during combined arch+indep build

On Fri, Aug 07, 2020 at 01:17:29AM +0200, Andreas Beckmann wrote: > e17/experimental FTBFS during a combined binary arch+indep build (i.e. the > default dpkg-buildpackage mode), while it succeeds during separate arch and > indep builds (dpkg-buildpackage -B, dpkg-buildpackage -A; as done by the >

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

On Wed, May 20, 2020 at 12:48:18PM -0700, Ross Vandegrift wrote: > On Thu, May 07, 2020 at 07:52:31PM +0200, Julien Cristau wrote: > > On Thu, May 07, 2020 at 09:48:34PM +1000, Dmitry Smirnov wrote: > > > On Thursday, 7 May 2020 7:04:17 PM AEST Julien Cristau wrote: > >

Bug#957160: e17: ftbfs with GCC-10

Control: unblock -1 by 959828 Control: fixed -1 e17/0.24.1-2 Control: tags -1 fixed-in-experimental On Tue, Jun 09, 2020 at 10:17:21PM -0700, Ross Vandegrift wrote: > On Fri, Apr 17, 2020 at 10:59:16AM +, Matthias Klose wrote: > > The package fails to build in a test rebuild on at le

Bug#979100: Legally problematic GPL-3+ readline dependency

Control: tags -1 pending Hello, On Sat, 2 Jan 2021 18:47:07 +0100 Bastian Germann wrote: > This package depends on libreadline8 which is GPL-3+ licensed. According > to debian/copyright parts of your package are GPL-2-only licensed. If > that is also (transitively) the case for the binaries

Bug#1014662: cloud-initramfs-growroot: Initramfs hook does not include `flock` command

On Fri, Feb 17, 2023 at 09:54:08PM +0100, Santiago Vila wrote: > After applying the suggested patch, the reported error > does not show anymore. > > Instead, I get this: > > /scripts/local-bottom/growroot: line 97: wait-for-root: not found > > Where does this "wait-for-root" come from? > I

Bug#1040406: python3-azure-cli - fails with No module named 'azure.mgmt.compute.v2022_11_01'

Package: azure-cli Version: 2.45.0-1 Followup-For: Bug #1040406 X-Debbugs-Cc: rvandegr...@debian.org Hi Luca, I'm hitting this issue on azure-cli in bookworm. It sounds like this package is difficult - but is there any possibility of a stable update? $ az vm The command failed with an

Bug#1057548: cloud-init: FTBFS: failing tests

On Tue, Dec 05, 2023 at 11:04:12PM +0100, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build: I started updating to the latest upstream release, which fixes this FTBFS. But I'm reluctant to push to the team repo, due to an issue with the network

Bug#1057548: cloud-init: FTBFS: failing tests

Control: tags -1 pending On Mon, Feb 19, 2024 at 01:47:24PM -0800, Ross Vandegrift wrote: > On Tue, Dec 05, 2023 at 11:04:12PM +0100, Santiago Vila wrote: > > During a rebuild of all packages in unstable, your package failed to build: > > I started updating to the latest upstream