[gentoo-user] Re: screensaver problem : PS
Sorry, I should add that my desktop is the latest stable KDE + Qt & Xscreensaver is the latest stable version 6.01-r4 . -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
[gentoo-user] screensaver problem
I have Xscreensaver started by .xinit & it runs as it should ; each saver is set to run for 3 min . When I'm asleep, I kill Xscreensaver & the monitor blanks after 5 min , which is also what is expected. However, something is telling the monitor to blank after 5 min , even when Xscreensaver is running. The 1st saver runs for 3 min , then the next one starts & runs for 2 min , then the screen blanks. When I hit a key or move the mouse, the screen wakes up & if there's no activity for 5 min Xscreensaver takes over & the savers run for 5 min before the screen blanks again. Instead, the savers should run continually till activity resumes. Can anyone suggest what is telling the monitor to blank after 5 min regardless of whether Xscreensaver is running or not ? -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] MEGA sync problems
On Saturday, October 9, 2021 7:33:04 A.M. AEDT Skippy wrote: > Greetings. > > I have been using Megasync with Gentoo for many moons. Now I'm having an > assortment of problems. > > Mega is not in the official Gentoo. I've been getting my ebuilds from here: > > http://gpo.zugaina.org/net-misc/megasync > > I currently have 4.4.0 installed. This was working fine until about 2-3 > weeks ago. Now I get this error message when I attempt to start it. > > > -- > > There are newer versions available so I figured this was a good > indicator I should just update Megasync. > > Well the universe hates me and every version of Megasync newer than > 4.4.0 fails. In fact if I attempt to re-emerge my existing 4.4.0 that > fails as well. > > Here is the full emerge log for version 4.5.3. > > https://zerobin.net/?e8b7f31b1ce11c23#4wTnxsnZ+v31rS8PLplBxM+//23zC5b0rMXSAT > uoYDQ= > > I've been informed that 4.5.3 is failing because it needs <=ffmpeg-3.4. > > That brings me to how to install such a version of ffmpeg. My limited > understanding of slots tells me this should be possible, but I've yet to > find anything explaining how to install the older ffmpeg without > disturbing the newer version. > > Any help with this would be greatly appreciate. Much thanks. > > Skippy > - > > root # emerge -pqv '=net-misc/megasync-4.5.3::Skippy' > [ebuild U ] net-misc/megasync-4.5.3 [4.4.0] USE="cryptopp curl > readline sqlite thunar zlib -dolphin -examples -freeimage -gnome -java > -nautilus -php -python -threads (-qt5%*)" ABI_X86="32 (64) (-x32)" > > It looks like you are downloading the ebuild by hand from their web site. I just installed Megesync 4.5.3 on my system, which has ffmpeg-4.4 The commands I used were: layman -a 4nykey to add the 4nykey overlay, which contains megasync, then emerge -a megasync just like other portage programs. If you still get any crypto-related errors, have a look for the recent news item "*2021-07-23-libxcrypt-migration*" eselect news list will get you a list. -- Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/ Asking for technical help in newsgroups? Read this first: http://catb.org/~esr/faqs/smart-questions.html#intro
Re: [gentoo-user] MEGA sync problems
On Fri, 2021-10-08 at 14:33 -0600, Skippy wrote: > > I've been informed that 4.5.3 is failing because it needs <=ffmpeg-3.4. > > That brings me to how to install such a version of ffmpeg. My limited > understanding of slots tells me this should be possible, but I've yet to > find anything explaining how to install the older ffmpeg without > disturbing the newer version. It needs something older than ffmpeg-4.4. You can try the previous version: $ emerge -v1 =media-video/ffmpeg-4.3.2-r1 ffmpeg isn't slotted, so you can't install two versions at the same time. Ideally, the maintainer of the overlay would update the megasync ebuilds to require the older ffmpeg. That should work so long as nothing else on your system needs the newer version of ffmpeg.
[gentoo-user] MEGA sync problems
Greetings. I have been using Megasync with Gentoo for many moons. Now I'm having an assortment of problems. Mega is not in the official Gentoo. I've been getting my ebuilds from here: http://gpo.zugaina.org/net-misc/megasync I currently have 4.4.0 installed. This was working fine until about 2-3 weeks ago. Now I get this error message when I attempt to start it. MEGAprivate ERROR DUMP Application: MEGAsync [64 bit] Hash: 222639c0477a2da3b8cd2db6aea44b43 Version code: 4400.0 Module name: megasync Timestamp: 1633485549320 Operating system: Linux System version: gentoo 2.8/#1 SMP PREEMPT Fri Aug 14 14:04:49 MDT 2020 System release: 5.7.15-gentoo System arch: x86_64 Error info: Segmentation fault (11) at address 0 Stacktrace: /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP8CCM_Base6ResyncEPKhm+0x4a) [0x7f7a441d7fba] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP8CCM_Base6ResyncEPKhm+0x4a) [0x7f7a441d7fba] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP32AuthenticatedSymmetricCipherBase6SetKeyEPKhmRKNS_14NameValuePairsE+0x2e) [0x7f7a441c37ce] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP21SimpleKeyingInterface12SetKeyWithIVEPKhmS2_m+0x116) [0x7f7a441a3086] megasync(+0x26e68c) [0x5624a3d7368c] megasync(+0x2055db) [0x5624a3d0a5db] megasync(+0x34242f) [0x5624a3e4742f] megasync(+0x349220) [0x5624a3e4e220] megasync(+0x34932d) [0x5624a3e4e32d] /usr/lib64/libQt5Core.so.5(+0xc7e67) [0x7f7a4286ee67] /lib64/libpthread.so.0(+0x7cde) [0x7f7a4278ecde] /lib64/libc.so.6(clone+0x3f) [0x7f7a423577ef] -- MEGAprivate ERROR DUMP Application: MEGAsync [64 bit] Hash: 2c43c6c01ca4c7702c7d9d060adc8e61 Version code: 4400.0 Module name: megasync Timestamp: 1633442861697 Operating system: Linux System version: gentoo 2.8/#1 SMP PREEMPT Fri Aug 14 14:04:49 MDT 2020 System release: 5.7.15-gentoo System arch: x86_64 Error info: Segmentation fault (11) at address 0 Stacktrace: /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP8CCM_Base6ResyncEPKhm+0x4a) [0x7f8962d6ffba] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP8CCM_Base6ResyncEPKhm+0x4a) [0x7f8962d6ffba] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP32AuthenticatedSymmetricCipherBase6SetKeyEPKhmRKNS_14NameValuePairsE+0x2e) [0x7f8962d5b7ce] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP21SimpleKeyingInterface12SetKeyWithIVEPKhmS2_m+0x116) [0x7f8962d3b086] megasync(+0x26e68c) [0x55969c9ff68c] megasync(+0x2055db) [0x55969c9965db] megasync(+0x34242f) [0x55969cad342f] megasync(+0x349220) [0x55969cada220] megasync(+0x34932d) [0x55969cada32d] /usr/lib64/libQt5Core.so.5(+0xc7e67) [0x7f8961406e67] /lib64/libpthread.so.0(+0x7cde) [0x7f8961326cde] /lib64/libc.so.6(clone+0x3f) [0x7f8960eef7ef] -- MEGAprivate ERROR DUMP Application: MEGAsync [64 bit] Hash: 22b147369050913c257ead946c2a5694 Version code: 4400.0 Module name: megasync Timestamp: 1633441090912 Operating system: Linux System version: gentoo 2.8/#1 SMP PREEMPT Fri Aug 14 14:04:49 MDT 2020 System release: 5.7.15-gentoo System arch: x86_64 Error info: Segmentation fault (11) at address 0 Stacktrace: /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP8CCM_Base6ResyncEPKhm+0x4a) [0x7f5a3c060fba] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP8CCM_Base6ResyncEPKhm+0x4a) [0x7f5a3c060fba] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP32AuthenticatedSymmetricCipherBase6SetKeyEPKhmRKNS_14NameValuePairsE+0x2e) [0x7f5a3c04c7ce] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP21SimpleKeyingInterface12SetKeyWithIVEPKhmS2_m+0x116) [0x7f5a3c02c086] megasync(+0x26e68c) [0x55dc26dee68c] megasync(+0x2055db) [0x55dc26d855db] megasync(+0x34242f) [0x55dc26ec242f] megasync(+0x349220) [0x55dc26ec9220] megasync(+0x34932d) [0x55dc26ec932d] /usr/lib64/libQt5Core.so.5(+0xc7e67) [0x7f5a3a6f7e67] /lib64/libpthread.so.0(+0x7cde) [0x7f5a3a617cde] /lib64/libc.so.6(clone+0x3f) [0x7f5a3a1e07ef] -- MEGAprivate ERROR DUMP Application: MEGAsync [64 bit] Hash: cccd6451f0ed3093e9c2ce5120d5f2b2 Version code: 4400.0 Module name: megasync Timestamp: 1633441044705 Operating system: Linux System version: gentoo 2.8/#1 SMP PREEMPT Fri Aug 14 14:04:49 MDT 2020 System release: 5.7.15-gentoo System arch: x86_64 Error info: Segmentation fault (11) at address 0 Stacktrace: /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP8CCM_Base6ResyncEPKhm+0x4a) [0x7f394dd80fba] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP8CCM_Base6ResyncEPKhm+0x4a) [0x7f394dd80fba] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP32AuthenticatedSymmetricCipherBase6SetKeyEPKhmRKNS_14NameValuePairsE+0x2e) [0x7f394dd6c7ce] /usr/lib64/libcryptopp.so.8(_ZN8CryptoPP21SimpleKeyingInterface12SetKeyWithIVEPKhmS2_m+0x116) [0x7f394dd4c086] megasync(+0x26e68c) [0x56520b23a68c] megasync(+0x2055db) [0x56520b1d15db] megasync(+0x34242f) [0x56520b30e42f] megasync(+0x349220) [0x56520b315220] megasync(+0x34932d) [0x56520b31532d] /usr/lib64/libQt5Core.so.5(+0xc7e67) [0x7f394c417e67] /lib64/libpthread.so.0(+0x7cde) [0x7f394c337cde] /lib64/libc.so.6(clone+0x3f) [0x7f394bf007ef]
Re: [gentoo-user] Re: acrobat reader
On Fri, 2021-10-08 at 12:28 +0300, Nikos Chantziaras wrote: > On 22/09/2021 22:29, the...@sys-concept.com wrote: > > I have evince, it will not open it. > > > > This is the form I'm trying to open: > > > > https://cfr.forms.gov.ab.ca/Form/AHC0102.pdf > > I just opened this URL in firefox-bin-93.0, which claims support for > "XFA-based forms", and indeed I can fill it out just fine. Good to know. Credit is due to Mozilla for their work on pdf.js I suppose.
[gentoo-user] Re: acrobat reader
On 22/09/2021 22:29, the...@sys-concept.com wrote: I have evince, it will not open it. This is the form I'm trying to open: https://cfr.forms.gov.ab.ca/Form/AHC0102.pdf I just opened this URL in firefox-bin-93.0, which claims support for "XFA-based forms", and indeed I can fill it out just fine. So finally solved, I suppose?
Re: [gentoo-user] Soft scrolling on framebuffer consoles - New versions of the patches.
On Thursday, 7 October 2021 20:46:51 BST Alan Mackenzie wrote: > Here are the latest versions of my soft scrolling patch for the kernel > lines 5.10.xx and 5.14.xx. They fix bugs where a PC would crash if it > was initialised with a 25x80 console and later changed to a full > resolution frame buffer screen. It also now works (so I am told) for > kernels initialised with parameters like vga=791. --->8 Thank you for your efforts on all our behalf Alan. -- Regards, Peter.
