Bug#1054514: linux-image-6.1.0-13-amd64: Debian VM with qxl graphics freezes frequently
On Tue, Oct 24, 2023 at 11:09:10PM +0200, Salvatore Bonaccorso wrote: > Hi Timo, > > On Tue, Oct 24, 2023 at 11:14:32PM +0300, Timo Lindfors wrote: > > Package: src:linux > > Version: 6.1.55-1 > > Severity: normal > > > > Steps to reproduce: > > 1) Install Debian 12 as a virtual machine using virt-manager, choose qxl > >graphics card. You only need basic installation without wayland or X. > > 2) Login from the console and save thë following to reproduce.bash: > > > > #!/bin/bash > > > > chvt 3 > > for j in $(seq 80); do > > echo "$(date) starting round $j" > > if [ "$(journalctl --boot | grep "failed to allocate VRAM BO")" != "" ]; > > then > > echo "bug was reproduced after $j tries" > > exit 1 > > fi > > for i in $(seq 100); do > > dmesg > /dev/tty3 > > done > > done > > > > echo "bug could not be reproduced" > > exit 0 > > > > > > 3) Run chmod a+x reproduce.bash > > 4) Run ./reproduce.bash and wait for up to 20 minutes. > > > > Expected results: > > 4) The system prints a steady flow of text without kernel error messages > > > > Actual messages: > > 4) At some point the text stops flowing and the script prints "bug was > >reproduced". If you run "journalctl --boot" you see > > > > kernel: [TTM] Buffer eviction failed > > kernel: qxl :00:02.0: object_init failed for (3149824, 0x0001) > > kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO > > > > > > > > More info: > > 1) The bug does not occur if I downgrade the kernel to > >linux-image-5.10.0-26-amd64_5.10.197-1_amd64.deb from Debian 11. > > 2) I used the following test_linux.bash to bisect this issue against > >upstream source: > > > > #!/bin/bash > > set -x > > > > gitversion="$(git describe HEAD|sed 's@^v@@')" > > > > git checkout drivers/gpu/drm/ttm/ttm_bo.c include/drm/ttm/ttm_bo_api.h > > git show bec771b5e0901f4b0bc861bcb58056de5151ae3a | patch -p1 > > # Build > > cp ~/kernel.config .config > > # cp /boot/config-$(uname -r) .config > > # scripts/config --enable LOCALVERSION_AUTO > > # scripts/config --disable DEBUG_INFO > > # scripts/config --disable SYSTEM_TRUSTED_KEYRING > > # scripts/config --set-str SYSTEM_TRUSTED_KEYS '' > > # scripts/config --disable STACKPROTECTOR_STRONG > > make olddefconfig > > # make localmodconfig > > make -j$(nproc --all) bindeb-pkg > > rc="$?" > > if [ "$rc" != "0" ]; then > > exit 125 > > fi > > git checkout drivers/gpu/drm/ttm/ttm_bo.c include/drm/ttm/ttm_bo_api.h > > > > package="$(ls --sort=time ../linux-image-*_amd64.deb|head -n1)" > > version=$(echo $package | cut -d_ -f1|cut -d- -f3-) > > > > if [ "$gitversion" != "$version" ]; then > > echo "Build produced version $gitversion but got $version, ignoring" > > #exit 255 > > fi > > > > # Deploy > > scp $package target:a.deb > > ssh target sudo apt install ./a.deb > > ssh target rm -f a.deb > > ssh target ./grub_set_default_version.bash $version > > ssh target sudo shutdown -r now > > sleep 40 > > > > detected_version=$(ssh target uname -r) > > if [ "$detected_version" != "$version" ]; then > > echo "Booted to $detected_version but expected $version" > > exit 255 > > fi > > > > # Test > > exec ssh target sudo ./reproduce.bash > > > > > > Bisect printed the following log: > > > > git bisect start > > # bad: [ed29c2691188cf7ea2a46d40b891836c2bd1a4f5] drm/i915: Fix userptr so > > we do not have to worry about obj->mm.lock, v7. > > git bisect bad ed29c2691188cf7ea2a46d40b891836c2bd1a4f5 > > # bad: [762949bb1da78941b25e63f7e952af037eee15a9] drm: fix > > drm_mode_create_blob comment > > git bisect bad 762949bb1da78941b25e63f7e952af037eee15a9 > > # bad: [e40f97ef12772f8eb04b6a155baa1e0e2e8f3ecc] drm/gma500: Drop > > DRM_GMA600 config option > > git bisect bad e40f97ef12772f8eb04b6a155baa1e0e2e8f3ecc > > # bad: [5a838e5d5825c85556011478abde708251cc0776] drm/qxl: simplify > > qxl_fence_wait > > git bisect bad 5a838e5d5825c85556011478abde708251cc0776 > > # bad: [d2b6f8a179194de0ffc4886ffc2c4358d86047b8] Merge tag > > 'xfs-5.13-merge-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux > > git bisect bad d2b6f8a179194de0ffc4886ffc2c4358d86047b8 > > # bad: [68a32ba14177d4a21c4a9a941cf1d7aea86d436f] Merge tag > > 'drm-next-2021-04-28' of git://anongit.freedesktop.org/drm/drm > > git bisect bad 68a32ba14177d4a21c4a9a941cf1d7aea86d436f > > # bad: [0698b13403788a646073fcd9b2294f2dce0ce429] drm/amdgpu: skip > > PP_MP1_STATE_UNLOAD on aldebaran > > git bisect bad 0698b13403788a646073fcd9b2294f2dce0ce429 > > # bad: [e1a5e6a8c48bf99ea374fb3e535661cfe226bca4] drm/doc: Add RFC section > > git bisect bad e1a5e6a8c48bf99ea374fb3e535661cfe226bca4 > > # bad: [ed29c2691188cf7ea2a46d40b891836c2bd1a4f5] drm/i915: Fix userptr so > > we do not have to worry about obj->mm.lock, v7. > > git bisect bad ed29c2691188cf7ea2a46d40b891836c2bd1a4f5 > > # bad: [2c8ab3339e398bbbcb0980933e266b93bedaae52] drm/i915: Pin timeline > > map after first timeline pin, v4
Bug#1040618: xwayland: xwininfo, xkill doesn't change cursor when prompted to click
Package: xwayland Version: 2:22.1.9-1 Severity: important Dear Maintainer, I set up a keyboard shortcut to xkill in GNOME when I was in Debian bookworm. The shortcut worked there (the cursor changed to cross in order to select window to be killed). Then I upgraded to recent testing, at which xkill doesn't change cursor anymore. I have another DE installed (KDE) and can confirm this regression still occurs there. This regression doesn't occur on GNOME on Xorg session, hence reporting this as xwayland bug. Looking through journalctl, I see: ``` Jul 08 08:15:39 debian systemd[4747]: Started app-gnome-xkill-6559.scope - Application launched by gsd-media-keys. Jul 08 08:15:40 debian systemd[4747]: Started app-gnome-xkill-6564.scope - Application launched by gsd-media-keys. Jul 08 08:15:41 debian systemd[4747]: Reached target gnome-session-x11-services.target - GNOME session X11 services. Jul 08 08:15:41 debian gnome-shell[6576]: The XKEYBOARD keymap compiler (xkbcomp) reports: Jul 08 08:15:41 debian gnome-shell[6576]: > Warning: Unsupported maximum keycode 708, clipping. Jul 08 08:15:41 debian gnome-shell[6576]: > X11 cannot support keycodes above 255. Jul 08 08:15:41 debian gnome-shell[6576]: Errors from xkbcomp are not fatal to the X server Jul 08 08:15:41 debian systemd[4747]: Starting org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service... Jul 08 08:15:46 debian dnsmasq-dhcp[1664]: Ignoring domain mail for DHCP host name ohmymail Jul 08 08:15:47 debian systemd[4747]: Started org.gnome.SettingsDaemon.XSettings.service - GNOME XSettings service. Jul 08 08:15:47 debian systemd[4747]: Reached target gnome-session-x11-services-ready.target - GNOME session X11 services. Jul 08 08:15:48 debian gnome-shell[4944]: ATK Bridge is disabled but a11y has already been enabled. Jul 08 08:15:49 debian xkill[6564]: xkill: unable to grab cursor Jul 08 08:15:49 debian xkill[6564]: Select the window whose client you wish to kill with button 1 ``` Thanks. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.38-local (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xwayland depends on: ii libc6 2.36-9 ii libdrm2 2.4.115-1 ii libepoxy0 1.5.10-1 ii libgbm1 22.3.6-1+deb12u1 ii libgcrypt20 1.10.2-2 ii libgl1 1.6.0-1 ii libpixman-1-0 0.42.2-1 ii libtirpc3 1.3.3+ds-1 ii libwayland-client0 1.21.0-1 ii libxau6 1:1.0.9-1 ii libxcvt00.1.2-1 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.6-1 ii libxshmfence1 1.3-1 ii xserver-common 2:21.1.7-3 xwayland recommends no packages. xwayland suggests no packages. -- no debconf information
Bug#1037258: curl -I (HEAD request) fails with HTTP/2 against a Debian Apache instance
On Sun, Jun 11, 2023 at 01:56:21AM -0400, Sergio Durigan Junior wrote: > On Saturday, June 10 2023, Samuel Henrique wrote: > > > Hello, > > > > I'm not able to reproduce the issue on Bookworm with a HTTP2 localhost > > apache server. > [...] > > Hey, > > I was able to find another URL that triggers the same issue. This one: > > > https://chinarising.puntopress.com/wp-content/uploads/2023/04/Press-TV-KSA-Iran.mp3 OK so I tried reproducing it by installing WP on localhost (actually behind LXD container). The container is Debian bookworm (with deb.sury.org repo added). apache2 site configuration (`/etc/apache2/sites-enabled/test.conf`) is: ``` ServerName test.test ServerAdmin webmas...@test.test DocumentRoot/srv/www/test.test Redirect301 / https://wp.bagas.me ServerName test.test ServerAdmin webmas...@test.test DocumentRoot/srv/www/test.test DirectoryIndex index.php index.html Protocols h2 http/1.1 ... ... AllowOverride all Require all granted SetHandler "proxy:unix:/run/php/php8.2-fpm.sock|fcgi://localhost" ``` (requires mod_proxy and mod_proxy_fcgi for apache2 and php8.2-fpm package). WP configuration is pretty standard and it's rather fresh install (see the web for WP installation procedures). Log in to WP dashboard and upload random .mp3 files. Once uploaded, click `Copy URL to clipboard` besides the uploaded file and feed it to curl. In summary, I can't reproduce this bug either with above setup. Thanks. -- An old man doll... just what I always wanted! - Clara signature.asc Description: PGP signature
Bug#1040190: git: Please package new version 2.41.0
Package: git Version: 1:2.40.1-1 Severity: normal Tags: sid trixie Dear Jonathan, There is a latest Git release (v2.41.0), which is available at [1]. The release was already a month ago, and AFAIK the upstream is about to release new point release soon (which will be v2.41.1). Please consider packaging it, thanks! [1] https://mirrors.edge.kernel.org/pub/software/scm/git/git-2.41.0.tar.gz -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.4.0-local (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages git depends on: ii git-man 1:2.40.1-1 ii libc62.36-9 ii libcurl3-gnutls 7.88.1-10 ii liberror-perl0.17029-2 ii libexpat12.5.0-2 ii libpcre2-8-0 10.42-1 ii perl 5.36.0-7 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages git recommends: ii ca-certificates 20230311 ii less 590-2 ii openssh-client [ssh-client] 1:9.3p1-1 ii patch2.7.6-7 Versions of packages git suggests: ii gettext-base 0.21-12 pn git-cvs pn git-daemon-run | git-daemon-sysvinit pn git-doc ii git-email 1:2.40.1-1 pn git-gui pn git-mediawiki pn git-svn pn gitk pn gitweb -- no debconf information
Bug#1038315: lxd: AppArmor profile violations cause PrivateNetwork=yes services in the container fail to start
On 6/24/23 22:19, Mathias Gibbens wrote: >> systemd-hostnamed.service is probably also affected, but in my case I >> paved over the issue by setting PrivateNetwork=no in an override. > > For the moment setting PrivateNetwork=no for affected services is > probably a better approach than totally removing the container's > apparmor profile. > Hi Mathias, sorry for late reply. Indeed, overriding affected services with PrivateNetwork=no works. Thanks for the better workaround! -- An old man doll... just what I always wanted! - Clara
Bug#1038315: lxd: AppArmor profile violations cause PrivateNetwork=yes services in the container fail to start
Package: lxd Version: 5.0.2-5 Severity: important Dear Maintainer, I spin up containers using LXD. I'm primarily doing this for learning purposes (for example installing and configuring web services). I launched my first container (test) to get my feet wet by: ``` lxc launch images:debian/12 test ``` When I tried to set hostname in the container via (`hostnamectl set-hostname test.test`), I got `Could not set pretty hostname: Connection timed out` error. journalctl on the container showed errors related to network namespacing: ``` Jun 17 03:03:12 test dbus-daemon[81]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.7' (uid=0 pid=104 comm="hostnamectl set-hostname test.test") Jun 17 03:03:12 test (ostnamed)[105]: systemd-hostnamed.service: Failed to set up network namespacing: Permission denied Jun 17 03:03:12 test systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Jun 17 03:03:12 test (ostnamed)[105]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied Jun 17 03:03:12 test systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK Jun 17 03:03:12 test systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'. Jun 17 03:03:12 test systemd[1]: Failed to start systemd-hostnamed.service - Hostname Service. Jun 17 03:03:37 test dbus-daemon[81]: [system] Failed to activate service 'org.freedesktop.hostname1': timed out (service_start_timeout=25000ms) ``` dmesg on the host revealed that these errors above are due to AppArmor policy violations: ``` [10673.299973] audit: type=1400 audit(1686970915.519:84): apparmor="DENIED" operation="file_lock" profile="lxd-myself_test_" pid=12984 comm="(crub_all)" family="unix" sock_type="dgram" protocol=0 requested_mask="send" [10673.299988] audit: type=1400 audit(1686970915.519:85): apparmor="DENIED" operation="file_lock" profile="lxd-myself_test_" pid=12984 comm="(crub_all)" family="unix" sock_type="dgram" protocol=0 requested_mask="send" [10675.793944] audit: type=1400 audit(1686970918.015:86): apparmor="DENIED" operation="file_lock" profile="lxd-myself_test_" pid=12991 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 requested_mask="send" [10675.793966] audit: type=1400 audit(1686970918.015:87): apparmor="DENIED" operation="file_lock" profile="lxd-myself_test_" pid=12991 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 requested_mask="send" [10750.671804] audit: type=1400 audit(1686970992.896:88): apparmor="DENIED" operation="file_lock" profile="lxd-myself_test_" pid=13038 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 requested_mask="send" [10750.671817] audit: type=1400 audit(1686970992.896:89): apparmor="DENIED" operation="file_lock" profile="lxd-myself_test_" pid=13038 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 requested_mask="send" ``` >From the upstream discussion [1], the workaround is to put AppArmor profile for the container unconfined. To do this, I have to run: ``` lxc config set test raw.lxc "lxc.apparmor.profile=unconfined" ``` See lxc.container.conf(5) manpage [2] for explanation of lxc config key. The upstream discussion stated that this bug should have been already fixed in recent systemd, AppArmor, and Linux kernel versions (at least as shipped in Ubuntu Bionic release). However, I can (still) reproduce it on Debian testing. Thanks. [1]: https://discuss.linuxcontainers.org/t/bionic-containers-on-xenial-host-systemd-hostnamed-unable-to-start/1732 [2]: https://manpages.ubuntu.com/manpages/lunar/en/man5/lxc.container.conf.5.html -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lxd depends on: ii adduser 3.134 ii attr 1:2.5.1-4 ii ca-certificates 20230311 ii init-system-helpers 1.65.2 ii libacl1 2.3.1-3 ii libc62.36-9 ii libcap2 1:2.66-4 ii libdqlite0 1.11.1-1 ii libgcc-s112.2.0-14 ii liblxc-common1:5.0.2-1 ii liblxc1 1:5.0.2-1 ii libsqlite3-0 3.40.1-2 ii libudev1 252.6-1 ii lxcfs5.0.3-1 ii lxd-client 5.0.2-5 ii rsync3.2.7-1 ii squashfs-tools 1:4.5.1-1 ii uidmap 1:4.13+dfsg1-1+b1 ii xz-utils 5.4.1-0.2 Versions of packages lxd recommends: ii apparmor 3.0.8-3 ii dnsmasq-base [dnsmasq-base] 2.89-1 ii lxd-agent5.0.2-5 Versions of packages lxd suggests
Bug#889313: O: directfb -- direct frame buffer graphics library
On 4/12/23 15:47, Sebastian Ramacher wrote: >> Sebastian, do you agree on removal? > > I do not care either way. > > For removal, the following packages need to be fixed first: > > Checking reverse dependencies... > # Broken Depends: > baresip: baresip-core > directvnc: directvnc > gst-plugins-bad1.0: gstreamer1.0-plugins-bad > links2: links2 > xine-lib-1.2: libxine2-console > libxine2-x > > # Broken Build-Depends: > baresip: libdirectfb-dev > directvnc: libdirectfb-dev (0.9.24 >=) > gst-plugins-bad1.0: libdirectfb-dev > links2: libdirectfb-dev > xine-lib-1.2: libdirectfb-dev > Have bugs been filed for these revdeps yet? -- An old man doll... just what I always wanted! - Clara
Bug#889313: O: directfb -- direct frame buffer graphics library
On Sun, Jan 29, 2023 at 01:13:43PM +0100, Diederik de Haas wrote: > On 3 Feb 2018 15:42:21 +0100 Sebastian Ramacher wrote: > > Package: wnpp > > > > Note that upstream appears to MIA. > > https://web.archive.org/web/20170603093935/http://www.directfb.net/ seems to > be the last capture which at least shows a working home page, after that it > seems to be all redirects to non-existing/spam stuff. > > But it seems like all the links in the sidebar still don't work, including > the > link to the Source Code ... So maybe it's time to remove the package, right? Sebastian, do you agree on removal? -- An old man doll... just what I always wanted! - Clara
Bug#1021056: free(): invalid pointer and double free or corruption (!prev) when taking screenshot of 540x360 video
Package: vlc Version: 3.0.17.4-0+deb11u1 Severity: normal I discovered this bug when I tried to take the screenshot of "I Died in a Car Crash" contemporary dance video by Ana Zimhart ([1]), which have been downloaded to my computer. The video resolution was 540x360. When the video was played at position 1:53 (when Ana did arc penché trick at 90 degrees leg position), I took a snapshot. Instead of vlcsnap-* image on ~/Pictures be generated, VLC exited with invalid pointer error on free(). The tail from "vlc -vvv" was: ``` [56b17d80] main filter debug: Filter 'VAAPI filters' (0x56b184f0) appended to chain [56b1c9d0] main filter debug: looking for video converter module matching "any": 23 candidates [56b1c9d0] swscale filter debug: 540x360 (544x368) chroma: I420 -> 540x360 (544x368) chroma: RV24 with scaling using Bicubic (good quality) [56b1c9d0] main filter debug: using video converter module "swscale" [56b17d80] main filter debug: Filter 'Swscale' (0x56b1c9d0) appended to chain [56b17d80] main filter debug: using video converter module "chain" [56b16560] main filter debug: Filter 'chain' (0x56b17d80) appended to chain [56b2f2f0] main filter debug: looking for video converter module matching "any": 23 candidates [swscaler @ 0x56b31e40] Forcing full internal H chroma due to input having non subsampled chroma [56b2f2f0] swscale filter debug: 540x360 (544x368) chroma: RV24 -> 540x360 (540x360) chroma: RV24 with scaling using Bicubic (good quality) [56b2f2f0] main filter debug: using video converter module "swscale" [56b16560] main filter debug: Filter 'Swscale' (0x56b2f2f0) appended to chain [56b16560] main filter debug: using video converter module "chain" [56b0ee00] main encoder debug: removing module "png" [56b16560] main filter debug: removing module "chain" [56b17d80] main filter debug: removing module "chain" [56b184f0] main filter debug: removing module "vaapi_filters" free(): invalid pointer ``` The log above was from gdb session. When vlc was invoked outside gdb with the reproducer above, I got double free or corruption (!prev) error. The tail log for that case was: ``` [7efe3044dcb0] main filter debug: Filter 'VAAPI filters' (0x7efe300d5d30) appended to chain [7efe300d0f70] main filter debug: looking for video converter module matching "any": 23 candidates [7efe300d0f70] swscale filter debug: 540x360 (544x368) chroma: I420 -> 540x360 (544x368) chroma: RV24 with scaling using Bicubic (good quality) [7efe300d0f70] main filter debug: using video converter module "swscale" [7efe3044dcb0] main filter debug: Filter 'Swscale' (0x7efe300d0f70) appended to chain [7efe3044dcb0] main filter debug: using video converter module "chain" [7efe306b3d00] main filter debug: Filter 'chain' (0x7efe3044dcb0) appended to chain [7efe300d0700] main filter debug: looking for video converter module matching "any": 23 candidates [swscaler @ 0x7efe309eac80] Forcing full internal H chroma due to input having non subsampled chroma [7efe300d0700] swscale filter debug: 540x360 (544x368) chroma: RV24 -> 540x360 (540x360) chroma: RV24 with scaling using Bicubic (good quality) [7efe300d0700] main filter debug: using video converter module "swscale" [7efe306b3d00] main filter debug: Filter 'Swscale' (0x7efe300d0700) appended to chain [7efe306b3d00] main filter debug: using video converter module "chain" [7efe3010] main encoder debug: removing module "png" [7efe306b3d00] main filter debug: removing module "chain" [7efe3044dcb0] main filter debug: removing module "chain" [7efe300d5d30] main filter debug: removing module "vaapi_filters" double free or corruption (!prev) ``` The bug didn't occur on 640x360 and 1280x720 videos. The similar bug have been reported on Ubuntu ([2]) with older VLC version. [1]: https://www.youtube.com/watch?v=eoocJ3euHy8 [2]: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1894968 -- System Information: Debian Release: 11.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.19.12-local (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vlc depends on: ii vlc-bin 3.0.17.4-0+deb11u1 ii vlc-plugin-base 3.0.17.4-0+deb11u1 ii vlc-plugin-qt3.0.17.4-0+deb11u1 ii vlc-plugin-video-output 3.0.17.4-0+deb11u1 Versions of packages vlc recommends: ii vlc-l10n 3.0.17.4-0+deb11u1 ii vlc-plugin-access-extra3.0.17.4-0+deb11u1 ii vlc-plug
Bug#931400: RFP: pcynlitx -- Innovative IDE for Multithreading
Package: wnpp Severity: wishlist Package name: pcynlitx Version: 0.0~git20190606 Upstream Author: Erkam Murat Bozkurt License: GPLv3 URL: http://www.pcynlitx.tech Description: Innovative IDE for Multithreading From project's homepage: Pcynlitx is an outcome of a scientific research study that is carried out by Erkam Murat Bozkurt who is a research engineer in Istanbul / Turkey. Pcynlitx platform has been developed based on a new idea. This idea is to develop a software that can write codes in a collaboration with its user. By this way, Pcynlitx acts as a separate intelligent actor simplifying the multi-threaded software development process. Basically, pcynlitx is a code generator which can be programmed by the programmer. More specifically, It receives the requirements of the software to be developed from the programmer by means of a descriptor file and then, writes a C++ class library ( a thread library ). Why Pcynlitx? - More control on threads : Give a certain number to each thread and control it with that numbers. - Autonom thread management : on each operation, thread management tools record the numbers of the threads and provide the execution of the threads according to programmer’s directives. - Easy to use : there is no need to learn any new coding style. It is only C++. - Coding Simplicity : Pcynlitx makes abstraction to C++ threads and many operation are performed on the inside of the library constructed by - Strong Documentation : You can find out many tutorial and technical documents on the web site - Deterministic Multi Threading : Pcynlitx provides input-output determinisim Features: - Code editing : You can use pcynlitx as a code editor. However, it is more than a code editor. Pcynlitx interracts with its user and it is a part of software development process. - The interraction with the user : You can enter your preferences to the pcynlitx by means of its menus. In each step of software development process, pcynlitx asists the programmers - Directory Tree View : You can search over the directories by means of the directory tree view option. - Project management : You can build and manage your multi-thread application directly with pcynlitx. - Special Library Construction : You can build your multi-threading library according to your reqirements - Compiler : Pcynlitx uses gcc compiler as its compiler tool chain and wxWidgets as its graphical user interface toolkit. - License : GNU GPLv3 Copyright Notice: - An application to the US Copyright office has been performed for the modified version of the source code of the project - A certificate of registration has been received from US Copyright office for the source code of the project - A certificate of registration has been received from the copyright office of Turkey
