March 2024 - openSUSE Users - openSUSE Mailing Lists

Slowroll repos and updating
by Ben T. Fender 21 Mar '24

21 Mar '24

I load a fresh Tumbleweed, go into Yast and delete every single repo. Then I 'begin' the routine linked here and quoted below... https://en.opensuse.org/openSUSE:Slowroll rm /etc/zypp/repos.d/* ...which in essence dumps any existing repo but when I reload Yast they're all back there! If I then continue with the ritual I end up with 14 mostly TW repos and trying to do 'zyopper up' get me a warning about tumbleweed needing 'zypper dup'. As for 'zypper up', it will use 14 repos, mostly Tumbleweed! Not sure if this was the intent :-) ----------------------------------------- zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/oss/ base-oss zypper ar --refresh http://cdn.opensuse.org/slowroll/repo/non-oss/ base-non-oss zypper ar --refresh -p 80 http://cdn.opensuse.org/update/slowroll/repo/oss/ update zypper ar --refresh --disable http://cdn.opensuse.org/slowroll/repo/src-oss/ base-src-oss zypper ar --refresh --disable https://download.opensuse.org/debug/slowroll/repo/oss/ base-oss-debug zypper ar --refresh http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/ h264 zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman

5 9

read-only filesystem
by Roger Oberholtzer 20 Mar '24

20 Mar '24

I have a strange (to me) situation on a Tumbleweed system with btrfs filesystems. Due to issues updating to KDE6, I had to rollback. And the rollback did not really roll back. So I snapper rm'd the various pre/post items so that the snapshot before the attempted update was the default one. It is now sorted so that it boots into the snapshot that I want. All of the file systems are mounted rw. I see this in the mount command. There are no ro file systems (except /boot/uefi). However, when I try to write to most of the file systems, it complains that they are read-only. At the mount level, they are not mounted read-only. So it must be the case that somewhere there is a flag that the file systems are read-only. I've only encountered this at the mount level. I tried a mount -oremount,rw on them, and it completes without a complaint. But there is no change. And as the mount command lists that they are rw, this is no surprise. I am bnot mounting into a read-only snapshot. Or at least I am not choosing that when booting. It is just the default snapshot that is being used. Where else other than via mount can a file system be made read-only? And how to correct that? -- Roger Oberholtzer

8 34

Spam Filter Testing
by Masaru Nomiya 16 Mar '24

16 Mar '24

Please ignore

1 0

packman repo fit
by bent fender 16 Mar '24

16 Mar '24

It happens that a "zypper dup" ends with a stalling download. Right now I have this Retrieving: Mesa-gallium-23.3.6-1699.369.pm. 1.x86_64.rpm ..............<51%>==============[- (2.4 KiB/s)] And if I do nothing but come back in 50 years time it will still be exactly the same. I tried "zypper ref", "zypper clean --all" nothing seems to work. The one thing that does is to go into Yast-Software and lock the package and then come back to do zypper before Yast again to unlock it (until the next time). It seems like THIS 'whaaaaatever' happens invariably with the packman repo and very ofgtyen with Mesa-xyz. Anyone know exactly WHAT the cause is, I can't even TRY countermeasures without knowing what it is. TIA

2 5

plasmoids and kde 6
by Stakanov 15 Mar '24

15 Mar '24

will plasmoids still exist on kde6 or have they been abolished? It is clear to me that there will be a period of transition but kde6 does not seem to have the menu points (right click) "join plasmoid" at all. Anybody knows? thank you

2 1

Lost all multimedia playing
by Albert Oszkó 10 Mar '24

10 Mar '24

Hi, I thought I put on some music while scanning old photos. I did not succeed: the loudspeaker icon on the tray is crossed, and says there isn't any application that plays or records sound. No vlc, no smplayer, no youtube, nothing. I tried the tips found on the the net, but none of them worked (or i would not write this letter). I have Tumbleweed with KDE Any help is welcome Thanks, Albert

4 3

Proot and android and dbus-broker question while using openSUSE Tumbleweed
by Mgr. Janusz Chmiel 08 Mar '24

08 Mar '24

Dear advanced Opensuse users and developers, I Am running several Linux distributions on my Android devices. I would like to ask somebody of us, if Dbus-broker does support Android kernel system calls? So Dbus-broker can be used even in userspace mode when Android and not real Linux kernel is being used. Why I want to use dbus-broker on my Android devices? Because The Dbus-broker speed up interprocess communication. Especially when reading long list of E-mail messages while working with many thousants of E-mail messages while using Seamonkey E-mail client. Please could someone of us try to invent The commands, which could be executed to allow Dbus-broker work on Android kernel? I Am using Termux and Proot special C binary, which uses Btrace to change and retranslate system calls and folders name to allow to run Linux on Android. Sure. There are plenty of limitations, which are being caused by The difference between real Linux kernel and Android kernel. It is not possible to use Qemu on cheap Android phones. Only expensive Pixel phones support Kqemu hardware virtualisation directly on their CPU level. But those expensive models of Android devices are out of my scope. Running Qemu and real Linux kernel does have sense only for developers, who want to run less intensive tasks. I can not boot Opensuse and run Mate and Orca while using Qemu in user mode. Rooting phones is not easy and it can corrupt phones firmware. Proot is The best available alternative. So if someone of us could describe how to start dbus-broker on Android, I will be very positively impressed. I have been able to use Orca, Mate desktop and Tuner Internet radio while using The latest available Opensuse packages for AArch64 architecture. Unfortunately, using Seamonkey is very very slow. So I Am hoping, that Dbus-broker will speed it up. Normal Dbus work normally.

1 0

cups 2 printersetup for one printer
by Simon Becherer 08 Mar '24

08 Mar '24

Hi, since years i use 2 (or more) printer setups in cups to use one printer. -> for different "standard" settings lets say its a color printer, but to save money often i like to print black and white. so i define a printer with the a ppd file and same printer adress twice, one with color settings one with settings black and white. so i have not to click and search all the printer settings to set up this 2 main settings. instead if i like to print color, i use the "color printer, or the foto-setting-printer or the black-and-white printer. since years i have used this with different printers "hp" and "qms" was working. since about a year i own a "sharp mx3060" i do not know if cups has changed anything or if its the printer. but it did not work any more. i have 2 stored ppd's inside etc/cups/ppd/... "sharp_mx-306N-sw" (black and white) "sharp_mx-306N" (colorsettings) but after i print something in one or the other, it changed settings for both. not inside the ppd file (it has always the same timestamp and is not changed since setup the printer), but somwhere else. the etc/cups/printers.conf show the "2" printers </Printer> <Printer SHARP_MX-3060N> PrinterId 6 UUID urn:uuid:959c4210-b868-3eea-7a36-b457b2df28a9 AuthInfoRequired none Info SHARP MX-3060NPCL_PS Location oben MakeModel Sharp MX-3060N PS, 1.2 DeviceURI ipp://192.168.0.11/ipp State Idle StateTime 1700126750 ConfigTime 1656701711 Type 8401116 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Attribute marker-colors \#00FFFF,#FF00FF,#FFFF00,#000000 Attribute marker-levels 50,91,27,96,0,53,53,53,87,77,77,77,66,-1 Attribute marker-low-levels 1,1,1,1 Attribute marker-high-levels 100,100,100,100 Attribute marker-names cyan,magenta,yellow,black Attribute marker-types toner,toner,toner,toner Attribute marker-change-time 1700126750 </Printer> <DefaultPrinter SHARP_MX-3060N-sw> PrinterId 7 UUID urn:uuid:2ab5b068-ec17-3277-58a9-b8c1a50cbfa9 AuthInfoRequired none Info SHARP MX-3060NPCL_PS Location oben MakeModel Sharp MX-3060N PS, 1.2 DeviceURI ipp://192.168.0.11/ipp State Idle StateTime 1700201877 ConfigTime 1656710353 Type 8401116 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy stop-printer Attribute marker-colors \#00FFFF,#FF00FF,#FFFF00,#000000 Attribute marker-levels 50,91,27,96,0,53,53,53,87,77,77,77,66,-1 Attribute marker-low-levels 1,1,1,1 Attribute marker-high-levels 100,100,100,100 Attribute marker-names cyan,magenta,yellow,black Attribute marker-types toner,toner,toner,toner Attribute marker-change-time 1700201877 </DefaultPrinter> so the question ist, where is cups storing actual printer settings, (color or bw, duplex or singele page......) (somewhere in the home directroy?) and why did this 2 printerques interfer each other? simoN -- www.becherer.de

3 4

acpi journalctl errors:
by -pj 08 Mar '24

08 Mar '24

Hi, I am attempting to operate openSUSE Tumbleweed on this machine (fully updated). I and have discovered acpi errors in journalctl output. These errors are shown as follows: > Thinkcentre-M57p:/etc/udev/rules.d # journalctl -p3 -b > Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0._OSC.CAPB], AE_ALREADY_EXISTS (20230628/dsf> > Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20230628/dswload2-477) > Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (20230628/psparse-529) > Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: platform INT0800:00: failed to claim resource 0: [mem 0xff800000-0xffffffff] > Mar 06 18:06:06 paul-Thinkcentre-M57p kernel: acpi INT0800:00: platform device creation failed: -16 > Mar 06 18:06:23 paul-Thinkcentre-M57p kernel: I do hope the journalctl output above is displayed correctly. I chose to 'paste as quotation' the journalctl output using Thunderbird mail client here. I have also attempted adding the 'acpi=off' parameter to /etc/default/grub then updated grub/bootloader resulting in *no graphical target* is reached after powercycling the machine. What is displayed is TTY login - which I can login and then remove the "acpi=off" parameter. My brief searching of this on the web has not yielded results explaining anything related to failing to load into SDDM or KDE. Do you think these acpi warnings could have something to do with: Hibernating the machine results in a proper hibernation *but* does not shut completely down (2 seconds then instantly powers up again) - goes through boot - grub - login again... What is going on here what are your thoughts about this?

4 14

Attempting to Hibernate, powercycles machine instead::
by -pj 07 Mar '24

07 Mar '24

Hello, A question for you is that currently attempting to 'Hibernate' (tried twice), the machine goes through the process...halts/poweroff *completely* for about a second. All signs of PSU and display features turn off.... then suddenly powers up at bios menu. After entering the LUKS passphrase some boot information is displayed. pertaining to the prior "Hibernate" attempt (I believe). Here is some journalctl output on this: Thinkcentre-M57p:/> journalctl -b -1 | grep "hibernate" Feb 17 13:15:48 Thinkcentre-M57p systemd[1]: systemd-hibernate-resume.service: Deactivated successfully. - I recently created a PS2.Keyboard.service to try allow for 'suspend' to work with my PS/2 connector style keyboard in an attempt to mitigate the i8042 controller bug. The machine seems to work well now when suspend is envoked. - I have increased the swap partition and swap on the system to 15.5G . # swapon NAME TYPE SIZE USED PRIO /dev/dm-1 partition 15.5G 2.3G -2 Thinkcentre-M57p:/> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS fd0 2:0 1 4K 0 disk sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 8M 0 part └─sda2 8:2 0 931.5G 0 part └─Lenovo_M57p-openSUSE_Tumbleweed 254:0 0 931.5G 0 crypt ├─system-swap 254:1 0 15.5G 0 lvm [SWAP] └─system-root 254:2 0 916G 0 lvm /var /usr/local /srv /root /opt /home /boot/grub2/x86_64-efi /boot/grub2/i386-pc /.snapshots / sdb 8:16 1 1.9G 0 disk └─luks-fd28e551-c765-461e-aab0-a2c49bb786b9 254:3 0 1.9G 0 crypt /run/media/paul/WORLDWIDE1 sr0 11:0 1 1024M 0 rom - Do you know what is going on here by preventing "hibernate' feature from functioning completely? -Regards

3 14