Bug#677470: xserver-xorg: X server eats CPU when there is animated icons in [plasma]tray

Similar things can be observed in thunderbird or palemoon or anything with spinners and throbbers and crap. I suspect it might(also) be a lousy porter/duff implementation somewhere in libpixman or thereabout. slowness reading from gfx memory and all that...

Bug#1002839: default clearances are set to a compiled in value

Package: pcb-lesstif Version: 20140316-3 Hello, I was just trying to get a layout ready to fab with a boardhouse and tried to get the defaults for polygon and solder mask clearance adjusted. I was using some old style footprints without the Pin clearances specified. > Pin(25 42 40

Bug#964295: production without refuelling

Package: asc Version: 2.6.1.0-5+b1 When trying to build a unit without fuel or ammo, the checkbox for don't fuel doesn't work. I have to either store material/fuel somewhere to avoid creating ammo/fuel. or exit the building dialog and. use backspace to revert 1 step (the fuelling/ammo step). (it

Bug#964297: crash when doing maximize-minimize window

Package: asc Version: 2.6.1.0-5+b1 when trying to remaximize the game. window (Alt-Enter, Alt-Enter) I get: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. asc:

Bug#964298: Unchecking the show all technologies checkbox does not work

Package: asc Version: 2.6.1.0-5+b1 Happens in the default campaign missions that allow research. I can view the Technologies with preconditions, but can not revert back, except by closing/reopening the dialog.

Bug#964296: NOS campaign ends after the first map

Package: asc Version: 2.6.1.0-5+b1 After completing the first map in NOS campaign, I end up in the game menu again. The source tree shows 7 maps. Also, there's a redundant '#' in the german text.

Bug#867136: Impossible to use SDCC with PIC devices as non-free headers are removed

Still no luck... After creating pic16f1703.h, pic16f1703.c, devices.txt and pic14devices.txt I'm getting "error 131: cannot generate code for target 'pic14'" Either the compiler binary is crippled or one of the paths is wrong.

Bug#867136: Impossible to use SDCC with PIC devices as non-free headers are removed

Also the browse link on the PTS seems down (getting a 404)

Bug#867136: Impossible to use SDCC with PIC devices as non-free headers are removed

On Tue, 04 Jul 2017 07:06:57 +0200 Petter Reinholdtsen wrote: > > Package: sdcc > Version: 3.4.0+dfsg-2 > Severity: wishlist > > The --use-non-free option for sdcc do not work, making it impossible to > use sdcc to compile code for PIC devices. I wanted to use it to compile > the firmware for

Bug#872002: some more context

The control flow diverges somewhere after FlushUpdate... it seems to be this if.. in Text.c 3320#ifndef OLDXAW 3321if (XawTextSinkBeginPaint(ctx->text.sink) == False) 3322#endif 3323display_text = OldDisplayText; the condition differs because of:

Bug#872002: libxaw7: mixing international and non-international asciiTextWidgets segfaults

Package: libxaw7 Version: 2:1.0.12-2 Severity: normal The text widgets have this resource, XtNinternational. It is a boolean. If it is set to True for one Widget, and False for another, a call to XtSetValues to set the text will crash the application. compile the testcase using: cc -std=gnu99

Bug#853797: patched version

I believe I've come across this before and there's a patched version here: no dedicated patch tho'... I was kinda waiting for the next release, but start wondering if it will ever happen

Bug#230695: Sorry

Ignore the previous message. It's for the other bug. (#853797)

Bug#230695: patched version

I believe I've come across this before and there's a patched version here: no dedicated patch tho'... I was kinda waiting for the next release, but start wondering if it will ever happen

Bug#771677: patches added to Debian source tree

On Mon, 5 Dec 2016 22:49:08 +0100 Geert Stappers wrote: > Control: tag -1 pending > > The provided patches are in the Debian source tree. > They are under debian/patches/ > > But they are "commented out" in the debian/patches/series file. > Because they trigger a compile

Bug#820398: [Pkg-lyx-devel] Bug#820398: Lyx crashes with SIGILL on processors without cmov

On 05/11/2016 05:18 PM, Nikos Andrikos wrote: > Hi Johann, > > Can this be related to the recent move from i386 to 686-class move for > debian? > https://lists.debian.org/debian-devel-announce/2016/05/msg1.html > Yeah, great... > I think cmov is now part of the required ISA. > What

Bug#813119: ngspice: FTBFS with nonexistant $HOME

this one works better with parallel builds... #!/usr/bin/make -f # -*- makefile -*- # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 export CPPFLAGS=$(shell dpkg-buildflags --get CPPFLAGS) export CFLAGS=$(shell dpkg-buildflags --get CFLAGS) export CXXFLAGS=$(shell dpkg-buildflags

Bug#820398: Lyx crashes with SIGILL on processors without cmov

Package: lyx Version: 2.1.4-2 I got this while trying to build ngspice on my fileserver (it holds the debian installation here, and ngspice dropped from testing) [...] dh_testdir #cd build/manual && lyx --export ps manual.lyx. cd build/manual && lyx --export pdf2 manual.lyx.

Bug#813119: ngspice: FTBFS with nonexistant $HOME

Try this debian/rules file. #!/usr/bin/make -f # -*- makefile -*- # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 export CPPFLAGS=$(shell dpkg-buildflags --get CPPFLAGS) export CFLAGS=$(shell dpkg-buildflags --get CFLAGS) export CXXFLAGS=$(shell dpkg-buildflags --get CXXFLAGS)

Bug#785109: Asylum crashes in Psyche level

Can you apply the patches locally, plz?

Bug#796263: pcb-lesstif: SIGSEGV when clicking `Next' in `DRC check' Message Box

This seems to be the same as: https://bugs.launchpad.net/pcb/+bug/699284 A workaround seems to be not to use the line drawing tool in DRC mode/stopping DRC mode to draw... I was able to complete editing that way...

Bug#796263: pcb-lesstif: SIGSEGV when clicking `Next' in `DRC check' Message Box

Package: pcb-lesstif Version: 20140316-3 Severity: important Good evening, When running a drc check on a pcb board, I ran into a SIGSEGV. It does not happen right away, might be a delayed effect of memory corruption... I did some editing to correct drc fails, and had caused a short during the

Bug#771677: Segmentation fault during detect

The SVF parser crashes, too... here's another patch... Description: fixes SVF parser segfaulting --- urjtag-0.10+r2007.orig/src/svf/svf.c +++ urjtag-0.10+r2007/src/svf/svf.c @@ -68,7 +68,7 @@ #undef DEBUG -int urj_svf_parse (urj_svf_parser_priv_t *priv_data, urj_chain_t *chain); +int

Bug#771677: Segmentation fault during detect

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

Bug#771677: Segmentation fault during detect

Yes, It's the bison parameter mismatch... Is It possible to get a new version from upstream (assuming it works on current testing)? Alternatively, there's a patch appended... (I believe it's a bit prettier) Description: Fix pointer mixup this changes the function prototypes for parser and

Bug#771677: Segmentation fault during detect

I have run into this, too... jtag cable DLC5 ppdev /dev/parport0 jtag frequency 10 jtag detect IR length: 10 Chain length: 1 Device Id: 0001010100010111 (0x0151403F) Manufacturer: Atmel (0x03F) Part(0): ATF1504ASV (0x1514) Stepping: A Filename:

Bug#785109: buffer overruns...

Package: asylum Version: 0.3.2-1 Tags: patch I tried to debug the segfault I get sometime at the end of the second level. This is what I found. two buffer overruns... a stale FILE*... Perhaps there's more... Did not get to finish the second level yet... The keyword[12] and FILE* was found

Bug#780449: FTBFS during reproducibility tests

Package: berkeley-abc Version: 1.01+20140822hg4d547a5+dfsg Tags: patch The PTS complains about the __TIME__ etc macros, so I removed them. Someone please apply. Description: Remove the __TIME__ etc macros Otherwise the debian package checking complains... ---

Bug#780450: fails to export trivial .PLA files

Package: berkeley-abc Version: 1.01+20140822hg4d547a5+dfsg severity: minor Tags: patch abc fails an assert when the network is too shallow(due to constants). I've submitted an issue upstream before, but nothing happened. It has a testcase:

Bug#763755: blender: SIGILL on startup

On 10/10/2014 08:48 AM, Matteo F. Vescovi wrote: No, it doesn't. Your patch wasn't applied in 2.71. I modified it locally... Oh, gotta check this either... but I've no X on my laptop at the moment. Thanks for reporting. Not sure it's a bug.. it's quite possible they don't support

Bug#763755: blender: SIGILL on startup

the changelog. Adjust it or drop it. . blender (2.71+dfsg1-2) UNRELEASED; urgency=medium . * change rules file to set architecture flags Author: Johann Klammer klamm...@a1.net --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps

Bug#763755: blender: SIGILL on startup

On 10/09/2014 03:01 PM, Matteo F. Vescovi wrote: Hi again! On 2014-10-09 at 14:39 (CEST), Matteo F. Vescovi wrote: Re-applying it with next upcoming revision. Sorry for the mess. FTR, test build on i386 with your patch applied on top of 2.72 now fails [1]. I hope to find a solution

Bug#763755: blender: SIGILL on startup

On Thu, 2 Oct 2014 14:43:30 +0200 Matteo F. Vescovi mfvesc...@gmail.com wrote: Control: tag -1 + upstream Hi! On 2014-10-02 at 13:54 (CEST), Daniele Forsi wrote: Dear Maintainer, could Blender be changed to check if it is running on a supported CPU and fail with a nicely

Bug#712573: regression: ctrl key continually pressed

I believe you can disable it by setting 'screensaver_timeout' to 0. It is in the gui tab. And yes, it's totally annoying while editing text in another window... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#632080: vlc: VLC cannot open mpeg (TS) files recorded from satellite channels

I have a .ts snippet, which does not display anything here. Works in xine. Was part of a larger file. vlc would just grind the disk, but not display anything. http://members.aon.at/~aklamme4/scratch/hang.ts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject

Bug#665732: reopen: vlc: GUI latency/unresponsiveness to clicks on control options

Rémi Denis-Courmont wrote: tags 665732 = moreinfo help unreproducible thanks Hello, Le mardi 26 février 2013 17:33:21, Johann Klammer a écrit : Adding a usleep(1) after the last aout_unlock() in aout_DecPlay() in src/audio_output/dec.c solves the problem for me. Unfortunately

Bug#665732: reopen: vlc: GUI latency/unresponsiveness to clicks on control options

Adding a usleep(1) after the last aout_unlock() in aout_DecPlay() in src/audio_output/dec.c solves the problem for me. It seems that the GUI thread fails to get woken up after the mutex here is unlocked Not sure if this is a kernel bug or just quality of implementation... -- To

Bug#687735: Testcase for demuxer/psi bug

There: http://members.aon.at/~aklamme4/scratch/test.ts File was generated using rtpdump, Switching from TELE5 to ProSieben(on different mux). The .ts file crashes vlc at the point of transition. I find it hard to believe that you could not reproduce as it always, reliably happens here when

Bug#687735: Testcase for demuxer/psi bug

Fabian Greffrath wrote: Please note that the bug got tagged upstream and moreinfo, not wontfix. Sorry, Should have been more precise. I was ranting about #665732(not submitted by me, but affects me too) in the second paragraph. -- To UNSUBSCRIBE, email to

Bug#236507: sane-utils: scanimage generates bad PPM files

Package: sane-utils Version: 1.0.22-7.4 Hello, I can confirm that scanimage truncates pnm files. I am using a brother DCP7010 print/scan combo on a LAN. The back-end seems to report the paper size wrongly or do faulty rounding (I think it should truncate to nearest pixel, while in fact it

Bug#236507: sane-utils: scanimage generates bad PPM files

Just did some more reading... Seems I am using the binary brother brscan2 driver. It does replace some parts of the sane infrastructure... So I do not know if the observed behaviour is caused by sane-utils or (more likely) brscan2. dpkg -l \*brscan2\* Desired=Unknown/Install/Remove/Purge/Hold

Bug#687735: VLC crashes when playing back TS-over-RTP and transport stream changes

Package: vlc Version: 2.0.3-2 Hello, I recently upgraded vlc from 1.1.13-1+b1 to 2.0.3-2. I am using it to play back rtp:// streams forwarded by this software: https://github.com/klammerj/dvb-vulture AFAIK The stream contains a valid PCR... When the stream composition changes (by tuning to

Bug#599680: conditional SSE/2 patch

This one is a bit better, as it leaves SSE/2 enabled on targets that support it. Description: Conditionalize SSE and SSE2 support This makes sure it builds compatible binaries also on machines which have sse/sse2. Fixes the SIGILL bug. Checks for DEB_HOST_ARCH_CPU!=i386 before tests are

Bug#599680: blender: crashes with: illegal hardware instruction

Arrgh, Just tried Version 2.63a-1 .deb and it _still_ fails with SIGILL. The blender bugzilla/wiki[1][2][3] mentions that their binary build is done on a virtual machine and build flags get set automatically... Obviously this will not work for debianized builds, as (sub)architectures vary,

Bug#682812: calloc (nmemb=0, size=12)

Michel Dänzer wrote: On Mit, 2012-07-25 at 23:01 +0200, Johann Klammer wrote: Does the problem still occur with libgl1-mesa-dri version 8.x? updated to 8.0.3-1 Same results. Also, I get these unexpected messages on startup of the application: nvfx_screen_get_param:95 - Warning: unknown

Bug#682812: calloc (nmemb=0, size=12)

Package: mesa Version: 7.11.2-1 Hello, I tried to replace the memory allocator for a program linked against mesa. With the libc allocators the app shows some textured and shaded triangles, but with the custom allocators, it's all black triangles. Sorry, I cannot post the program source as it

Bug#634261: Forgive my illiteracy...

But... How is the operator precedence? is it if ((_IO_stdin_used == NULL)) or if ((_IO_stdin_used) == NULL) IMHO It should be the latter... can you do a p (_IO_stdin_used == NULL) and p ((_IO_stdin_used) == NULL) in your gdb session? Bye, JK -- To UNSUBSCRIBE, email to

Bug#634261: Another wild guess...

Could there be a #define _IO_stdin_used somewhere further up? I am not sure if gdb sees those, so it may output a different symbol from what the program sees. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#676862: posix_memalign patch fails some tests

overruns are more likely to be detected. make heavy tests pass without error. . dmalloc (5.5.2-3) unstable; urgency=low . * Integrate alignment into chunk.c Author: Johann Klammer klamm...@a1.net --- dmalloc-5.5.2.orig/malloc.c +++ dmalloc-5.5.2/malloc.c @@ -734,11 +734,6 @@ void

Bug#676587: A patch for this bug and 676585

* changed GET_RET_ADDR() to use __builtin_return_address Author: Johann Klammer klamm...@a1.net Bug-Debian: http://bugs.debian.org/676585 Bug-Debian: http://bugs.debian.org/676587 --- dmalloc-5.5.2.orig/malloc.c +++ dmalloc-5.5.2/malloc.c @@ -38,6 +38,20 @@ # include unistd.h

Bug#676585: dmalloc_fc_t -s segfaults in arg checking code

Source: dmalloc Version: 5.5.2-2 The test program dmalloc_fc_t that is run after compiling fails badly. The build continues anyway, but it indicates a problem with the library. Some excerpts from a gdb session follow.. (gdb) backtrace #0 malloc (size=8) at malloc.c:1226 #1 0x0804f906 in

Bug#676587: posix_memalign missing. Other alignment thingys unimplemented except for valloc.

Package: libdmalloc5 Version: 5.5.2-2 Hello, Some time ago I tried building a program against libmesa, nouveau and libdmalloc. I got some `cannot locate pointer in heap` errors. installing debug versions of the nouveau module and googling the source code indicated that the module was using

Bug#676587: A patch for this bug and 676585

__builtin_return_address Author: Johann Klammer klamm...@a1.net Bug-Debian: http://bugs.debian.org/676585 Bug-Debian: http://bugs.debian.org/676587 --- dmalloc-5.5.2.orig/malloc.c +++ dmalloc-5.5.2/malloc.c @@ -38,6 +38,20 @@ # include unistd.h /* for write */ #endif

Bug#599680: blender: crashes with: illegal hardware instruction

Just tried the 2.62-1 version .deb and it still fails with SIGILL The official build from the blender homepage works well, though. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org