Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

[Jason Quinn]

I was also bitten by this bug with the Debian bookworm alpha1 era
installer. This is not a wishlist kind of bug; This is a bug of grave
severity. Breaking hibernation is unacceptable and is a key feature of
modern operating systems for both laptop and desktop users. If the
idea behind the 1GB default is to cater to the server world, then
somewhere the installer needs to either prompt the user to say what
kind of installation it is (desktop or server) or to offer a choice
between the two camps so the installer picks better defaults.

I completely don't understand the comments about hibernation not
working on x86. I'm going to disregard that unless there's a
clarification.

Thanks to Johannes (in Message #30) for suggesting a solution. Other
workarounds found on the web suggest tinkering with systemd's
SYSTEMD_BYPASS_HIBERNATION_MEMORY_CHECK variable and re-configuring
the GRUB menu (see
https://bbs.archlinux.org/viewtopic.php?pid=1928690#p1928690). I
haven't tried these yet but the Debian installer shouldn't burden
users with such low-level tinkering.

This is going to push potential Debian users to other distros after
they discover hibernate doesn't work.

Bug#1012341: med-config: 90med-config file missing a necessary trailing semi-colon

[Jason Quinn]

Thank you for the quick follow-up, Andreas. There's no pressing need
for an immediate upload. I'm just a user who wanted to help Debian be
as polished as possible.

I'm glad you found the solution ultimately lies in blends-dev. Please
note I filed a similar bug (#1011982) against the science-config
package. If both my reports are caused by the same issue in
blends-dev, maybe you can create a bug there and close the two
separate bugs (or however Debian handles such cases).

Thanks again.

Bug#935805: False report... please close

[Jason Quinn]

Problem ended up being a local environment for JAVA_HOME was being set.

Bug#737505: Just saw during install of 8.7.1

[Jason Quinn]

I just saw the same error during the installation of a long list of
packages on a fresh 8.7.1 installation. Confirming issue.

Jason

Bug#714399: a7xpg: spaceship drifts to upper left corner of screen making gameplay impossible

[Jason Quinn]

I agree. I looks that those bugs are very closely related to this one.
Thank you.

On 12/23/15, Peter De Wachter  wrote:
> This looks like a long-standing kernel bug:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=28912
> https://bugzilla.kernel.org/show_bug.cgi?id=37982
>
> More information and a work-around is here:
>
> https://github.com/denilsonsa/udev-joystick-blacklist
>

Bug#714399: a7xpg: spaceship drifts to upper left corner of screen making gameplay impossible

[Jason Quinn]

You are right, Peter! I ran jstest-gtk and my mouse is being detected
as a joystick! I quickly tried the game with and without my mouse and
this toggles the problem. It is a Microsoft Wireless Mobile Mouse 4000
(Model 1383). I happen to have TWO of the same mice and I tested both
and they both exhibit the same problem. I then tried calibrating the
mouse using jstest-gtk but I still cannot get the mouse to work.

jstest-gtk detects both mice as "Microsoft Microsoft® Nano
Transceiver v1.0" and as "Device: /dev/input/js0" with "Axes: 37" and
"Buttons:57". ALL the axes are shown in the jstest-gtk information
window show with value -32767 except for Axis 10 and 11 which are 0.

It becomes a question now whether the mouse is sending invalid output
and/or the game is not processing valid input.

Cheers,
Jason

PS Here are the relevant entries in my devices file:

I: Bus=0003 Vendor=045e Product=0745 Version=0111
N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
P: Phys=usb-:00:1d.0-1/input0
S: Sysfs=/devices/pci:00/:00:1d.0/usb4/4-1/4-1:1.0/input/input22
U: Uniq=
H: Handlers=sysrq kbd event13
B: PROP=0
B: EV=120013
B: KEY=10007 ff8007ff febeffdff3cf fffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=045e Product=0745 Version=0111
N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
P: Phys=usb-:00:1d.0-1/input1
S: Sysfs=/devices/pci:00/:00:1d.0/usb4/4-1/4-1:1.1/input/input23
U: Uniq=
H: Handlers=kbd mouse2 event14
B: PROP=0
B: EV=1f
B: KEY=4837fff072ff32d bf56 1f0001 20f908b17c000
677bfad9415fed 9ed6804400 1002
B: REL=3c3
B: ABS=1
B: MSC=10

I: Bus=0003 Vendor=045e Product=0745 Version=0111
N: Name="Microsoft Microsoft® Nano Transceiver v1.0"
P: Phys=usb-:00:1d.0-1/input2
S: Sysfs=/devices/pci:00/:00:1d.0/usb4/4-1/4-1:1.2/input/input24
U: Uniq=
H: Handlers=sysrq kbd event15 js0
B: PROP=0
B: EV=10001f
B: KEY=4c37fff072ff32d bf544456 c01 30f908b17c007
7bfad951dfff febeffdfffef fffe
B: REL=40
B: ABS=ff01000701ff
B: MSC=10

Bug#714399: a7xpg: spaceship drifts to upper left corner of screen making gameplay impossible

[Jason Quinn]

Your sentence that says "when you can't reproduce such an apparently
obvious issue" that makes it sound as if I'm doing something wrong.
It's clear you intend to say that you cannot reproduce the issue but
your phrasing could be improved.

I do not have a joystick. The keyboard is attached to a laptop. I have
not tried the game recently on another computer but if I get the
chance I will. As I wrote before, I believe I have already seen this
issue on multiple machines (likely on another Dell laptop at minimum)
but it's been a long time since I would have tried and I don't recall
anything for certain.

As for seeing more people report the bug, this an an obscure game.
When you start with the small fraction of people running Debian and
multiply it by the fraction of people who actually install this game
and then multiply by the fraction of people who experience the bug,
and then multiply the fraction of people who report bugs (which is
canonically taken to be about 1 in 100 users) , you are getting down
to a small number of expected bug reports... perhaps on the order of
one like just me. While it's interesting that you do not experience
the bug, I assure you the bug does happen for me; and your message
almost makes it sound like you dismiss the concept of bugs that depend
on various external issues or even hardware. It's far from obvious to
me that we should have seen more confirms in this case and I also note
the lack of additional "works for me" comments. So please don't
dismiss my report as if you are sceptical of the problem that *I'm*
experiencing because just because you don't see it.

Jason

Bug#714399: a7xpg: spaceship drifts to upper left corner of screen making gameplay impossible

[Jason Quinn]

Don't close. The problem still exists. Just freshly installed it and
have same exact issue.

Jason

Bug#700373: gedit-latex-plugin: texmf.cnf configuration setup is wrong/outdated/badly implemented

[Jason Quinn]

Package: gedit-latex-plugin
Followup-For: Bug #700373


I had the same issue. Makes gedit extremely annoying to use from command line.
Just removed gedit-latex-plugin to solve issue.



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

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

Versions of packages gedit-latex-plugin depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.12.1-3
ii  gedit3.4.2-1
ii  gvfs-bin 1.12.3-4
ii  python   2.7.3-4
ii  python-dbus  1.1.1-1
ii  python-glade22.24.0-3+b1
ii  rubber   1.1+20100306-2

Versions of packages gedit-latex-plugin recommends:
ii  python-enchant  1.6.5-2
ii  texlive 2012.20120611-5

gedit-latex-plugin suggests no packages.


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

Bug#714399: a7xpg: spaceship drifts to upper left corner of screen making gameplay impossible

[Jason Quinn]

Package: a7xpg
Version: 0.11.dfsg1-7
Severity: grave
Justification: renders package unusable

* What led up to the situation?

Just tried to play the game.

* What exactly did you do (or not do) that was effective (or ineffective)?

Move the spaceship around.

* What was the outcome of this action?

Spaceship drifts to upper-left corner of screen. I can make it move left or
right while it's happening but eventually I'm just pressed against the top of
the screen.

* What outcome did you expect instead?

Can move the spaceship around on the screen.

-

I had installed this game under Debian Squeeze and had the same issue. I
believe I've install it under older versions of Ubuntu and also had the same
issue. In other words, the game has never worked for me. I'm using a Dell
Inspiron 1720 laptop but I do not think it's a hardware problem because I
*think* I've also installed the game on other machines in the past and had the
same issue.




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

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

Versions of packages a7xpg depends on:
ii  a7xpg-data0.11.dfsg1-7
ii  libc6 2.13-38
ii  libgcc1   1:4.7.2-5
ii  libgl1-mesa-glx [libgl1]  8.0.5-4+deb7u2
ii  libsdl-mixer1.2   1.2.12-3
ii  libsdl1.2debian   1.2.15-5
ii  zlib1g1:1.2.7.dfsg-13

a7xpg recommends no packages.

a7xpg suggests no packages.

-- no debconf information


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

Bug#714401: alex4: game totally borked: stuck up key issue causing game to be unusable

[Jason Quinn]

Package: alex4
Version: 1.1-5+b1
Severity: grave
Justification: renders package unusable

* What led up to the situation?

Just tried to play it.

* What exactly did you do (or not do) that was effective (or ineffective)?

Just tried to play.

* What was the outcome of this action?

Couldn't even select menu item to play (or quit even) because selection arrow
is quickly cycling through options despite no input. Had to xkill game
because
can't even choose quit and the window's close button doesn't respond to a
close.

* What outcome did you expect instead?

Menu would wait for user input.




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

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

Versions of packages alex4 depends on:
ii  alex4-data 1.1-5
ii  libaldmb1  1:0.9.3-5.4
ii  liballegro4.4  2:4.4.2-2.1
ii  libc6  2.13-38
ii  libdumb1   1:0.9.3-5.4

alex4 recommends no packages.

alex4 suggests no packages.

-- no debconf information


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

Bug#712844: axiom: 3D plots fail saying: The viewport manager could not read from a 3D viewport window

[Jason Quinn]

Package: axiom
Version: 20120501-1
Severity: grave
Justification: renders package unusable

   * What led up to the situation?

 Just testing the basic functions.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 Tried to do a basic 3D plotting example using the Axiom help browser
(Basic Commands  Draw  A parametrically defined surface  Continue  Do It).

   * What was the outcome of this action?

 A buffer overflow crash (caught by axiom system however).

   * What outcome did you expect instead?

 A three-dimensional plot should have appeared.

Basically this makes plotting 3D plot impossible, which largely renders this
package unusable for many users. It's a rather big package too, taking up
almost a gig, so there's no sense is wasting a large amount of space on
people's hard drives.




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

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

Versions of packages axiom depends on:
ii  axiom-databases  20120501-1
ii  libc62.13-38
ii  libgmp10 2:5.0.5+dfsg-2
ii  libreadline6 6.2+dfsg-0.1
ii  libx11-6 2:1.5.0-1+deb7u1
ii  libxpm4  1:3.5.10-1

Versions of packages axiom recommends:
ii  axiom-doc   20120501-1
ii  axiom-graphics  20120501-1
ii  axiom-hypertex  20120501-1
ii  axiom-source20120501-1

Versions of packages axiom suggests:
ii  axiom-test  20120501-1
ii  axiom-tex   20120501-1
pn  nowebm  none
pn  texmacs none

-- no debconf information


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

Bug#622701: having trouble for few months now

[Jason Quinn]

I am running a fully updated Debian Squeeze (with Update Manager 0.200.5).
I started getting the Downloading list of changes... message that never
finishes a few months ago. I don't know what caused it. It used to work.

I am not using any proxy stuff.

I'd be great to know a workaround to this, or at least why it's occurring.

Bug#651649: I believe this bug still bites because NVIDIA drivers force older kernel

[Jason Quinn]

This bug, I believe, is indirectly caused by the Debian NVIDIA drivers in
non-free. Those drivers force an older kernel (2.6.32-5-amd64) to be used
that is presently shipped with 6.0.6 (linux 2.6.32-46-amd64). The kernel
USB bug causing the panic still exists in those older kernels but I think
the bug was fixed by the time of the 6.0.6's kernel.

This bug is rather severe and many launchpad bugs have been reported
related to it such as

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/844957