You are not logged in.
Pages: 1
Thank you, found it!
In which package would I find the deepsea based desktop background image? I'm using Gnome 3 on arm64, and it does not seem to be installed right now... a download link for the .jpg file itself would also help.
Thanks,
Alex
Update... this error, which was independent from the codec used, is gone with the upgrade to kernel 5.10.110... the version which showed the error was 5.10.90.
I´m not sure if the underlying problem is caused by the kernel, raspberry video drivers, or the gnome-delivered totem player... playing a video works well until totem is closed or asked to load another video file on the fly... any ideas?
[19054.870510] ------------[ cut here ]------------
[19054.870569] WARNING: CPU: 3 PID: 8638 at drivers/media/common/videobuf2/videobuf2-core.c:1956 __vb2_queue_cancel+0x1b8/0x220 [videobuf2_common]
[19054.870575] Modules linked in: rfcomm fuse md4 md5 nls_utf8 cifs libarc4 cmac algif_hash aes_arm64 algif_skcipher af_alg bnep lz4 lz4_compress zram zsmalloc hci_uart btbcm bluetooth ecdh_generic ecc brcmfmac brcmutil vc4 bcm2835_v4l2(C) bcm2835_codec(C) bcm2835_isp(C) cec cfg80211 v3d bcm2835_mmal_vchiq(C) drm_kms_helper v4l2_mem2mem videobuf2_vmalloc rfkill videobuf2_dma_contig gpu_sched videobuf2_memops videobuf2_v4l2 snd_soc_core videobuf2_common drm rpivid_mem snd_compress videodev snd_bcm2835(C) snd_pcm_dmaengine drm_panel_orientation_quirks mc snd_pcm raspberrypi_hwmon vc_sm_cma(C) snd_timer syscopyarea sysfillrect sysimgblt snd fb_sys_fops backlight nvmem_rmem uio_pdrv_genirq uio sg
[19054.870759] CPU: 3 PID: 8638 Comm: totem Tainted: G C 5.10.90-v8 #1
[19054.870763] Hardware name: Raspberry Pi 4 Model B Rev 1.2 (DT)
[19054.870771] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--)
[19054.870780] pc : __vb2_queue_cancel+0x1b8/0x220 [videobuf2_common]
[19054.870790] lr : __vb2_queue_cancel+0x3c/0x220 [videobuf2_common]
[19054.870793] sp : ffffffc01cd63b10
[19054.870797] x29: ffffffc01cd63b10 x28: ffffff806471a000
[19054.870805] x27: 0000000040045613 x26: ffffffc00914faa8
[19054.870814] x25: 0000000000000000 x24: ffffffc01cd63d38
[19054.870821] x23: ffffff8043f7ee30 x22: ffffff8017b38000
[19054.870829] x21: ffffff808e178028 x20: ffffff808e178028
[19054.870836] x19: ffffff808e178028 x18: 0000000000000000
[19054.870843] x17: 0000000000000003 x16: 0000008331158038
[19054.870850] x15: 0000000000000004 x14: ffffff8041dc0030
[19054.870859] x13: 0000000000000000 x12: ffffff8005c13288
[19054.870866] x11: ffffff8005c13230 x10: ffffff8005c13232
[19054.870873] x9 : ffffffc008c6b7d0 x8 : ffffff8005c13258
[19054.870881] x7 : 0000000000000001 x6 : ffffff8005c13458
[19054.870887] x5 : ffffff8043f7f01c x4 : 0000000000000000
[19054.870895] x3 : ffffff8041dc0008 x2 : 0000000000000000
[19054.870902] x1 : 00000000000055ac x0 : 0000000000000003
[19054.870912] Call trace:
[19054.870924] __vb2_queue_cancel+0x1b8/0x220 [videobuf2_common]
[19054.870933] vb2_core_streamoff+0x30/0xd0 [videobuf2_common]
[19054.870951] vb2_streamoff+0x28/0x80 [videobuf2_v4l2]
[19054.870972] v4l2_m2m_streamoff+0x48/0x134 [v4l2_mem2mem]
[19054.870980] v4l2_m2m_ioctl_streamoff+0x24/0x30 [v4l2_mem2mem]
[19054.871047] v4l_streamoff+0x30/0x40 [videodev]
[19054.871068] __video_do_ioctl+0x190/0x3f0 [videodev]
[19054.871088] video_usercopy+0x1b0/0x580 [videodev]
[19054.871109] video_ioctl2+0x24/0x50 [videodev]
[19054.871129] v4l2_ioctl+0x4c/0x70 [videodev]
[19054.871154] __arm64_sys_ioctl+0xb4/0x100
[19054.871166] el0_svc_common.constprop.0+0x84/0x200
[19054.871171] do_el0_svc+0x30/0xa0
[19054.871182] el0_svc+0x20/0x30
[19054.871188] el0_sync_handler+0x1a4/0x1b0
[19054.871195] el0_sync+0x180/0x1c0
[19054.871200] ---[ end trace 27a7751cc6bf050c ]---
[19054.871215] videobuf2_common: driver bug: stop_streaming operation is leaving buf 00000000fd2f1de2 in active state
[19054.871228] videobuf2_common: driver bug: stop_streaming operation is leaving buf 00000000d87fd423 in active state
[19054.871236] videobuf2_common: driver bug: stop_streaming operation is leaving buf 00000000f60efcc5 in active state
I´m running the official Chimaera releases (dated Oct 19th 2021) on two systems for a few weeks now, one is a Pi3 application and database server (volkszaehler.org software, based mainly on PHP and MariaDB), the other one is a Pi 4 and my one and only desktop.
Those Devuan builds are very well crafted and (in my case) have replaced Raspbian (32bit Buster and 64bit Beta). The 64bit Raspbian does (as per today) not have a working hardware accelerated X server, hardware accelerated web browser (I am using chromium), and also no hardware video decoding (for almost two years)... Devuan has all of it... I am impressed.
If testing or some other form of contribution or feedback is needed, let me know.
-Alex
Well, regarding that wish list...
Donate an ARM development board (50$-100$) (contact parazyd parazyd@dyne.org / #devuan-arm)
Donate PowerPC/Sparc hardware for build/development (contact devs on #devuan-dev)
... as per the ARM board, there was a wire transfer (€50) recently, dedicated to the ARM team...
... regarding to the Sparc hardware, I have a spare Sun Blade 150 with a 650-MHz UltraSPARC IIi and 2GB of memory, currently located in Germany ... if there's interest, let me know.
Package: system-config-printer-udev
Provides the udev config file 70-printers.rules, which stops or resumes a matching cups device if a printer is added to or removed from USB.
Said rules file references a systemd service for usb device adds, and uses the program udev-configure-printer (also part of the pkg) for removals.
It is very easy to change /usr/lib/udev/rules.d/70-printer.rules so an added USB printer is activated when not using systemd - udev-configure-printer can handle this as well.
-ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", ENV{ID_USB_INTERFACES}!="*:070104:*", TAG+="systemd", ENV{SYSTEMD_WANTS}="configure-printer@usb-$env{BUSNUM}-$env{DEVNUM}.service"
+ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", ENV{ID_USB_INTERFACES}!="*:070104:*", RUN+="udev-configure-printer add %p"
However it takes some time to figure this out... so the question is if there's some easy way to change this in the package, either by repackaging or by adopting the file conditionally in a post install script and feeding the complete package back to the Debian upstream...?
PS - system-config-printer-udev comes with system-config-printer, which itself came (in my case) with gnome-core.
Pages: 1