Bug#1059250: mate-screensaver: SIGSEGV of mate-screensaver while automatic activation and interfering with mouse pointer movement

Package: mate-screensaver Version: 1.26.1-1 Severity: normal Dear Maintainer, Screensaver was activating automatically, while darken the screen, I have interferred with mouse pointer. Screensaver was not able to lock anymore the screen because it crashed with SIGSEGV. regards, Joël -- System

Bug#986290: libags-audio3: wrong ref-count in ags_fx_factory.c

Package: libags-audio3 Version: 3.7.44-3 Severity: normal Tags: patch Dear Maintainer, Upstream discovered wrong ref-count in ags/audio/ags_fx_factory.c affecting libags_audio.so and the gsequencer binary. Without patching memory corruptions could occur. As AgsChannel implementation might be

Bug#985146: unblock: gsequencer/3.7.44-3

-3) UNRELEASED; urgency=medium + + * removed rejected patches + * minimal patch to fix Bug#983868 + * updated patches series file + + -- Joël Krähemann Sat, 13 Mar 2021 14:59:27 +0100 + +gsequencer (3.7.44-2) unstable; urgency=medium + + * add patch to fix undefined behavior or missing return

Bug#983868: gsequencer ftbfs with -Werror=maybe-uninitialized

AM Mattia Rizzolo wrote: > > > > On Wed, 3 Mar 2021, 10:30 am Joël Krähemann, wrote: >> >> I am going to provide another tarball including this fix. > > > There is no need to stage this for bullseye, it can be fixed later. > (Also because at this point it would require a release unblock...)

Bug#983868: gsequencer ftbfs with -Werror=maybe-uninitialized

nd GCC 11 as well. The name of the option even implies that this is a > "maybe". > Forcing it to become an error with -Werror might be wrong, so if you build > with > -Werrer, build with -Wno-error=maybe-uninitialized as well. > > On 3/2/21

Bug#983868: gsequencer ftbfs with -Werror=maybe-uninitialized

output 0 length, this means you can't use return location, so why should I set it? regards, Joël On Tue, Mar 2, 2021 at 1:45 PM Matthias Klose wrote: > > Package: src:gsequencer > Version: 3.7.38-1 > Severity: important > Tags: sid bullseye > X-Debbugs-CC: Joël Krähemann &g

Bug#973552: xserver-xorg-video-amdgpu: GPU crashed while doing screencast using ffmpeg with gsequencer

Package: xserver-xorg-video-amdgpu Version: 19.1.0-2 Severity: normal Dear Maintainer, While I was running ffmpeg to do a screencast showing the capabilities of gsequencer. But while doing so the GPU crashed after some time of playback. The system was not usable, anymore. I wasn't able to

Bug#944589: gsequencer: stalls system

The only thing I can do is to allow the user to configure AGS_RT_PRIORITY http://git.savannah.nongnu.org/cgit/gsequencer.git/tree/ags/audio/thread/ags_audio_loop.c?h=3.0.x=93bddce14d8b1bf98f30867babd9d36db1487fbf#n660 regards, Joël On Thu, Nov 28, 2019 at 6:21 AM westlake wrote: > > It looks

Bug#944589: gsequencer: stalls system

Hi, Thank you very much for your information. As you might have noticed there is much going on related to new threading API in GSequencer v3.0.0 And thanks to your information you pointed me to allow adjusting realtime priorities by configuration seems to be mandatory.

Bug#944589: gsequencer: stalls system

Hi, This one liner patch would reduce CPU usage from 300 % to 100 %. cheers, Joël On Thu, Nov 28, 2019 at 5:35 AM Joël Krähemann wrote: > > Hi, > Just checked the CPU usage again as running the AgsDrum sequencer, > during playback the usage goes down to 80 %. > > I think wit

Bug#944589: gsequencer: stalls system

Hi, Just checked the CPU usage again as running the AgsDrum sequencer, during playback the usage goes down to 80 %. I think with a small patch we can fix this behavior. regards, Joël On Thu, Nov 28, 2019 at 4:26 AM Joël Krähemann wrote: > > Hi, > I take your complain about CPU usage s

Bug#944589: gsequencer: stalls system

API, here are further informations: http://savannah.nongnu.org/forum/forum.php?forum_id=9601 sorry, Joël On Thu, Nov 28, 2019 at 3:26 AM Joël Krähemann wrote: > > Hi, > Yes, it is true. GSequencer consumes too much power as doing no audio > processing. > This was targeted

Bug#944589: gsequencer: stalls system

Hi, Yes, it is true. GSequencer consumes too much power as doing no audio processing. This was targeted with next major release v3.0.0 expected available within a half year. To change this behavior, I had to refactor the threading API of GSequencer. Currently it creates many threads without

Bug#944589: gsequencer: stalls system

Your computer has not enough power to run these realtime priorities. On my workstation the realtime priorities work. It is a dual CPU system with 2x Intel Xeon hexa core and hyper threading. regards, Joël On Wed, Nov 27, 2019 at 7:59 AM Joël Krähemann wrote: > > Hi, > >

Bug#944589: gsequencer: stalls system

Hi, This solved the problem. rm /etc/security/limits.d/audio.conf I am even to run JACK with the attached configuration. If you want to use it, make sure samplerate and buffer-size matches. best regards, Joël On Wed, Nov 27, 2019 at 7:34 AM Joël Krähemann wrote: > > Hi, > > I w

Bug#944589: gsequencer: stalls system

Hi, I was just able to reproduce "gsequencer stalls system" while using realtime priorities. If you want to use GSequencer might be you have to revert the modifications in: /etc/security/limits.d thank you for reporting the bug. regards, Joël On Wed, Nov 27, 2019 at 6:11 AM Joël

Bug#944589: gsequencer: stalls system

provide a stack-trace of the running GSequencer process: `gdb -ex "set pagination 0" -ex "thread apply all bt" --batch -p $(pidof gsequencer)` regards, Joël On Wed, Nov 27, 2019 at 5:53 AM Joël Krähemann wrote: > > Hi, > > Just installed linux-image-rt from bpo

Bug#944589: gsequencer: stalls system

Hi, Just installed linux-image-rt from bpo, and I am not able to reproduce the behavior ... I am using an Intel 4 Core CPU, too. Please, tell me about your modifications to: /etc/security/limits.conf best regards, Joël On Wed, Nov 27, 2019 at 5:28 AM Joël Krähemann wrote: > > Hi, >

Bug#944589: gsequencer: stalls system

Hi, Please stay on topic. On Wed, Nov 27, 2019 at 1:42 AM westlake wrote: > > the system here sets RT for the applications without issue, > Might be but its not related as told you prior. > "$ pgrep -fa jack > 1717 /usr/bin/jackdbus auto > $ chrt -a -p 1717 > pid 1717's current scheduling

Bug#944589: gsequencer: stalls system

Hi, I think there is no problem except the lack CPU resources, GSequencer needs power and pulseaudio behaves really bad on low CPU power. Please, try the ALSA configuration as previously been told. This always appears, even as loading builtin config: /home/user/.gsequencer/ags.conf This is

Bug#944589: gsequencer: stalls system

Few days ago, someone reported a similar behavior, we figured out that low CPU power and the use of pulseaudio caused problems. Does it help if you put a different configuration in your: $HOME/.gsequencer/ags.conf As shown here: http://nongnu.org/gsequencer/help.html Or see attachment.

Bug#944589: gsequencer: stalls system

t; > cat /proc/version > "Linux version 5.2.14-rt7 (customx@debian) (gcc version 8.3.0 (Debian > 8.3.0-6)) #1 SMP PREEMPT RT Mon Sep 30 05:58:30 EDT 2019 > " > > On 2019-11-13 5:50 a.m., Joël Krähemann wrote: > > Hi, > > > > thank you for reporting

Bug#944589: gsequencer: stalls system

Hi, Don't forget to provide GSequencer configuration in $HOME/.gsequencer/ags.conf regards, Joël On Wed, Nov 13, 2019 at 1:25 PM Joël Krähemann wrote: > > Hi, > > I just installed realtime kernel and gsequencer from debian repository. > > I am not able to reproduce. >

Bug#944589: gsequencer: stalls system

Hi, I just installed realtime kernel and gsequencer from debian repository. I am not able to reproduce. please provide more information and your kernel configuration. cheers, Joël On Wed, Nov 13, 2019 at 11:50 AM Joël Krähemann wrote: > > Hi, > > thank you for reporting the bug

Bug#944589: gsequencer: stalls system

Hi, thank you for reporting the bug. Do you use a custom realtime kernel configuration? best regards, Joël On Tue, Nov 12, 2019 at 10:18 AM westlake wrote: > > Package: gsequencer > Version: 2.1.53-2 > Severity: important > > stalls a system that is running on an RT kernel >

Bug#933875: gsequencer: AgsThread synchronization broken

Source: gsequencer Severity: normal Dear Maintainer, GSequencer v2.2.10 introduced an experimental synchronization routine. AgsThread was improved by later versions. The application is not usable with current version in unstable and testing. Please update to latest upstream. regards, Joël --

Bug#928500: mentors.debian.net

Hi, FYI: https://mentors.debian.net/package/gsequencer cheers, Joël

Bug#928500: some notes

Hi, Section should be sound. * Package name: gsequencer Version : 2.1.53-2 Upstream Author : Joël Krähemann * URL : http://nongnu.org/gsequencer * License : GPLv3+ Section : section Since the repository contains newer

Bug#928500: additional information

* Package name: gsequencer Version : 2.1.53-2 Upstream Author : Joël Krähemann * URL : http://nongnu.org/gsequencer * License : GPLv3+ Section : optional It builds those binary packages: gsequencer

Bug#928500: sponsorship-requests: additional sponsor for gsequencer

Package: sponsorship-requests Severity: normal Dear Maintainer, Since my sponsor has not enough time to do a review for gsequencer within next days, he gave me an advice to look for an additional sponsor. https://salsa.debian.org/multimedia-team/gsequencer best regards, Joël Krähemann

Bug#927865: gsequencer: Important upstream bug-fixes

these patches can be provided to debian buster release via unstable update. by Joël Krähemann -- System Information: Debian Release: 10.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-3-amd64 (SMP w/24 CPU cores

Bug#923951: gsequencer: there are important upstream bug-fixes available

Source: gsequencer Version: 2.1.53 Severity: important Dear Maintainer, There are 3 important patches available with severity important: * ags_thread-posix-max-precision.patch * ags_simple_file_read_config.patch * ags_automation_get_value.patch The max precision and read config are related

Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())

Hi, Yes, it is an application bug. So, I fixed my upstream source. Just recognized calling pthread_cond_destroy() twice, later. Best regards, Joël On Wed, Mar 6, 2019 at 11:44 AM Florian Weimer wrote: > > * Joël Krähemann: > > > This happens as you call pthread_cond_destroy() tw

Bug#923802: Acknowledgement (pthread: dead-lock while pthread_cond_destroy())

Hi, This happens as you call pthread_cond_destroy() twice on the very same cond variable. Just attached a file to reproduce. Bests, Joël On Tue, Mar 5, 2019 at 4:27 PM Debian Bug Tracking System wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this

Bug#923802: pthread: dead-lock while pthread_cond_destroy()

Package: libc0.1-dev Version: 2.25-2 Severity: normal File: pthread Dear Maintainer, As checking why GSequencer's test didn't continue, I have discovered a dead-lock as calling pthread_cond_destroy() http://salsa.debian.org/multimedia-team/gsequencer Here is the command to reproduce:

Bug#923625: gsequencer: please update to latest version v2.1.64

a new branch 2.2.x of it. I as upstream expect that versioning is straight forward. But in debian is still version 2.1.53 published. Further I wish latest improvements and bug-fixes are included in debian. by Joël Krähemann -- System Information: Debian Release: buster/sid APT prefers unstable

Bug#919269: autopkgtest: provide stack-traces of crashed integration tests

Package: autopkgtest Severity: normal Dear Maintainer, I am the upstream of GSequencer. The software comes with system integration tests. https://salsa.debian.org/multimedia-team/gsequencer/blob/master/debian/tests/ags-integration-test The makefile compiles the integrations sets and runs them

Bug#909195: openshot-qt crashes during export

Hi, The media files are available here: http://krähemann.com/reportbug/openshot-qt/ Good luck, Joël On Wed, Sep 19, 2018 at 4:54 PM Joël Krähemann wrote: > > Package: openshot-qt > Version: 2.4.2+dfsg1-1 > Severity: normal > > Dear Maintainer, > > Openshot-qt cras

Bug#909195: openshot-qt crashes during export

Package: openshot-qt Version: 2.4.2+dfsg1-1 Severity: normal Dear Maintainer, Openshot-qt crashes during export. I use a screencast captured with `ffmpeg` and webcam `guvcview`. Audio is provided by gsequencer-2.0.13 as signed 16 bit WAV PCM. Thought I can export using:

Bug#898322: openshot: export crashes

Hi, I added deb-multimedia.org because no video editor was working. Bests, Joël On Fri, May 11, 2018 at 10:50 AM, Fabian Greffrath <fab...@debian.org> wrote: > Joël Krähemann wrote: >> iu openshot-qt 1:2.4.1-dmo2 > > Maybe this is your problem. Please replace this pack

Bug#898322: openshot: export crashes

Package: openshot Version: 2.4.1+dfsg1-1 Severity: normal Dear Maintainer, After my editing my screencast recorded using ffmpeg as MKV and audio exported from GSequencer as WAV. I basically combined MKV and WAV. The export crashes after writing a few MB. I wanted to export HD video 1080p as MP4

Bug#894386: libinstpatch: memory corruption in file IpatchSF2Reader.c

Source: libinstpatch Severity: normal Dear Maintainer, The file IpatchSF2Reader.c has seen in the upstream code base some fixes of potential memory corruption. This can lead to undefined behaviour. I provide a patch with the specific changes, fixing the issue. -- System Information: Debian

Bug#888470: pa_glib_main_loop_new()

Due to refactoring in GSequencer pa_main_loop_new() was not suitable anymore. Moving to pa_glib_main_loop_new() actually solved the issue. Bests, Joël

Bug#888470: pulseaudio: make pulseaudio callback less penetrant

Package: pulseaudio Version: 11.1-4 Severity: normal File: pulseaudio Dear Maintainer, pulseaudio callback is such penetrant that it brings down my desktop environment. The current situation is as running GSequencer with pulseaudio on a macbook pro 2016 it slows down the entire desktop. The

Bug#887723: mate-screensaver: the screen stays darken and desktop not available anymore

Package: mate-screensaver Version: 1.18.2-1 Severity: serious Justification: the desktop must be available Dear Maintainer, I have installed mate-desktop and its screensaver. The screen stays darken after a while it was darken. Hitting my Logitech USB wireless keyboard doesn't show up login

Bug#882513: gsequencer: autopkgtest is broken

Hi, My sponsor created a new package. It should be fixed now. https://tracker.debian.org/news/893466 Bests, Joël On Sat, Nov 25, 2017 at 8:35 AM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi, > Just provided a new upstream package v1.1.5 and made debian > repository fit

Bug#882513: gsequencer: autopkgtest is broken

Hi, Just provided a new upstream package v1.1.5 and made debian repository fit for autopkgtest. Best regards, Joël On Fri, Nov 24, 2017 at 10:55 AM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi, > Since I (upstream) doesn't have the infrastructure to run integration > tes

Bug#882513: gsequencer: autopkgtest is broken

at 10:50 AM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi, > Just providing a patch. The target ags-integration-test wasn't take care > much. > > Apply the patch fix-integration-tests.patch > `patch -p1 < ../nongnu/gsequencer/fix-integration-tests.patch` > run

Bug#882513: gsequencer: autopkgtest is broken

ests, Joël On Fri, Nov 24, 2017 at 9:26 AM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi Dimitri, > The make target ags-integration-test runs against installed libraries. Just > run > `make check` which contains the very same functional tests. But this requires > to remove

Bug#882513: gsequencer: autopkgtest is broken

against installed gsequencer package. Further libgsequencer.so can't be a private library if you want to run them. So additional patch would be required to change library installation path. Best regards, Joël Krähemann On Thu, Nov 23, 2017 at 5:01 PM, Dimitri John Ledkov <x...@ubuntu.com>

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Hi Code like this might destabilize the operating system and compromise debian. There is a good reason why glib-2.0 uses void pointers. Bests, Joël On Fri, Aug 11, 2017 at 9:23 PM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > Might be just a programming error. But

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

uarantees this points to at least capacity bytes of allocated > memory (though only size bytes of that are valid events). > */ > uint8_t* data; > > > not a bug. > > On 08/11/2017 08:20 PM, Joël Krähemann wrote: >> Hi >> >> For sure you can cast any pointer. But fee

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Hi For sure you can cast any pointer. But feels somehow wrong. The opinion was the specs are always correct. Bests, Joël On Fri, Aug 11, 2017 at 8:12 PM, Jaromír Mikeš <mira.mi...@gmail.com> wrote: > > > 2017-08-10 16:23 GMT+02:00 Joël Krähemann <jkraehem...@gmail.co

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Hi James, It is common that you use for storing uint8_t an entire word. The use of a uint8_t pointer confused me as you are pointing to a struct. Bests, Joël On Thu, Aug 10, 2017 at 4:10 PM, James Cowgill <jcowg...@debian.org> wrote: > Hi, > > On 10/08/17 08:31, Joël

Bug#871649: lv2-dev: abuse of non portable pointer of uint8_t type

Package: lv2-dev Version: 1.14.0~dfsg1-1 Severity: important Dear Maintainer, The following header makes use of smallest possible pointer in LV2_Event_Buffer struct's data field. lv2/lv2plug.in/ns/ext/event/event.h Please change it to biggest possible pointer. It should be definitely void*

Bug#869152: lv2-dev: type conflict of and

Package: lv2-dev Version: 1.14.0~dfsg1-1 Severity: important Dear Maintainer, As doing #include before I get following compiler errors: /usr/lib/lv2/atom.lv2/forge.h:114:11: error: two or more data types in declaration specifiers LV2_URID Bool; ^ /usr/lib/lv2/atom.lv2/forge.h: In function

Bug#861908: gsequencer: testsuite crashes if AddressSanitizer is enabled

Hi I have targeted the issue during release of gsequencer-0.8.7. I think we should close this bug. Bests, Joël On Mon, May 22, 2017 at 12:19 AM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > Just figured out that are mainly issues related > to memory leakes within

Bug#861908: gsequencer: testsuite crashes if AddressSanitizer is enabled

at 11:38 PM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > Just recognized every _ unit test fails. > So I'm busy for a while. > > Cheers, > Joël > > > On Sun, May 21, 2017 at 11:15 PM, Joël Krähemann <jkraehem...@gmail.com> > wrote: >> Hi

Bug#861908: gsequencer: testsuite crashes if AddressSanitizer is enabled

Hi Just recognized every _ unit test fails. So I'm busy for a while. Cheers, Joël On Sun, May 21, 2017 at 11:15 PM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > the stack-trace above should be fixed commit: > > http://git.savannah.nongnu.org/cgit/gsequence

Bug#861908: gsequencer: testsuite crashes if AddressSanitizer is enabled

Hi the stack-trace above should be fixed commit: http://git.savannah.nongnu.org/cgit/gsequencer.git/commit/?h=0.8.x=d6a5a226fa01525bbcce3824dfb5f7e82767eb62 Since I didn't test with address sanitizer this wasn't recognized. I just do run it now. Might be there other issues. Bests, Joël On

Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test

Hi again Sorry wrong context. It is the problem for sure: Since it is used by AgsAutomationEditor, too. Joël On Fri, May 5, 2017 at 6:31 PM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > The flag was set. However it is not that beautiful. > So it can't be the

Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test

Hi The flag was set. However it is not that beautiful. So it can't be the problem. https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/ags/X/ags_editor.c#n222 Bests, Joël On Fri, May 5, 2017 at 6:09 PM, James Cowgill <jcowg...@debian.org> wrote: > Hi, > > On 05/05

Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test

ests, Joël On Wed, May 3, 2017 at 1:40 PM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > I just tried to run `make check` in a mipsel chroot on tty2. > > As running ./ags_xorg_application_context_test I get: > > Suite: AgsXorgApplicationContextTest > Test:

Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test

Unsupported ioctl: cmd=... Bests, Joël On Tue, May 2, 2017 at 6:53 PM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > I have experienced on some other architectures with > ags_xorg_application_context_test > the same problems. It was not evident to me if the problem was

Bug#861645: gsequencer FTBFS on mips/mipsel: FAIL: ags_xorg_application_context_test

Hi I have experienced on some other architectures with ags_xorg_application_context_test the same problems. It was not evident to me if the problem was related to Gtk+-2.0 or xvfb-run since the stack-trace ended as doing gtk_widget_show(window); However other architectures just pass the test.

Bug#858285: gsequencer: New upstream version available 0.7.122.7

Source: gsequencer Severity: wishlist Dear Maintainer, The new package comes with a lot improvements. Thought the important ones are provided by a patch. Maintenance would be just much easier as providing this package. -- System Information: Debian Release: 9.0 APT prefers unstable APT

Bug#858283: gsequencer: GSequencer crashes as no soundcard configured

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, GSequencer allows configuration in place. As removing all soundcards and adding certain machines it does SIGSEGV. This happens because of a NULL pointer dereference. GSequencer shall not crash under any circumstances.

Bug#857915: gsequencer: should link libraries using LIBADD instead of LDFLAGS

Hi I'm unsure about the issue. Could you provide an example? cheers, Joël On Thu, Mar 16, 2017 at 11:43 AM, James Cowgill wrote: > Source: gsequencer > Version: 0.7.122-2 > Severity: normal > > Hi, > > gsequencer incorrectly links libraries in Makefile.am using LDFLAGS >

Bug#857948: Acknowledgement (gsequencer: missing mutex locks might crash the application)

Hi Just merged related patches to one file: https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/debian/patches/fix-missing-mutices.diff bests, Joël On Thu, Mar 16, 2017 at 4:27 PM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report

Bug#857934: Acknowledgement (gsequencer: configuration in-place broken thread frequency)

Hi The patches were provided prior and are now merged to on patch file because its related to each other: https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/debian/patches/fix-broken-thread-frequency.diff On Thu, Mar 16, 2017 at 2:00 PM, Debian Bug Tracking System

Bug#857948: gsequencer: missing mutex locks might crash the application

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, Some mutex locks are missing. They protect common memory of threads. The data-race may crash GSequencer. It should add some mutexes. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500,

Bug#857947: gsequencer: possible data-race as clearing buffer of soundcard

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, The soundcard output is affected by a data-race. While clearing the output buffer, a data race is possible. Resulting in corrupted audio export or playback. The possibility of an application crash exists. The clearing

Bug#857937: Acknowledgement (gsequencer: memory leaks while g_timeout_add() function in GUI)

Hi Just added the needed patches: https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/debian/patches/fix-leak-while-g-timeout-function.diff bests, Joël On Thu, Mar 16, 2017 at 2:15 PM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug

Bug#857931: Acknowledgement (gsequencer: AgsSynth possible division by zero by oscillator)

Hi Just provide the diff fixing the issue: https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/debian/patches/fix-possible-division-by-zero.diff bests, Joël On Thu, Mar 16, 2017 at 1:51 PM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug

Bug#857933: Acknowledgement (gsequencer: The MIDI connection dialog is not provided by restoring AgsLv2Bridge)

Hi Just added the diff fixing missing midi connection dialog after restore: https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/debian/patches/fix-missing-midi-connection-dialog.diff bests, Joël On Thu, Mar 16, 2017 at 1:57 PM, Debian Bug Tracking System

Bug#857935: Acknowledgement (gsequencer: SIGSEGV as doing NULL pointer dereference as restoring AgsFFPlayer)

Hi all Just provide the patch in alioth git repo: https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/debian/patches/fix-null-pointer-dereference.diff bests, Joël On Thu, Mar 16, 2017 at 2:03 PM, Debian Bug Tracking System wrote: > Thank you for filing a

Bug#857936: gsequencer: duplicated flag AGS_MIDI_PARSER_EOT makes header useless

Hi just provided the patch https://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/tree/debian/patches/fix-duplicated-flag-definition.diff bests, Joël On Thu, Mar 16, 2017 at 2:05 PM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Source: gsequencer > Version: 0.7.122-

Bug#857937: gsequencer: memory leaks while g_timeout_add() function in GUI

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, The missing free of a string and wrong free of a glist leaks memory. This happens during g_timeout_add() function. Since it polls it continuesly leaks memory. The system shouldn't run out of memory. -- System

Bug#857910: gsequencer: GObject::dispose() is not implemented

Hi Note some finalize() methods don't g_object_unref() all struct fields. It has a strong relation to this bug. Further GObject::dispose() requires Bug#857930 to be fixed. Bests, Joël On Thu, Mar 16, 2017 at 1:25 PM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > Basica

Bug#857936: gsequencer: duplicated flag AGS_MIDI_PARSER_EOT makes header useless

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, libags-audio.h is useless because there is a duplicated flag. It should not occure twice. The second AGS_MIDI_PARSER_EOT should be AGS_MIDI_BUILDER_EOT. Development with libags-audio.h is not possible. It should be

Bug#857935: gsequencer: SIGSEGV as doing NULL pointer dereference as restoring AgsFFPlayer

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, The restore of AgsFFPlayer crashes as no Soundfont2 file is selected. It causes SIGSEGV due to NULL pointer dereference. GSequencer should not crash. -- System Information: Debian Release: 9.0 APT prefers unstable

Bug#857934: gsequencer: configuration in-place broken thread frequency

Source: gsequencer Version: gsequencer Severity: important Dear Maintainer, The configuration in place lacks updating thread frequencies. As modifying buffer size or samplerate the refresh rate changes. It shall update thread frequencies. Note it causes useless audio output. -- System

Bug#857933: gsequencer: The MIDI connection dialog is not provided by restoring AgsLv2Bridge

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, After restore GSequencer doesn't provide the MIDI connection editor. As adding the machine immediately the MIDI connection editor is there. During restore there is a function call missing. You expect the MIDI connection

Bug#857931: gsequencer: AgsSynth possible division by zero by oscillator

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, The user can select a frequency of 0 what leads to a division by 0. This causes a SIGSEGV and the application gets killed. The application shouldn't crash at all. -- System Information: Debian Release: 9.0 APT prefers

Bug#857930: gsequencer: Wrong GParamSpec of mixed properties containing GObject and GList

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, Some mixed properties do use g_param_spec_object() instead of g_param_spec_pointer(). But g_value_set_object() doesn't work for GList. The property doesn't return a value while calling g_object_get() or alike. It should

Bug#857910: gsequencer: GObject::dispose() is not implemented

Hi Basically the changes from 0.7.122.6 to 0.7.122.7 I have dedicated this release to memory-leaks. Note it includes some bug-fixes we should check if they are applicable to 0.7.122-2 http://download.savannah.gnu.org/releases/gsequencer/stable Best, Joël On Thu, Mar 16, 2017 at 11:53 AM, Tino

Bug#857910: gsequencer: GObject::dispose() is not implemented

Hi Upstream includes the wished changes. We could do a diff and strip unwanted changes. Bests, Joël On Thu, Mar 16, 2017 at 11:12 AM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Source: gsequencer > Version: 0.7.122-2 > Severity: important > > Dear Maintainer,

Bug#857910: gsequencer: GObject::dispose() is not implemented

Source: gsequencer Version: 0.7.122-2 Severity: important Dear Maintainer, GObject::dispose() is not implemented. But it is necessary in order to release circular dependencies properly. It causes to application to leak memory while playback. Only by program termination it is released. The

Bug#853936: unblock: gsequencer/0.7.122-2

/changelog 2017-01-03 17:02:45.0 +0100 +++ gsequencer-0.7.122/debian/changelog 2017-02-01 11:14:14.0 +0100 @@ -1,3 +1,13 @@ +gsequencer (0.7.122-2) unstable; urgency=medium + + [ Joël Krähemann ] + * Disabled ALSA on non-linux, and enabled OSS4 only on kFreeBSD +(Closes: #852985

Bug#852985: gsequencer: please do not build-depend on oss4-dev on Linux

Hi The patch looks fine. There should be no problem as passing this configure flag. I even used gsequencer on linuxfromscratch.org based system without having OSS4 at all. Note you can disable it for GNU/Hurd, as well. So JACK is the only output sink. Bests, Joël On Sun, Jan 29, 2017 at 5:18

Bug#837606: general: system freeze

Hi I experienced the same as developing GSequencer probably a concurrency issue. I had to fix it. This can happen may be with unintialized mutices or conditional locks. Bests, Joël On Tue, Sep 13, 2016 at 4:15 PM, Abou Al Montacir wrote: > Control: reopen -1 > > >

Bug#836328: gsequencer: FTBFS on non-Linux: ALSA too old (1.0.5 vs. 1.0.25)

Hi Upstream 0.7.64 contains now OSS support however alsa still required in order to do DSSI and Lv2. I have replaced snd_midi_event_decode() with ags_midi_buffer_util_decode(). Bests, Joël On Mon, Sep 5, 2016 at 10:35 AM, Joël Krähemann <jkraehem...@gmail.com> wrote: > Hi > > I'

Bug#836328: gsequencer: FTBFS on non-Linux: ALSA too old (1.0.5 vs. 1.0.25)

Hi I'm doing my best to port it. Most of the work has been fulfilled so far. I just need to add a g_strv_length(), g_strv_contains() and snd_midi_event_decode() replacement. Since these functions aren't big it won't take too long. A bigger task would be adding OSS output. Bests, Joël On Thu,

Bug#836327: gsequencer: FTBFS on mips and powerpc: ags_functional_audio_test segmentation fault

Hi Yesterday, I was providing an new tarball 0.7.63 making the tests pass. ags_functional_audio_test.c needs your soundcard but shouldn't crash if it's not available. Further there was an issue with $(HOME)/.gsequencer/ags.conf having jack=enabled. Since jack support is a work in progress it is

Bug#836326: gsequencer: FTBFS on i386: ags_channel_test segmentation fault

Hi Yesterday, I was providing a new tarball 0.7.63 fixing the unit tests. They should all pass for now. Bests, Joël On Thu, Sep 1, 2016 at 7:10 PM, Aaron M. Ucko wrote: > Source: gsequencer > Version: 0.7.62-1 > Severity: serious > Justification: fails to build from source

Bug#807823: Patch to fix the issue

Hi I have just found the dead-lock. The issue should be fixed. cheers, Joël Index: libinstpatch-1.0.0/libinstpatch/IpatchBase.c === --- libinstpatch-1.0.0.orig/libinstpatch/IpatchBase.c 2010-10-25 21:03:42.0 +0200 +++

Bug#807823: test case to reconstruct the situation

Hi I'm just doing a test-case: https://github.com/gsequencer/gsequencer/blob/0.6.0/src/ags/test/ags_libinstpatch_test.c cheers, Joël

Bug#807823: dead-lock as calling functions from different threads

Package: libinstpatch-1.0-0 Version: 1.0.0-4 Severity: important Tags: upstream -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)

Bug#807823: detailed stack-trace

Hi, here you have a stack-trace with debugging symbols. One thread opens the file an other one reads of it. Thread 35 (Thread 0x7f45cc8a0700 (LWP 9062)): #0 0x7f45f29bc7fc in __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7f45f29b84d4 in

Bug#807823: calling functions

Here's an overview what I'm doing ... Thread A: /* open file */ ipatch_file_identify_open(); ipatch_sf2_reader_new(); ipatch_sf2_reader_load(); ipatch_convert_object_to_type(); ipatch_container_get_children(); /* select preset */ ipatch_container_get_children(); ipatch_sf2_preset_get_name();

  1   2   >