Description of problem: I have tried printing to boomaga from several programs, similar lines in journal: maj 31 11:56:47 svarten.tribun cupsd[4170]: Boomaga morgan 144 [31/May/2023:11:56:47 +0200] total 0 1 localhost Canon LBP7750cdn p_06.html.pdf A4 one-sided maj 31 11:58:12 svarten.tribun cupsd[4170]: REQUEST localhost - - "POST /printers/Boomaga HTTP/1.1" 200 589 Create-Job successful-ok maj 31 11:58:12 svarten.tribun cupsd[4170]: REQUEST localhost - - "POST /printers/Boomaga HTTP/1.1" 200 2916818 Send-Document successful-ok maj 31 11:58:12 svarten.tribun cupsd[4170]: [Job 145] [Boomaga GUI] WARNING: Can\'t read DBUS session directory /var/spool/cups/tmp/.dbus/session-bus maj 31 11:58:12 svarten.tribun cupsd[4170]: [Job 145] [Boomaga GUI] ERROR: Can\'t start boomaga gui. And this happens also with boomaga already launched cleanly from konsole. Version-Release number of selected component (if applicable): I am pretty sure this last worked before i updated amongst other things cups 2023-05-25 boomaga have not been updated. I see no problems printing to my real printer nor pdf. Note this is not the same symptoms as in Bug 31859 - Boomaga sometimes crash when printing to it from some programs, i.e Okular Maybe I should try downgrading cups and related packages. The usual problem running cauldron: getting the previous versions... Beta 2 install iso ? Thierry: CUPS maintainer
CC: (none) => thierry.vignaud
Only cups package to have been updated since i think boomaga worked ok is lib64cups-filters1-1.28.16-6.mga9.x86_64.rpm That does not sound like a possible culprit to me.
On my Cauldron system, the only relevant packages updated recently are: cups-filters-1.28.16-6.mga9.x86_64 Dydd Sul 28 mis Mai 2023 21:32:49 lib64cups-filters1-1.28.16-6.mga9.x86_64 Dydd Sul 28 mis Mai 2023 21:32:47 but note: boomaga-3.0.0-6.mga9.x86_64 Dydd Sul 21 mis Mai 2023 16:21:36 Trying to print to Boomaga, nothing happens. Journal: Mai 31 20:39:56 cupsd[1821]: REQUEST localhost - - "POST /printers/Boomaga HTTP/1.1" 200 36077 Print-Job successful-ok Mai 31 20:39:56 cupsd[1821]: [Job 47] [Boomaga GUI] WARNING: Can\'t read DBUS session directory /var/spool/cups/tmp/.dbus/session-bus Mai 31 20:39:56 dbus-daemon[2493]: [session uid=1001 pid=2493] Activating service name='org.boomaga' requested by ':1.120' (uid=1001 pid=7242 comm="boomaga --started-from-cups /var/cache/boomaga/lew") Mai 31 20:39:56 dbus-daemon[2493]: [session uid=1001 pid=2493] Successfully activated service 'org.boomaga' Mai 31 20:39:57 cupsd[1821]: Boomaga lewis 47 [31/May/2023:20:39:57 +0200] total 0 - localhost bugsquad.txt - - Mai 31 20:39:57 org.boomaga[7245]: double free or corruption (fasttop) So this looks down to Boomaga, which was updated Tue May 2 by DavidG. So assigning to you! Un-CC'ing tv.
CC: thierry.vignaud => (none)Source RPM: (none) => boomaga-3.0.0-6.mga9.src.rpm
Assignee: bugsquad => geiger.david68210
Thank you Lewis. That boomaga was installed here already at fresh install beta2 + updates during install. Probably I remembered wrong about it ever working on *this* system. But it is strange difference you (but not me) get in your log "Successfully activated service 'org.boomaga'", (and later it crash)
I think this issue should be reported upstream, I'm not the boomaga developer so I can't do more for this.
Searching internet, I found similar reports. Upstream seem to not have time anymore, since years :( https://github.com/Boomaga/boomaga/issues/117 at a straight question, https://github.com/Boomaga/boomaga/issues/123 two weeks ago. Darn, this "intermediate printer" is so useful. Good thing is that developer at least answers :) So IF someone wants to step up and take it on... lets hope! Boomaga is still working in updated Mageia 8. Tedious workaround: print to pdf, open in a pdf page shuffler (we have some packaged), then print.
Keywords: (none) => FOR_ERRATA9, UPSTREAMSeverity: normal => majorURL: (none) => https://github.com/Boomaga/boomaga
https://wiki.mageia.org/en/Mageia_9_Errata#Boomaga_virtual_printer
Keywords: FOR_ERRATA9 => IN_ERRATA9
Now I get really confused: It works perfectly on my laptop. That install have never had printing installed. Originally installed from mga9 beta 1 classic i think, then updated, used sparsely. Now I: 1) Installed boomaga package 2) opened MCC > Hardware > Printer -> it installed packages, then boomaga icon showed up used that icon to print test page: boomaga popped up and showed it! 3) rebooted 4) started firefox, which i let open a pdf, print to boomaga: perfect! Go figure... Edited Errata.
After reboot of the problematic system in Comment 0, it works again. (Print from Kolourpaint -> boomaga popped up showing the picture) Maybe some state of DBUS, CUPS, whatever needed to be reset? Edited Errata to suggest reboot. @Lewis: does rebooting help on your system?
Boomaga had been working perfectly for me several months. Then it suddenly stopped a couple or so months ago. It works to launch it from command line, and let it to open a file in the autosave folder i have configured. I can also alunch it with that file directly by in Dolphin double click i.e /home/morgan/Ut/Boomaga-autosave/[2024.12.20-00:06:49]-Betalningsavisering.pdf.boo But when trying to print to boomaga, the GUI do not open. In journal i see i.e: mar 14 17:20:58 svarten.tribun cupsd[1853]: REQUEST localhost - - "POST /printers/Boomaga HTTP/1.1" 200 636 Create-Job successful-ok mar 14 17:20:58 svarten.tribun cupsd[1853]: REQUEST localhost - - "POST /printers/Boomaga HTTP/1.1" 200 3714800 Send-Document successful-ok mar 14 17:20:58 svarten.tribun cupsd[1853]: [Job 1892] [Boomaga GUI] WARNING: Can\'t read DBUS session directory /var/spool/cups/tmp/.dbus/session-bus mar 14 17:20:58 svarten.tribun cupsd[1853]: [Job 1892] [Boomaga GUI] ERROR: Can\'t start boomaga gui. mar 14 17:20:58 svarten.tribun cupsd[1853]: Boomaga morgan 1892 [14/Mar/2025:17:20:58 +0100] total 0 1 localhost P:\ACADWIN\Direktlev\els_250016-1\sid01.dwg Model (1) A4 one-sided Also it do not work to have boomaga open and then print. Tested: Per https://github.com/Boomaga/boomaga/issues/131, I tried adding myself to lp group and reboot, but no change. I tried to downgrade ghostscript to 10.03.1-1.mga9 because some upstreanissue said problem appeared in 10.04 for them Then, i also tried downgrading both ghostscript and poppler to mga9 release versions: $ sudo urpmi --media "Core Release" --downgrade poppler lib64poppler-qt5_1 lib64poppler-glib8 lib64poppler-gir0.18 lib64poppler-cpp0 lib64poppler126 ghostscript ghostscript-common ghostscript-module-X Rebooting each time of course. No improvement. I also tried deleting ~/.config/boomaga/boomaga.conf (it gets recreated automatically by boomaga) I also tried using MCC to remove boomaga and create it again. The test page works - probably because it is executed as root? Tried again, then i got segfault at 0 ip 00007f1391ba0e36 sp 00007ffcf29d5128 error 4 in libc.so.6 Sigh. How does it work for you, other users?
Fedora is using a more recent commit but is from 3 years ago :S BTW there was a suggestion to add other pdf printer that works for me but I'm unable to find :S
It not was a comment about boomaga https://bugs.mageia.org/show_bug.cgi?id=32198#c16
I build a package based in last commit, I send the url to Morgan in the qa list, if he can confirm that helps, I'll send the changes
CC: (none) => geiger.david68210Assignee: geiger.david68210 => j.alberto.vc
Tested boomaga3.3.0 from katnanek, printing a booklet with HP Eny 6022 duplexer. Worked perfectly. I had no problems with the current 3.0.0 in M9 repos.
CC: (none) => herman.viaene
Thank you all for checking and working on this. Mistery thickens as I see both here and in QA list that it works for others, and it works on my wifeś laptop too, which also run mga9-64 Plasma... --- I forgot in Comment 9 to downgrade lib64gs10 - did that now and rebooted, no change. --- I will try the build by katnatek.
I installed it from the Mageia 9 repos. After configuring for my color Laserjet M254dw, telling it I have a duplexer, I printed 16 pages of a manual in booklet form, 8 pages to a side. It worked perfectly. The individual pages were too small to read, but that was to be expected, given the task I set it to do. One thing, though - I had added myself to the lp group ages ago, to facilitate the ability of canceling a print job without being root.
CC: (none) => andrewsfarm
A couple observations before I try katnatek's version: On the laptop here where it works user is not in lp group. She is only in her own group. To make sure i have our current official versions, performed dnf offline-distrosync download --disablerepo=\*testing\* --allowerasing And the subsequent dnf offline-distrosync reboot It basically only removed what I had from testing: LibreOffice and Chromium, and updated ghostscript and poppler which I downgarded before. Before that sync, I had removed boomaga printer, and then the package boomaga, and then installed it afterwards. Still same problem. But something seem fishy: A few minutes after boomaga test, I in journal got a crash logged: mar 16 21:33:10 svarten.tribun DiscoverNotifier[71990]: packagekitqt.transaction: Unknown Transaction property: "Sender" QVariant(QString, ":1.143") mar 16 21:33:10 svarten.tribun systemd[1]: Starting systemd-localed.service... mar 16 21:33:10 svarten.tribun systemd[1]: Started systemd-localed.service. mar 16 21:33:10 svarten.tribun systemd-coredump[71997]: [🡕] Process 45047 (DiscoverNotifie) of user 10702 dumped core. Stack trace of thread 45047: #0 0x00007f608dab34bc __pthread_kill_implementation (libc.so.6 + 0x854bc) #1 0x00007f608da64932 raise (libc.so.6 + 0x36932) #2 0x00007f608f4ea6f0 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x56f0) #3 0x00007f608da649e0 __restore_rt (libc.so.6 + 0x369e0) #4 0x00007f6065fb2b84 _ZNK10PackageKit11Transaction4roleEv (libpackagekitqt5.so.1 + 0x19b84) #5 0x00007f607bff7269 _ZN18PackageKitNotifier15refreshDatabaseEv (DiscoverPackageKitNotifier.so + 0x8269) #6 0x00007f608ded79c5 _ZN16QSingleShotTimer10timerEventEP11QTimerEvent (libQt5Core.so.5 + 0x2d79c5) #7 0x00007f608dec8b5d _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c8b5d) #8 0x00007f608eb6240e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16240e) #9 0x00007f608de9e888 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29e888) #10 0x00007f608def2701 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2f2701) #11 0x00007f608def2ed4 _ZL19timerSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5 + 0x2f2ed4) #12 0x00007f608c447689 g_main_context_dispatch (libglib-2.0.so.0 + 0x58689) #13 0x00007f608c447a18 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58a18) #14 0x00007f608c447a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c) #15 0x00007f608def31f6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f31f6) #16 0x00007f608de9d46b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29d46b) #17 0x00007f608dea4fe6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2a4fe6) #18 0x00000000004071f2 main (DiscoverNotifier + 0x71f2) #19 0x00007f608da51737 __libc_start_call_main (libc.so.6 + 0x23737) #20 0x00007f608da517f5 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x237f5) #21 0x0000000000407341 _start (DiscoverNotifier + 0x7341) Stack trace of thread 45080: #0 0x00007f608daae846 __futex_abstimed_wait_common (libc.so.6 + 0x80846) #1 0x00007f608dab0eb8 pthread_cond_wait@@GLIBC_2.3.2 (libc.so.6 + 0x82eb8) #2 0x00007f6079b3b9a9 cnd_wait (libgallium-24.2.8.so + 0x13b9a9) #3 0x00007f6079b1be7b util_queue_thread_func (libgallium-24.2.8.so + 0x11be7b) #4 0x00007f6079b3b8e7 impl_thrd_routine (libgallium-24.2.8.so + 0x13b8e7) #5 0x00007f608dab19ca start_thread (libc.so.6 + 0x839ca) #6 0x00007f608db2d61c __clone3 (libc.so.6 + 0xff61c) Plus about then more like the last section, all concering libc.so.6 I can not tell what that is about. Desktop is operating normally... ...Anyway... =========== Using MCC, I again removed Boomaga printer, then urpme boomaga, and installed the new candidate: $ sudo urpmi boomaga-3.3.0-1.20220220git7f7ad47.mga9.x86_64.rpm varning: boomaga-3.3.0-1.20220220git7f7ad47.mga9.x86_64.rpm: Huvud V4 RSA/SHA256 Signature, nyckel-ID a1281639: NOKEY Följande paket har felaktig signatur: boomaga-3.3.0-1.20220220git7f7ad47.mga9.x86_64.rpm: Ogiltig signatur (NOT OK (no key): boomaga-3.3.0-1.20220220git7f7ad47.mga9.x86_64.rpm: Huvud V4 RSA/SHA256 Signature, nyckel-ID a1281639: NOKEY) Vill du fortsätta installationen? (j/N) j installerar boomaga-3.3.0-1.20220220git7f7ad47.mga9.x86_64.rpm Förbereder... ########################################################################################################################################################################################### 1/1: boomaga ########################################################################################################################################################################################### lpadmin: Printer drivers are deprecated and will stop working in a future version of CUPS. Printer Boomaga has been installed successfully. Tried printing a pdf from Thunderbird: fail. In journal same as usual...: mar 16 21:54:29 svarten.tribun cupsd[1877]: REQUEST localhost - - "POST /printers/Boomaga HTTP/1.1" 200 26818 Print-Job successful-ok mar 16 21:54:29 svarten.tribun cupsd[1877]: [Job 1909] [Boomaga GUI] WARNING: Can\'t read DBUS session directory /var/spool/cups/tmp/.dbus/session-bus mar 16 21:54:29 svarten.tribun cupsd[1877]: [Job 1909] [Boomaga GUI] ERROR: Can\'t start boomaga gui. mar 16 21:54:29 svarten.tribun cupsd[1877]: Boomaga morgan 1909 [16/Mar/2025:21:54:29 +0100] total 0 - localhost Händelsedetaljer 2630615066.pdf - - Hm... Could this be about ownership / access rights of DBUS session directory /var/spool/cups/tmp/.dbus/session-bus ? Still weird that this my workstation have this problem but no one else reported it lately here on Mageia.
Just to try something i rebooted. Not better. Like previous version i can launch boomaga from command line. But a regression is that it now crashed when i tried to open a file from cache folder, populated by previous version from when it worked. mar 16 22:11:17 svarten.tribun systemd-coredump[23654]: [🡕] Process 16960 (boomaga) of user 10702 dumped core. Stack trace of thread 23645: #0 0x00007f4a4ad76319 cmsFreeToneCurve (liblcms2.so.2 + 0x18319) #1 0x00007f4a4ad7fd78 cmsCloseProfile (liblcms2.so.2 + 0x21d78) #2 0x00007f4a4c31f747 _ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv (libpoppler.so.126 + 0x11f747) #3 0x00007f4a4c38519e _ZN8GfxStateC1EddPK12PDFRectangleib (libpoppler.so.126 + 0x18519e) #4 0x00007f4a4c35f2d1 _ZN3GfxC2EP6PDFDocP9OutputDeviP4DictddPK12PDFRectangleS8_iPFbPvES9_P4XRef (libpoppler.so.126 + 0x15f2d1) #5 0x00007f4a4c3bf75f _ZN4Page9createGfxEP9OutputDevddibbiiiibPFbPvES2_P4XRef (libpoppler.so.126 + 0x1bf75f) #6 0x00007f4a4c3c09de _ZN4Page12displaySliceEP9OutputDevddibbiiiibPFbPvES2_PFbP5AnnotS2_ES2_b (libpoppler.so.126 + 0x1c09de) #7 0x00007f4a4e4acbf2 _ZNK7poppler13page_renderer11render_pageEPKNS_4pageEddiiiiNS_13rotation_enumE (libpoppler-cpp.so.0 + 0x13bf2) #8 0x0000000000449dd0 _Z13doRenderSheetPN7poppler8documentEid (boomaga + 0x49dd0) #9 0x0000000000449faf _ZN12RenderWorker11renderSheetEi (boomaga + 0x49faf) #10 0x000000000044413c _ZN12RenderWorker18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv (boomaga + 0x4413c) #11 0x00007f4a4d0c8d40 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2c8d40) #12 0x00007f4a4dd6240e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x16240e) #13 0x00007f4a4d09e888 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29e888) #14 0x00007f4a4d0a15b9 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2a15b9) #15 0x00007f4a4d0f3b03 _ZL23postEventSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5 + 0x2f3b03) #16 0x00007f4a4ba47689 g_main_context_dispatch (libglib-2.0.so.0 + 0x58689) #17 0x00007f4a4ba47a18 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x58a18) #18 0x00007f4a4ba47a9c g_main_context_iteration (libglib-2.0.so.0 + 0x58a9c) #19 0x00007f4a4d0f31f6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2f31f6) #20 0x00007f4a4d09d46b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29d46b) #21 0x00007f4a4ceca297 _ZN7QThread4execEv (libQt5Core.so.5 + 0xca297) #22 0x00007f4a4cecb389 _ZN14QThreadPrivate5startEPv (libQt5Core.so.5 + 0xcb389) #23 0x00007f4a4ccb19ca start_thread (libc.so.6 + 0x839ca) #24 0x00007f4a4cd2d61c __clone3 (libc.so.6 + 0xff61c) Just my system?
[morgan@svarten ~]$ inxi -SMCG System: Host: svarten.tribun Kernel: 6.6.79-desktop-1.mga9 arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9 Machine: Type: Desktop Mobo: ASRock model: P55 Pro serial: <superuser required> BIOS: American Megatrends v: P2.60 date: 08/20/2010 CPU: Info: quad core model: Intel Core i7 870 bits: 64 type: MT MCP cache: L2: 1024 KiB Speed (MHz): avg: 1205 min/max: 1200/2934 cores: 1: 1205 2: 1205 3: 1205 4: 1205 5: 1205 6: 1205 7: 1205 8: 1205 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] driver: amdgpu v: kernel Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: amdgpu,v4l dri: radeonsi gpu: amdgpu resolution: 3840x2160~60Hz API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.6 vendor: amd mesa v: 24.2.8 renderer: AMD Radeon RX 6400 (radeonsi navi24 LLVM 15.0.6 DRM 3.54 6.6.79-desktop-1.mga9)
OK you are not alone, I try this and see [Job 1] [Boomaga GUI] WARNING: Can\'t read DBUS session directory /var/spool/cups/tmp/.d> inxi -SMCG System: Host: jgrey.phoenix Kernel: 6.6.79-1.mga9 arch: x86_64 bits: 64 Desktop: LXQt v: 1.4.0 Distro: Mageia 9 Machine: Type: Desktop Mobo: Intel model: DH55HC v: AAE70933-505 serial: <superuser required> BIOS: Intel v: TCIBX10H.86A.0037.2010.0614.1712 date: 06/14/2010 CPU: Info: dual core model: Intel Core i5 650 bits: 64 type: MT MCP cache: L2: 512 KiB Speed (MHz): avg: 3193 min/max: 1197/3193 cores: 1: 3193 2: 3193 3: 3193 4: 3193 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] driver: radeon v: kernel Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: radeon resolution: 1360x768~60Hz API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.5 vendor: amd mesa v: 24.2.8 renderer: VERDE (radeonsi LLVM 15.0.6 DRM 2.50 6.6.79-1.mga9) API: Vulkan v: 1.3.231 drivers: llvmpipe surfaces: xcb,xlib
I not even see the .dbus/session-bus in /var/spool/cups/tmp ls -la /var/spool/cups/tmp total 8 drwxrwx--T 2 root lp 4096 oct 2 08:33 ./ drwx--x--- 3 root lp 4096 mar 16 19:04 ../ groups katnatek cdrom usb cdwriter audio video mock apache qemu qarepo usbmux render kvm ls -laR /var/spool/cups /var/spool/cups: total 148 drwx--x--- 3 root lp 4096 mar 16 19:04 ./ drwxr-xr-x 10 root root 4096 jul 13 2024 ../ -rw------- 1 root lp 1130 mar 16 19:04 c00001 -rw-r----- 1 root lp 133047 mar 16 19:04 d00001-001 drwxrwx--T 2 root lp 4096 oct 2 08:33 tmp/ ls -la /var/spool/ total 40 drwxr-xr-x 10 root root 4096 jul 13 2024 ./ drwxr-xr-x 18 root root 4096 abr 18 2024 ../ drwxr-xr-x 2 root root 4096 dic 17 2023 anacron/ drwx------ 2 root root 4096 feb 11 2023 cron/ drwx--x--- 3 root lp 4096 mar 16 19:04 cups/ drwxr-xr-x 2 root daemon 4096 sep 6 2022 lpd/ drwxrwxr-x 2 root mail 4096 jul 5 2024 mail/ drwxr-xr-x 2 root root 4096 mar 16 18:51 plymouth/ drwxr-xr-x 5 root root 4096 jun 4 2024 postfix/ drwxr-xr-x 2 root root 4096 nov 30 2023 repackage/ so I add to lp group, test will come
And now see the comment#17 things :S
I reset to bugsquad, as you and I get the Murphy's lottery Don't now what more to try I even try a pending Pull request without success , looks like something is rotten related to dbus manage
Assignee: j.alberto.vc => bugsquadCC: (none) => j.alberto.vc
This bug was originally filed as a Cauldron bug, but that was before Mageia 9 was released. Switching it to Mageia 9. Any resolution should be passed along to Cauldron, but this is a Mageia 9 bug. For what it's worth, here is the hardware I used where the current Mageia 9 Boomaga is working: $ inxi -SMCGD System: Host: localhost Kernel: 6.6.79-desktop-1.mga9 arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9 Machine: Type: Desktop Mobo: ASUSTeK model: PRIME Q270M-C v: Rev X.0x serial: <superuser required> UEFI: American Megatrends v: 2201 date: 12/21/2023 CPU: Info: quad core model: Intel Core i5-7500 bits: 64 type: MCP cache: L2: 1024 KiB Speed (MHz): avg: 800 min/max: 800/3800 cores: 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: NVIDIA GM107GL [Quadro K620] driver: nvidia v: 550.144.03 Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: nvidia,v4l gpu: nvidia,nvidia-nvswitch resolution: 1920x1080~60Hz API: EGL v: 1.5 drivers: nvidia,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 4.6.0 vendor: nvidia v: 550.144.03 renderer: Quadro K620/PCIe/SSE2 API: Vulkan v: 1.3.231 drivers: nvidia,llvmpipe surfaces: xcb,xlib Drives: Local Storage: total: 1.84 TiB used: 579.79 GiB (30.8%) ID-1: /dev/nvme0n1 vendor: TeamGroup model: TM8FP6001T size: 953.87 GiB ID-2: /dev/nvme1n1 vendor: Crucial model: CT1000P3PSSD8 size: 931.51 GiB Printer is an HP Color Laserjet Pro M254dw, used as a network printer, connected to my router via Ethernet cable. There is also an HP Envy Photo 7858 all-in-one connected via wifi, and a Deskjet 5650 connected to the above hardware through usb, but I didn't try those.
Version: Cauldron => 9
I wonder if "Murphy" may be a threading issue? Maybe try to run the system on one core only. I guess there are kernel boot line options to achieve that.
(In reply to Morgan Leijström from comment #24) > I wonder if "Murphy" may be a threading issue? > Maybe try to run the system on one core only. > I guess there are kernel boot line options to achieve that. I'm going to say age, 2010 is the common thing I see between our systems, but I did try the solution for guayadeque and not produce difference.
So a compiler/CPU/microcode type issue? Would be interesting to switch mainboard and CPU, or move drives to another machine so see if the exact same issue repeats there. I do not want to try that myself - this system with current boomaga issue is my workstation, and I do not have a newer hardware compatible machine. I may try kernel command line parameter maxcpus=1
I tried easier method: temporarily closed all "CPU" except one (this is a 4 core 8 thread i7) [root@svarten ~]# echo 0 > /sys/devices/system/cpu/cpu1/online [root@svarten ~]# echo 0 > /sys/devices/system/cpu/cpu2/online [root@svarten ~]# echo 0 > /sys/devices/system/cpu/cpu3/online [root@svarten ~]# echo 0 > /sys/devices/system/cpu/cpu4/online [root@svarten ~]# echo 0 > /sys/devices/system/cpu/cpu5/online [root@svarten ~]# echo 0 > /sys/devices/system/cpu/cpu6/online [root@svarten ~]# echo 0 > /sys/devices/system/cpu/cpu7/online Interesting to watch gkrellm, originally showing a graph per "CPU", while doing this. Reminds of the movie where astronaout pulls modules from HAL9000... Still same problem trying to boomaga: "[Boomaga GUI] ERROR: Can\'t start boomaga gui." What next... remove microcode package, use release version kernel?
My Probook is of the same 2010 vintage,but of course still different hardware: $ inxi -SMCGD System: Host: localhost Kernel: 6.6.79-desktop-1.mga9 arch: x86_64 bits: 64 Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9 Machine: Type: Laptop System: Hewlett-Packard product: HP ProBook 6550b v: N/A serial: <superuser required> Mobo: Hewlett-Packard model: 146D v: KBC Version 73.17 serial: <superuser required> BIOS: Hewlett-Packard v: 68CDE Ver. F.60 date: 11/10/2015 CPU: Info: dual core model: Intel Core i3 M 350 bits: 64 type: MT MCP cache: L2: 512 KiB Speed (MHz): avg: 933 min/max: 933/2266 cores: 1: 933 2: 933 3: 933 4: 933 Graphics: Device-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X: loaded: intel,v4l dri: i965 gpu: i915 resolution: 1366x768~60Hz API: EGL v: 1.5 drivers: crocus,swrast platforms: gbm,x11,surfaceless,device API: OpenGL v: 2.1 vendor: intel mesa v: 24.2.8 renderer: Mesa Intel HD Graphics (ILK) API: Vulkan v: 1.3.231 drivers: llvmpipe surfaces: xcb,xlib Drives: Local Storage: total: 942.7 GiB used: 217.62 GiB (23.1%) ID-1: /dev/sda vendor: TeamGroup model: T253X2512G size: 476.94 GiB ID-2: /dev/sdb vendor: Hitachi model: HTS727550A9E364 size: 465.76 GiB (sda is an SSD, containing /, swap, and /home partitions. sdb is a rust drive, containing most of the data for Downloads, Documents, Pictures, Videos, and the like, with links to those in /home.) I installed the repo version of Boomaga, configured it to use the Laserjet. Then I closed it, and opened a camera manual in Okular, telling it to use Boomaga to print 16 pages, four pages to a sheet. It worked perfectly.
Grasping at straws... My user is a member of these groups: his lp qarepo vboxusers That's it. Is there a group that Morgan and katnatek have in common, but not with me?
Not working (also not working before adding lp): kamo lp wheel users gamemode boinc vboxusers Working at my wifeś laptop: kamo - Yes only that one "kamo", which is our common group.
(In reply to Thomas Andrews from comment #28) > My Probook is of the same 2010 vintage,but of course still different > hardware: > > $ inxi -SMCGD > System: > Host: localhost Kernel: 6.6.79-desktop-1.mga9 arch: x86_64 bits: 64 > Desktop: KDE Plasma v: 5.27.10 Distro: Mageia 9 > Machine: > Type: Laptop System: Hewlett-Packard product: HP ProBook 6550b v: N/A > serial: <superuser required> > Mobo: Hewlett-Packard model: 146D v: KBC Version 73.17 > serial: <superuser required> BIOS: Hewlett-Packard v: 68CDE Ver. F.60 > date: 11/10/2015 2015 not 2010 and the other working in comment#23 is from 2023
I bought the Probook in 2016, and it was definitely more than a year old. The BIOS is from 2015, the latest available, but the hardware itself is from 2010. Decoding the serial number to be precise, November 2010. That fits with it using a first-generation i3, and having a Legacy BIOS rather than UEFI. The BIOS does have a secure boot option, but it's labeled as "experimental" and disabled by default. Conversely, my Pavilion 15, which IS from 2015, has a fully operational UEFI BIOS. It had Windows 8 factory-installed, where the Probook was originally a Windows 7 machine.
(In reply to Thomas Andrews from comment #32) > I bought the Probook in 2016, and it was definitely more than a year old. > The BIOS is from 2015, the latest available, but the hardware itself is from > 2010. Decoding the serial number to be precise, November 2010. > > That fits with it using a first-generation i3, and having a Legacy BIOS > rather than UEFI. The BIOS does have a secure boot option, but it's labeled > as "experimental" and disabled by default. > > Conversely, my Pavilion 15, which IS from 2015, has a fully operational UEFI > BIOS. It had Windows 8 factory-installed, where the Probook was originally a > Windows 7 machine. I'm basing just in what inxi reports, but of course could be incomplete ;) BTW boomaga not works also in VM, later will test in 32b system
I'll try with the basic, i.e rebuild the current version, but I not expect difference
(In reply to katnatek from comment #34) > I'll try with the basic, i.e rebuild the current version, but I not expect > difference As expected not change :(
Another shot in the dark: i removed - microcode-0.20250211-1.mga9.nonfree.noarch - microcode_ctl-2.1-11.mga9.x86_64 and rebooted, no change; "Can\'t start boomaga gui." --- Another idea to try is to make a persistent Mageia 9 Plasma live system on USB, only add boomaga and deps and see if it works, then update all and see if it works. If it worked then stopped working, revert (empty persistence) and try updates selectively until it stop working. I see from my Comment 7 above that it first did not work, then at that date had started working. And this is the same system, same install as now have boomaga stopped working.