openSUSE Factory September 2017

factory@lists.opensuse.org

108 participants
76 discussions

[opensuse-factory] [Tumbleweed] dracut wails about not being able to disassemble device-mapper

by Achim Gratz

Since a few weeks dracut spews about two pages of errors/warnings on shutdown. Yesterday I halted the system instead of poweroff to be able to read those and it seems that the unmount of /oldroot fails and then the disassembly of the device-mapper devices errors out (maybe there'd been other errors before that that already rolled off the screeb). Does anybody have an idea what is going on and how to fix it? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 years, 3 months

[opensuse-factory] GNOME Wayland (in QEMU)

by Andrei Borzenkov

I'm trying to play with Wayland. The issues so far 1. I originally had XFCE pattern when installing TW. I installed gnome-wayland-session pattern which pulled in some dependencies including gdm. But gdm simply does not work - whatever session I select it fails to login as any user. I presume this is the old "patterns are not self contained" issue (I never managed to recreate anything proposed by installer post-installation, which is why I was rather sad seeing these choices removed from installation dialogue). 2. In lightdm I see two GNOME sessions and one "GNOME Xorg" session. Whatever session I select I apparently end up in GNOME on Xorg (at least if I can believe loginctl session type). How can I start GNOME Wayland session from display manager? What gnome-session-wayland is supposed to do - desktop file it installs is not in any way different from "normal" desktop? 3. I can select Weston in lightdm and it actually works - it starts weston (and loginctl confirms that session type is wayland), so wayland itself sort of works - but keyboard is unusable. It seems to miss key presses/releases, so first no character is entered, when I press the same character once more it often starts auto-repeat filling screen with the same character over and over. 4. I can start GNOME wayland from tty using XDG_SESSION_TYPE=wayland exec dbus-run-session gnome-session but session type remains tty and I have exactly the same issue with keyboard (now in gnome-terminal instead of weston-terminal). Any ideas? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 years, 6 months

[opensuse-factory] *Updated* NVIDIA gfx driver RPMs available for Tumbleweed ...

by Stefan Dirsch

Hi Since today there are updated NVIDIA gfx driver RPMs available for Tumbleweed. Feel free to give them a/another try by adding the repository manually via zypper ar https://download.nvidia.com/opensuse/tumbleweed nvidia-tumbleweed (if not created yet) and install them via zypper inr (or "zypper up", if already installed) The kernel module is being built during installation (as it's done with the Leap packages). But the kernel module is also being rebuilt and reinstalled after a kernel update has been done, since we don't necessarily keep the kABI stable for TW. This has been implemented by making use of RPM's trigger scripts. Issues fixed in this update: - gdm could not be started Known issues/limitations: https://download.nvidia.com/opensuse/tumbleweed nvidia-tumbleweed is a non-browsable directory, so please don't tell me it doesn't exist after pasting it into your favorite web-browser. ;-) Packages are only available for the latest long lived branch (currently 384.59). Reason is, that with TW we switched to libglvnd, which is not supported by the legacy driver series 340.xx and 304.xx. If you had NVIDIA driver installed manually when updating TW from Mesa to libglvnd+Mesa, you'll see an orphaned libGL.so.1.2* in /usr/lib64 and /usr/lib. This may have happened unnoticed. So please check this after running nvidia-installer --uninstall and remove these files, if available via rm -f /usr/lib*/libGL.so.1.2* before installing the NVIDIA RPMs. This is already documented in https://en.opensuse.org/SDB:NVIDIA_the_hard_way You can provide feedback here in this mail thread or via bugzilla. If you use Bugzilla, please use Product: openSUSE Tumbleweed Component: X11 3rd party Driver Thanks, Stefan Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany --------------------------------------------------------------- SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 years, 6 months

[opensuse-factory] SUSE Studio Express questions

by S.

Congrats to the team on getting this integration rolling. Quick question: > Since OBS already builds images for various environments, we will first add a new image building GUI to OBS. This combined solution will now be delivered as “SUSE Studio Express”. Currently when I go to https://studioexpress.opensuse.org/ I just see a landing page with links to the OBS image templates and some instructions. But I don't see a new GUI or visual way of putting together a custom image, except for the "Edit Kiwi" section. Is the full GUI still forthcoming? And what about external repositories? It appears that non-OBS RPM repos added to Studio Express fail unless they have the `obs:/` scheme address. So that means no adding external repos such as Packman? (As a matter of fact, it looks like none of my repos from the SuseStudio import work, even the openSUSE OSS ones, since they use an `http://` URL scheme.) Also, with the "KIWI Image Templates for openSUSE Leap 42.3", which would I use for a live ISO image that can run on physical hardware? All the current templates seem to be only for virtualization systems. > other features are not on the roadmap like test drive I'll sure miss this one. As the developer of GeckoLinux with no less than seventeen (17) different ISO editions, the test drive was the single biggest time saver that allowed me to test configurations. It even had a fascinating feature where you could see what files were getting changed during the test drive session, complete with diffs of the changes, and then you could hand pick which modified files to overlay in the final ISO. I learned so much about how and where the different desktop environments save their settings thanks to this feature. I've learned to really appreciate SuseStudio despite all of its quirks and intricacies. I hope that the OBS / Studio Express feature set can be eventually improved to gradually come close to parity. SuseStudio, you will be missed! :-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 years, 7 months

[opensuse-factory] Tumbleweed snapshot 20170928 problem

by Larry Finger

Since upgrading to the snapshot of the subject, I am unable to use to start any graphics application. For example, "kdesu yast" returns "Invalid MIT-MAGIC-COOKIE-1 keyQXcbConnection: Could not connect to display :0". I get the same message when running the VirtualBox GUI. Firefox is unable to display any new pages; however, the program starts. My graphics driver is i915. In case it might be helpful, the output of "strace kdesu yast" is attached. Thanks, Larry

4 years, 7 months

[opensuse-factory] Workarounds for Buggy Bluetooth Audio

by Chan Ju Ping

I have problems with getting all my Bluetooth audio device pairing and working when first paired, and these steps nearly always get them to work, so I was wondering whether there is a root cause that can be pinned down and fixed as a bug report. Device: Mee Audio Air-Fi Rumble Headphone 1. No sound when paired. 2. Open Audio and Video system settings module in KDE. 3. Wait for it to appear, and select Air-Fi Rumble in Device Preference > Audio Playback and click Test. 4. Test audio plays and now audio works. Device: Bluedio Wireless Headset 1. No sound when paired. 2. Device not activated in Audio and Video system settings module in KDE. 3. Select Audio Hardware Setup > Soundcard > Bluedio 4. Toggle Profile to A2DP Sink (device not activated with this selection, but will be with HSP/HFP!) 5. Device will still be greyed out in Device Preference. Unpair and pair device again. 6. Device will show up in Device Preference, but without audio. 7. Select Bluedio and press the Test button. 8. Test audio plays and now audio works. I am not sure why both devices are treated differently, but it is certain that the Air-Fi is the more expensive device. Thoughts?

4 years, 7 months

[opensuse-factory] RHEL dumps Btrfs and replaces it with Stratis

by Roman Bysh

Hi all, Looks like Redhat will no longer use Btrfs in their next release and has replaced it with Stratis. Stratis appears to be an XFS derivative designed by Redhat. Can we see this as an option for openSUSE in the future? Cheers! Roman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 years, 7 months

[opensuse-factory] reproducible builds test results

by Bernhard M. Wiedemann

Hi, I did another round of rebuild testing for openSUSE Factory. All resulting build-compare diffs are in http://rb.zq1.de/compare.factory-20170406/ as well as a machine-readable summary http://rb.zq1.de/compare.factory-20170406/rbstats.txt current summary says: total-packages: 10971 build-tried: 10971 build-failed: 118 build-n-a: 114 build-succeeded: 10739 build-official-failed+na: 115 build-compare-failed: 1209 build-compare-succeeded: 9530 bit-by-bit-identical: 8133 not-bit-by-bit-identical: 2599 not-bit-by-bit-identicalcheck: 2606 meaning, 75% of packages already give bit-identical results. And half of the remaining problems are so bad that even build-compare filters do not help and thus trigger unnecessary rebuilds in OBS. and I have details about each of the 10971 packages http://rb.zq1.de/compare.factory-20170406/reproducible.json and a .diff file next to it, comparing it to the previous round The good news is, that nearly all of the packages that build in OBS, could be built locally as well, with 2 of 5 build bugs already fixed * https://bugzilla.opensuse.org/show_bug.cgi?id=1032257 * https://bugzilla.opensuse.org/show_bug.cgi?id=1031548 * https://bugzilla.opensuse.org/show_bug.cgi?id=1031549 * https://bugzilla.opensuse.org/show_bug.cgi?id=1031554 * https://bugzilla.opensuse.org/show_bug.cgi?id=1031556 Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 years, 7 months

[opensuse-factory] Need to click twice on shutdown to power-off TW

by Marco Calistri

Hello, I've posted same question if I'm not wrong time ago but didn't get answers. I'm using TW and I've installed four DE: Gnome, Cinnamon and XFCE IceWM. It happens that when I want to power-off the machine I need to repeat the steps twice: click on exit, power-off. This is needed with all the above DE. Would like to know if somebody else has faced same behavior and if it is possible to correct it in the way of just clicking exit, power-off once to shutdown the machine. Thanks. P.S. S/MIME testing -- TThheerree''ss aann EEcchhoo iinn hheerree.

4 years, 7 months

[opensuse-factory] TW and ksysguard

by Frans de Boer

LS, The past two-three weeks or so, ksysguard is losing a setting and displays the wrong cpu speeds. The clock speed is now always at his highest, while the ondemand governor is selected. Before, it ranged between 800 and 3600 MHz. Btw: the indicator is now 3615 MHz, which is the speed set in the BIOS. Thus, finally an accurate speed is displayed, but no change in clock speed displayed. The cpupower util does display correctly the various clock speeds. Second, the setting for vcore min is lost after terminating ksysguard. The setting for Vcore max is preserved. Regards, Frans de Boer. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory September 2017