Bug#905090: wine-development: Causing SEGV when using Qt.

Hello, just tried to reproduce the issue and was able to in a buster i386 VM. Unfortunately winedbg does not take advantage of the automatic dbgsym pages. Therefore running from a local package build directory gives this stack: Backtrace: =>0 0x7ea989c5 USER_SetWindowPos+0x25()

Bug#887468: hpanel: Crashes with SIGSEGV sometimes

Forgot to attach ... Description: Avoid crash when there too many windows open to draw at least one char. Author: Bernhard Übelacker Bug-Debian: https://bugs.debian.org/887468 Forwarded: no Last-Update: 2018-08-07 --- hpanel-0.3.2.orig/hpanel.c +++ hpanel-0.3.2/hpanel.c @@ -588,7 +588,7 @@

Bug#887468: hpanel: Crashes with SIGSEGV sometimes

Control: tag -1 patch Hello Paul, I could trace from your core the crash into a call to XftTextExtents8 in libxft2 library. There is just one location that calls that function which is responsible to draw the window title near the icon in the window bar. There I could reproduce that crash:

Bug#887468: hpanel: Crashes with SIGSEGV sometimes

On Wed, 17 Jan 2018 09:41:44 +1100 Paul Szabo wrote: > Dear Maintainer, > > Running on x86_64, hpanel sometimes crashes with SIGSEGV. > As yet I have not noticed what actions may cause this, so > do not know how to make it happen at will. Hello Paul, just tried if I can reproduce the issue even

Bug#887457: freecad crashes with SIGSEGV if want to create a curve on a cylinder edge

Hello Robert, if you started the crashing application already with gdb then, after the crash, please also call the "bt" command to get a complete call stack. More information in [1]. And this is most helpful, if the debug packages got installed before, e.g. freecad-dbgsym and at least the last

Bug#829417: dosemu: *** stack smashing detected ***: /usr/bin/xdosemu terminated

Am 04.08.2018 um 21:53 schrieb Wolfgang Grünstern: > Thank you, > will the Debian version receive the patch next time automatically? > Kind Regards, > Wolfgang Hello Wolfgang, that would be up to the package maintainer, I think. Probably the best would be to try to get in contact with him

Bug#892016: scratch: segfault in lookupMethodInClass upon trying to load an image from the webcam

Hello Wouter, thanks for this additional information. I could reproduce the issue with a usb webcam inside a buster amd64 VM. Unfortunately this camera button was with the german translation not visible with the small resolution of that VM. It took a little time to get into the smalltalk side of

Bug#889878: closed by Picca Frédéric-Emmanuel (Bug#889878: fixed in hkl 5.0.0.2449-1)

Hello, tried have a look at this crash. The hkl-5.0.0.2449/Documentation/figures/.libs/sirius executable makes use of makecontext/swapcontext to execute function trajectory_gen_generator__. But it looks like the argument given to makecontext got truncated to 32 bits. So I looked for

Bug#892016: scratch: segfault in lookupMethodInClass upon trying to load an image from the webcam

Hello Wouter, just tried to reproduce this segmentation fault. Unfortunately we got new versions of squeakvm and other packages I fear the core dump is not that useful anymore. Also I was not able to got the current versions in Debian testing, when I started it that way: LANG=C

Bug#892288: arrayfire FTBFS on i386: test segfaults

Hello, tried to reproduce this, but unfortunately it fails to build against gcc-8, for which #897707 is already open. Therefore tried to reproduce it with gcc-7. I think this is what happens: - test Asssign_LinearAssignGenSeq_Test::TestBody allocates a buffer - buffer gets deleted - the same

Bug#897707: arrayfire: ftbfs with GCC-8

Hello, just tried to have a look at #892288 but got stopped by this one. Upstream handled this issue in [arrayfire/2148] and [arrayfire/2149]. Unfortunately this patch does not apply. Also the pull request mentions another change is needed in the boost library [boostorg/776]. Kind regards,

Bug#894861: openalpr: Segmentation fault reading particular image

Hello John Scott, I just tried to reproduce the issue. As far as I see this issue is known upstream as issue [openalpr#692]. That one got closed with following hint: Fixed by change in tesseract tesseract-ocr/tesseract#1669 In [tesseract#1665]/[tesseract#1669] a fix got commited for

Bug#900659: xsane: Preview results in SEGV

Hello Alison Chaiken, > Here is the backtrace from GDB. I'd be happy to compile the package > again from source and gather more info, although not if I must compile > GTK, too! No need to compile just for debug information as the debug information is now widely available in separate deb

Bug#902396: [nvram-wakeup] segfault with config generated by guess-helper

Hello, was just looking at some random crashes. I was only testing in a Debian testing/Buster amd64 VM. After some time looking at line readconf.c:71 I doubt that nvram-wakeup ever ran successfuly on amd64 architecture. At least in line 71 the 64bit pointers get trunctated by casting them to

Bug#893167: Stack smashing protection trigged in eboard

Hello, just tried to reproduce the stack smashing. It looks like the variable "gdouble c[3];" in colorb_csok needs to be a "gdouble c[4];". Did not find an related upstream ticket, neither in old SF nor at Github. Also at Github this function was not yet changed, so this should be forwarded to

Bug#829417: dosemu: *** stack smashing detected ***: /usr/bin/xdosemu terminated

Hello, just tried to reproduce this issue. I think the problem is with the usage of the segment register $fs in dosemu that is not compatible with gcc use of that segment register $fs. It looks like in "regular" processes the $fs register stays always at a value of 0. But after starting the

Bug#904588: supercollider: Stretch i386 Supercollider fails with segmentation fault

Hello Knut, Am 31.07.2018 um 00:37 schrieb Knut Jackowski: > So not sure how you see it, but I think that this is more a case of > borking one's own system and not a bug. I think it is not that easy, this might still be a bug. But yes, when the configuration gets more and more unique, the more

Bug#904588: supercollider: Stretch i386 Supercollider fails with segmentation fault

Hello Knut, thanks for your feedback. I was just asking because I did not know if Bunsen does rebuild packages. But as the packages are really from the Debian repo I assume here is a good place for this bugreport. So as it works with a default setup it is just harder to reproduce ... and it

Bug#904829: chuck: Adding a shred to a running server leads to the server segfault

Hello Al, I tried to reproduce the issue and the relevant part of the crash seems here: (gdb) bt #0 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:120 #1 0x7734446c in _IO_vfprintf_internal (s=s@entry=0x7fffe030, format=format@entry=0x556873e8 "[chuck](VM):

Bug#733304: wput package upgrade still crashes

tags -1 = patch bye Hello, just tried to reproduce the issue. With the help of the message #42 and the debug symbols in Stretch and later in a Debian Stretch i386 VM I could reproduce the issue. I think it all boils down to: (gdb) bt #0 get_port_fmt (ip=16777343, port=44081) at utils.c:81

Bug#798283: clvmd: stack smashing detected -- solved

Hello, just looking at some stack smashing errors and got onto this one here. Unfortunately Jessie did not have the dbgsym packages so I cannot get any clue of the given stack. Was or is this still an issue for Stretch or testing? Also it looks like this daemon got removed last month from

Bug#819487: yabause: stack smashed

Hello Richard Jasmin, can you still reproduce this issue or can this bug be closed? Could you tell if you use Gtk or Qt version? Or with which game this happens at which state? Kind regards, Bernhard

Bug#824390: Bug solved after upgrade

Hello Riccardo Lancellotti, > It looks like the problem was related to some incompatibility issue > with a previous version of some library (libecal-1.2 is my guess). Then was it solved by any update to libecal-1.2, or at least is it still an issue or should this bug be closed? Kind regards,

Bug#904588: supercollider: Stretch i386 Supercollider fails with segmentation fault

Hallo Knut, there is still the shadow that this issue might be first sent to the people from BunsenLabs. Nevertheless from looking at the stack it looks like a Qt5 application but we end up here in some Gtk 2 libraries ... Does this also happen with a new second user at this system? Also the

Bug#863926: fxt: FTBFS: Test failures

Hello, I tried to reproduce the issue. The original logfile showed this part: ending up *** stack smashing detected ***: /<>/tools/.libs/test terminated === Backtrace: = /lib/i386-linux-gnu/libc.so.6(+0x6737a)[0xf757e37a]

Bug#743948: hwinfo triggers "stack smashing" detector

Hello, tried to look if this issue could be closed. Unfortunately can also not reproduce it in a Debian Jessie i386 VM with 21.0-1 from snapshot.debian.org. Following the mail from message #20 [1], it leads to a bug in [2] which points in the attachement to the function read_klog. Upstream got a

Bug#904692: seahorse: Segfault few seconds after start

Hello Tobias Bengfort, I tried to reproduce by just starting seahorse in a VM, but the crash did not happen here. Probably you can follow the steps in [1] to locate where the crash happens? [1] https://wiki.debian.org/HowToGetABacktrace Kind regards, Bernhard

Bug#904588: supercollider: Stretch i386 Supercollider fails with segmentation fault

Hello Knut Jackowski, I tried to reproduce the issue with a Stretch i386 VM. "Unfortunately" the scide gui opened without a problem. So maybe you could deliver some more information about the crash by following this guide [1]. [1] https://wiki.debian.org/HowToGetABacktrace This mail is written

Bug#886777: crashes with Mustek scanner which worked before

Hello On Tue, 3 Jul 2018 20:57:46 +0200 "W. Martin Borgert" wrote: > Any more ideas? The workaround with the Jessie chroot is OK, but.. ;~) A way to get more information would be to install the debug information packages and let simple-scan run by gdb [1]. [1]

Bug#886776: genisoimage: Buffer Overflow found in isoinfo executable

Hello, I tried to reproduce the stack smashing. But found that the current package in Debian amd64 testing looks like it was not build with -fstack-protector-strong. So could it be that your report was using a local rebuilt package? Nevertheless it looks like the local variable testname has just

Bug#776161: qemu-system-x86: very long filename on virtual FAT disk -> stack smashing detected

fixed 776161 1:2.10.0-1 quit Hello Jakub Wilk, I tried to reproduce the issue in a Debian Jessie 32 bit VM. The stack smashing detector bytes are overwritten here: (gdb) bt #0 short2long_name (src=, dest=) at /home/benutzer/qemu/qemu-2.1+dfsg/block/vvfat.c:431 #1 create_long_filename

Bug#871503: msiinfo: buffer overflow in create_stream()

Hello, tried to reproduce this issue. The exact location where the stack smashing detector bytes get overwritten is below. Looks like an upstream bug where the size of the out parameter ("decoded" variable) is not respected. Kind regards, Bernhard (gdb) cont Continuing. Watchpoint 4:

Bug#807183: x86dis: *** stack smashing detected ***: x86dis terminated

Hello, tried to reproduce this issue in a Debian Jessie VM. The stack smashing detector bytes are changed here: (gdb) bt #0 __strncat_sse2 (s1=0x7fffd198 "s\201\215I\267\344Cݠ\022\271\367\377\177", s2=0x77ba5046 "s_expression>\n", n=0) at ../string/strncat.c:55 #1 0x77b9da83

Bug#898535: Incompatible ABI change without SONAME bump

Hello, this looks like it affects package mediainfo [1] too. Kind regards, Bernhard [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903054

Bug#903054: mediainfo: stack smashing detected with ffmpeg+webm+vp9+opus produced file

Hello, tried to reproduce this. So far it looks like it manifests not at amd64 but on i386. Also when rebuilding the package the fault is not visible. Using the previous package libtinyxml2-6_6.0.0+dfsg-1_i386.deb from snapshot.debian.org works without stack smashing. The problem might be a ABI

Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

Hello Alexander, thanks for your quick response. (Please leave at least the 898...@bugs.debian.org as recipient or CC to have the information stored in the bug database.) Unfortunately I guess Qt 5.12 will it not make into the Buster release. Kind regards, Bernhard Am 10.07.2018 um 11:32

Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

Hello, I got now a clarification in [KDE-396096]. There was a workaround attempted in [KDE-395346], but that led to another crash [KDE-395732] and got therefore reverted. Upstream it is handled in [QTBUG-68997], that got a fix in Qt 5.12. But except to wait for Qt 5.12 there is a workaround to

Bug#898553: grub-legacy 0.97-73 segfaults

(hd0) /dev/disk/by-id/ata-QEMU_HARDDISK_QM1 (hd1) /dev/disk/by-id/ata-QEMU_HARDDISK_QM2 Am 05.07.2018 um 21:09 schrieb Eugene Berdnikov: > Hello Bernhard. > > On Thu, Jul 05, 2018 at 06:10:44PM +0200, Bernhard Übelacker wrote: >> Hello Eugene, >> I ju

Bug#898553: grub-legacy 0.97-73 segfaults

Hello Eugene, I just tried to reproduce the issue and collect some more information. Unfortunately grub-legacy has not yet a dbgsym package. But is also crashing with a self built package. # gdb -q --args /usr/sbin/grub Reading symbols from /usr/sbin/grub...done. (gdb) display/i $pc 1: x/i $pc

Bug#898556: [kwin-wayland] Closing windows in Plasma Wayland crashes the entire session

Hello Maximiliano, I tried recently also a Plasma Wayland session and it crashed also on closing windows. I have coredumps enabled and installed the needed debug symbols. I put my findings into the upstream bug [396096]. That might be the same that Alexander observed. Kind regards, Bernhard

Bug#897390: xwayland: Segmentation fault loading GNOME 3

tags 897390 = moreinfo quit On Wed, 02 May 2018 02:09:08 +0200 Manolinux wrote: > #1 0x7f7cd8902231 in __GI_abort () at abort.c:79 > #2 0x5642194aaa5a in OsAbort () > #3 0x5642194b0573 in ?? () > #4 0x5642194b1395 in FatalError () > #5

Bug#897150: mixxx: Segmentation Fault

tags 897150 = moreinfo quit On Sat, 28 Apr 2018 23:25:07 -0500 Casey C wrote: > -- System Information: > Debian Release: buster/sid > APT prefers xenial-updates > APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, > 'xenial'), (500,

Bug#888585: RFS: dvbcut/0.7.2-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dvbcut" Package name: dvbcut Version : 0.7.2-1 Upstream Author : Bernhard Übelacker URL : https://github.com/bernhardu/dvbcut-deb License : GPL-

Bug#884608: doomsday: New upstream release available.

Package: doomsday Version: 1.15.8-5+b1 Severity: wishlist Tags: patch Dear Maintainer, Doomsday released upstream version 2.0.3. Please find in [1] a first try to upgrade this package. Changelog so far: * New upstream release. * Switch to Qt 5. (Closes: #874870) * Drop patches perms,

Bug#809064: [gimp] Cage Transform tool freezes UI

Dear Maintainer, today I stumbled also over this issue in Stretch amd64 with gimp-2.8.18-1. I tried to apply the patch by Alexis Scheuer from bug report [1][2] and built a package and can confirm that the freeze does not happen with it. As I could not easily apply it because of the format, find

Bug#876042: kexec-tools: "Unknown type (Reserved) while parsing" on newer kernel

Package: kexec-tools Version: 1:2.0.14-1 Severity: wishlist Dear Maintainer, trying to get kdump-tools in place I found that in Stretch using the kernel in stretch-backports (4.12.6-1~bpo9+1) I get following error: Sep 14 21:02:11 rechner systemd[1]: Starting Kernel crash dump capture

Bug#869684: linux-image-4.9.0-3-686-pae: Thinkpad T60 hangs on resume after suspend to disk; regress since Debian 8

Hello, I installed a Thinkpad T60 last year around 16.19.2016 with Debian Testing. With the kernel contained at that time suspend to disk was working well. (linux-image-4.6.0-1-686-pae 4.6.4-1, [1]) Just recently I got this system back and upgraded it to current Stretch.

Bug#864258: git-gui: Amend Last Commit scrambles umlaut in author name.

Package: git-gui Version: 1:2.11.0-3 Severity: normal Tags: patch Dear Maintainer, using "git gui" to "Amend Last Commit" scrambles the "Author" name in the commit, if the name contains at least a "Ü". A "new" commit is not affected. But on every amend it gets scrambled more. New: From:

Bug#863536: doomsday: Segfaults when attempting to start new game

Hello, tried to reproduce the issue. I think the problem is that in Cl_IsClientMobj the method maybeAs() is called on a NULL pointer on mo->thinker.d. With the attached patch the crash does not happen. And this time I took the opportunity to play in doom1-share.wad and doom2.wad (just short)

Bug#860751: mawk: segfaults on i386 during win32-loader build

Hello Thomas, sorry for the late reply. I tried to compare the mawk_1.3.3.orig.tar.gz from the current package and it compares best to the initial commit in mawk-snapshots [v1_3_3] from 2008. (Without debian directory and different VCS tags.) Since then the package just collected some patches on

Bug#863451: veusz: Segmentation fault

Hello, not being the maintainer I just tried to reproduce the issue. I received the segmentation fault, but unfortunately in some "Interface wrapper code" "Generated by SIP", that seems also not contained in the dbg package: # coredumpctl gdb (gdb) bt #0 0x in ?? () #1 0xb3da30f0 in

Bug#863460: hashrat: Seems to produce wrong results on big files

Hello, it seems that the value that start to lead to wrong values is 2048M. Also the returned hash from there is always the same as for an empty file. I first thought it has something to do with large file support, but it looks like that is already enabled. (gdb) print sizeof(off_t) $1 = 8

Bug#855125: moc: Segmentation fault

Hello, tried to debug it in a VM. # apt install moc-dbgsym $ gdb -q --args mocp Reading symbols from mocp...Reading symbols from /usr/lib/debug/.build-id/a2/ee23893fc19ab8924a10916a485b2a9c478e7c.debug...done. done. (gdb) set width 0 (gdb) set height 0 (gdb) run Starting program: /usr/bin/mocp

Bug#855325: Acknowledgement (libgs9: I updated yesterday my Wheeze System and now libgs.so.9 seggfault while printing with cups)

Hello Michelle Konzack, not being maintainer I was just curious about this problem, so I tried to reproduce ... - Installed a amd64 Wheezy VM - Inside installed cups-pdf printer. - Changed in /etc/cups/cupsd.conf from "LogLevel warn" to "LogLevel debug" Then following commands led not to the

Bug#863197: sysstat: sar program buffer overflow when option -s or -e are specified

Hello, just tried to reproduce the issue I think the problem here is just with a short time format ('04:00'). In that case 5 characters are copied by strncpy in parse_timestamp to timestamp variable. Unfortunately these 5 characters do not contain the termination, therefore the following strcat

Bug#847651: doomsday: Segfaults at startup

Hello, tried to reproduce the issue. I think the problem is that in de::File::parent the method maybeAs() is called on a NULL pointer. With the attached patch the crash does not happen. Kind regards, Bernhard # apt install doomsday doomsday-dbgsym doomsday-common-dbgsym $ gdb -q --args

Bug#858488: dieharder segfaults when testing the XOR generator

Hello, just tried to reproduce the crash I came to following stack: gdb -q --args dieharder -g 207 -a Program received signal SIGSEGV, Segmentation fault. gsl_rng_get (r=0x0) at ../gsl/gsl_rng.h:161 161 return (r->type->get) (r->state); (gdb) bt #0 gsl_rng_get (r=0x0) at

Bug#859342: Florence: segfault when clicking on size changing keys

Hello, this bug is probably a duplicate of https://bugs.debian.org/805895 Kind regards, Bernhard

Bug#805895: florence crashed with SIGSEGV in _IO_vfprintf_internal()

Hello, not being the maintainer I tried to reproduce the issue. I think we see here an exhaustion of the stack. Because clicking on the zoom button triggers a change of a g_settings/dconf entry. That triggers the callback view_set_scalex into florence. That tries to set the g_settings/dconf

Bug#862065: starplot: does not start due to invalid pointer error

Hello, not being the maintainer I tried to reproduce the issue. The message originates to freeing the std::string sSpecial in SpecClass::~SpecClass. I could follow in debugger to the constructor and set a watch point. That lead to a suspicious call to qsort. For this reason the content of

Bug#858647: make: SIGSEGVs on long parameter

Hello, not being the maintainer I tried to reproduce this issue. # apt-get install make-dbgsym # gdb -q /usr/bin/make --core /coredumps/core.make.8389 Reading symbols from /usr/bin/make...Reading symbols from /usr/lib/debug/.build-id/da/27c611d20ad6bc84f6309acb961492a00c114f.debug...done. done.

Bug#861978: xscorch: Segfault on startup

Hello, not being maintainer I tried to reproduce this issue. It looks like another case of pointer truncation due to "implicit declaration of function" in various files. Attached patch adds an include to gdk/gdk.h in a global header file. With it applied no implicit declarations remain and the

Bug#859653: ntopng: Segmentation fault with mysql

Hello, not being maintainer for ntopng I tried to reproduce the issue by the steps below. The crash happens because in MySQLDB.cpp this loop breaks only after 4 iterations instead of 2: const u_int16_t ipvers[2] = {4, 6}; for (u_int16_t i = 0; i < sizeof(ipvers); i++){ Attached are two

Bug#860821: tudu: Crashes with segfault when adding deadline to item

Hello, tried to reproduce the crash. Unfortunately there is no automatic dbgsym package available. # coredumpctl gdb ... Core was generated by `src/tudu'. Program terminated with signal SIGSEGV, Segmentation fault. #0 Date::operator== (this=0x38, d=...) at date.cc:275 275

Bug#861354: dash: segmentation fault when using >&$EMPTY_VARIABLE

Sorry, forgot to attach the patch. >From 98c530c23d9a7f86c996b028cadc2f685ec1b339 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bernhard=20=C3=9Cbelacker?= Date: Sat, 6 May 2017 10:40:37 +0200 Subject: Avoid crash when redirecting to file descriptor in expredir.

Bug#861354: dash: segmentation fault when using >&$EMPTY_VARIABLE

Hello, tried to reproduce this issue. Unfortunately no dbgsym package is available for dash. ./build-tmp/src/dash # echo test >&$EMPTY_VARIABLE Speicherzugriffsfehler (Speicherabzug geschrieben) # coredumpctl gdb Core was generated by `./build-tmp/src/dash'. Program terminated with signal

Bug#860443: bbrun fails to execute (Segment Violation)

Hello, I tried to reproduce the crash. It happens just after trying to execute something. History handling uses an array of pointer to char. Unfortunately it is stored in a pointer to a 32-bit integer. Therefore pointer get truncated. gcc is tries to warn about this: bbrun.c: In function

Bug#858037: ikarus FTBFS on i386: recipe for target 'ikarus.boot' failed (Segmentation fault)

Hello, tried to get some more information from the crash. # IKARUS_SRC_DIR=. IKARUS_BUILD_DIR=. IKARUS_FASL_DIRECTORY='' IKARUS_LIBRARY_PATH=.:.:./../lib gdb -q --args ../src/ikarus -b ./ikarus.boot.4.prebuilt --r6rs-script ./makefile.ss Reading symbols from ../src/ikarus...done.

Bug#860751: Bug#860695: win32-loader: FTBFS on i386: segmentation fault

Hello, this seems to be the same problem seen in #391051 for regular expressions (collect_RE). In this bug we overrun the size limit of string_buff (tempbuff._string_buff) in function collect_string. Attached patch adds a similar check like in #391051 to collect_string. With that applied the

Bug#858316: confirm the bug on 32 bit machine

Hello, tried to have a look at it. Program received signal SIGSEGV, Segmentation fault. 0x80015110 in mount () (gdb) bt #0 0x80015110 in mount () #1 0xb7f8ff03 in fuse_mount_sys (mnt_opts=0x800163a8 "rw,nosuid,nodev", mo=0xb398, mnt=0x80016288

Bug#860393: Segfaults on startup

Hello, just tried if I can reproduce the issue. I think this is a again a case of a pointer truncation by default int for a pointer returning function. First patch is just to build with debug information to make the automatic dbgsym packages helpful. The second patch adds some includes to get

Bug#844237: Incorrect handling of device major/minor

Hello, upstream applied Nicolas George's patch and released version 31 some days ago. I hope it is not too late for stretch? As I own an affected device I would like to supply some more informations and workarounds to people with similar devices. Kind regards, Bernhard - - Calling

Bug#853171: segmentation fault when disabling a screen with kscreen without upower installed on the system

Hello, I tried to debug this issue and spent "some" time to it. --- The class ShellCorona contains a QMap m_desktopViewforId storing pairs of idx and desktopViews pointers. When a display gets deactivated the method ShellCorona::removeDesktop [1] is called with parameter desktopView.

Bug#852532: olvwm: source code not 64-bit clean, SIGSEGV everywhere

Hello, I continued debugging from looking at #855167 and came up now with the 6 attached patches. With these applied olwm and olvwm are not crashing anymore inside my minimal test vm. Probably you want to give them a try. > Unless there is an automated way to identify all the cases of >

Bug#855167: olwm crashes trying to log in X

Hello Awtul, not being the maintainer for olwm I tried to shed shome light to it and describe some ways to get more informations out of it. (Even when olwm got removed from testing.) First one can install the systemd facility to collect coredumps: apt install systemd-coredump gdb

Bug#854981: unblock: le-dico-de-rene-cougnenc/1.3-2.3

-maintainer upload. + * Build with debug info to make dbgsym package usable. + * Avoid segfault by undefined behaviour. (Closes: #852659) + + -- Bernhard Übelacker <bernha...@mailbox.org> Wed, 08 Feb 2017 22:03:54 +0100 + le-dico-de-rene-cougnenc (1.3-2.2) unstable; urgency=medium * Non-main

Bug#852659: [le-dico-de-rene-cougnenc] segment fault

Hello Sandro, Am 08.02.2017 um 01:24 schrieb Sandro Tosi: > Hey Bernhard, > would be interested in preparing a NMU package with your patches > included (feel free to reply to me in private if you need instructions > on how to do that)? alternatively i'd be happy to NMU this myself I tried to

Bug#852659: [le-dico-de-rene-cougnenc] segment fault

Hello, not being the maintainer for this package, I just tried to have a look at it. 1043 *str = EquivalTable[ *str++ ] ; To me it looks like in the past the compiler did the assignment to the unincremented str. Today str gets first incremented, then *str assigned the element

Bug#852018: zapping: Segfaults immediately

Hello Helge, net being the zapping maintainer, I just tried to have a look at it. It looks like alloc_aligned does truncate the pointer to 32 bits. Therefore storing the original pointer, for being able to free it later, fails. common/alloc.c: 37 p = (void *)(((long)((char *) b +

Bug#782390: udev: time between USB-stick connection and device notification takes up to a minute

Hello Michael, I am sorry, but my old address got shut down. On Wed, 21 Dec 2016 19:30:10 +0100 Michael Biebl wrote: > just wanted to ask, if you still run into this issue with a newer kernel > (from testing). If so, I think it would probably best to re-assign this. > >

Bug#844517: fixed in kradio4 4.0.8+git20170114-1

Hello Pino Toscano, thank you for taking care for this report. May I still ask what I should do for the other packages in Stretch, that are still built using an old 0.9.0*-lirc version and are probably suffering from the same crash as this report is about? Get they rebuilt automatically before

Bug#850073: dvbcut: FTBFS on hppa -- --with-ffmpeg=/usr not passed to configure

notfound 850073 0.73.0 found 850073 0.7.0-1 thanks Hello Dave, sorry for the delay. I got a little distracted by creating a hppa chroot ... I assumed version 0.73.0 was just mixed up from the sbuild version, so I am trying to change it to 0.7.0. Due to [2] there is currently a version 0.7.1-1

Bug#844734: RFS: dvbcut/0.7.1-1

ildsystem=autoconf --with=autoreconf,autotools-dev --parallel > > this is useless with compat level 10 (at least it should be) > please bump compat to 10 and debhelper >=10 :) > also, consider dropping them as build-dependencies > > > [ Bernhard Übelacker ] > > >

Bug#841183: dvbcut: mplayer2 has gone away

Am 18.11.2016 um 18:08 schrieb James Cowgill: > On 18/11/16 14:28, Bernhard Übelacker wrote: >> Hello James, >> sorry for the late reply. >> >> I prepared a new version removing mplayer2 and opened a RFS in [1]. > > Why did you remove mpv? Hello James, becau

Bug#841183: dvbcut: mplayer2 has gone away

Hello James, sorry for the late reply. I prepared a new version removing mplayer2 and opened a RFS in [1]. Thanks, Bernhard [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844734

Bug#844734: RFS: dvbcut/0.7.1-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dvbcut" * Package name: dvbcut Version : 0.7.1-1 Upstream Author : Bernhard Übelacker * URL : https://github.com/bernhardu/dvbcut-deb * License

Bug#844517: kradio4: Crashes when lirc configuration is found. (interface of liblircclient0 changed)

Package: kradio4 Version: 4.0.8+git20160618-1 Severity: important Dear Maintainer, kradio4 crashes after reading the lirc configuration. In my opinion the crash happens because the current stretch package was built against liblircclient-dev (0.9.0~pre1-1.2). [1] [2] Now the interface changed

Bug#843707: kwin: No dbg package is built.

I was not aware of this repo. Just checked the source package at packages.debian.org, but did not find an entry for a dbg package. Thank you very much.

Bug#828010: RFS: dvbcut/0.7.0-1

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dvbcut" * Package name: dvbcut Version : 0.7.0-1 Upstream Author : Bernhard Übelacker * URL : https://github.com/bernhardu/dvbcut-deb * License

Bug#822609: dvbcut: Missing icons on main window

Hello Uwe Herrmuth, sorry for the delay and thanks for you report. I had a look at it and found that these icons are loaded from the current configured theme. At my desktop e.g.: /usr/share/icons/oxygen/48x48/actions/document-open.png This file belongs to package: oxygen-icon-theme But

Bug#826830: libqt5gui5: Touchscreen input broken for Qt5 apps when using libinput X-server driver

Package: libqt5gui5 Version: 5.5.1+dfsg-17 Severity: normal Dear Maintainer, Installing xserver-xorg in current stretch installs both X-server drivers: evdev and libinput. At least on my system X-server took therefore the libinput driver. Unfortunately libinput registers with "Abs X" instead

Bug#784715: qemu-system-x86: booting Debian install cd makes qemu window endless toggle between two window sizes

Hello Tokarev, Am 30.01.2016 um 12:04 schrieb Michael Tokarev: However I see one interesting difference between our setup. What is your screen size, and desktop area size? On your video, the VM window size is close to your desktop size. I remember seeing some strange effects when the VM

Bug#783081: installation-reports: Jessie daily installer installs kernel in flash without any further confirmation (QNAP TS-212)

Hello Martin, thanks for your answer. It was less of an inconvenience as a surprise. In fact, after all went fine, I was happy not to boot via tftp anymore. :-) So, yes, this was just a note to the few users, who have concerns writing to the flash in fear to create an unbootable device. (I

Bug#803809: dvbcut: FTBFS with FFmpeg 2.9

Hello, I uploaded a package with the change from Andreas to mentors.debian.net and filed a RFS for it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805511 Kind regards, Bernhard

Bug#805511: RFS: dvbcut/0.5.4+svn178-12

n) * Due to lintian command-in-menu-file-and-desktop-file: - debian/dvbcut.menu removed. -- Bernhard Übelacker <bernha...@vr-web.de> Wed, 18 Nov 2015 23:55:08 +0100 Regards, Bernhard Übelacker

Bug#795616: dvbcut: Illegal changelog date format

Hello Chris, I am sorry for this this mistake. I assume you tried to build dvbcut for the current gcc transition on testing/unstable where you got an error as following. # dpkg-buildpackage Error parsing time at /usr/lib/x86_64-linux-gnu/perl/5.20/Time/Piece.pm line 469, $filehandle line 12. I

Bug#795754: RFS: dvbcut/0.5.4+svn178-11

) -- Bernhard Übelacker bernha...@vr-web.de Sun, 16 Aug 2015 17:34:48 +0200 Regards, Bernhard Übelacker

Bug#795616: dvbcut: Illegal changelog date format

Opened this RFS: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795754 Kind regards, Bernhard

Bug#793156: RFS: dvbcut/0.5.4+svn178-10

) (Thanks to Sebastian Ramacher and Andreas Cadhalpun) -- Bernhard Übelacker bernha...@vr-web.de Tue, 21 July 2015 18:08:10 +0200 Regards, Bernhard Übelacker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas

Bug#793156: RFS: dvbcut/0.5.4+svn178-10

Hello Sebastian, thank you very much for your help. Please revert that. The point of the libav-ffmpeg transition is that ffmpeg provides libavcodev-dev, libavformat-dev, etc. I am sorry. I tried to build it with the stretch ffmpeg packages which did not provide these packages and therefore

<    7   8   9   10   11   12   13   >