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
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
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
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?
Some months ago it was possible to receive files via bluetooth with TW.
But since some weeks that fails for me. I waited for GNOME 3.20 and the
new bluez in the hope it will fix itself, but the failure remains:
Apr 05 18:01:28 probook obexd[3042]: CONNECT(0x0), (null)(0xffffffff)
Apr 05 18:01:28 probook obexd[3042]: CONNECT(0x0), (null)(0x0)
Apr 05 18:01:32 probook obexd[3042]: PUT(0x2), (null)(0xffffffff)
Apr 05 18:01:32 probook obexd[3042]: open(/home/olaf/.cache/obexd/GSIBFY): No such file or directory (2)
Apr 05 18:01:32 probook obexd[3042]: PUT(0x2), NOT_FOUND(0x44)
Apr 05 18:01:32 probook obexd[3042]: DISCONNECT(0x1), (null)(0xffffffff)
Apr 05 18:01:32 probook obexd[3042]: DISCONNECT(0x1), SUCCESS(0x20)
Apr 05 18:01:32 probook bluetoothd[1520]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)
Apr 05 18:01:32 probook obexd[3042]: disconnected: Transport got disconnected
Apr 05 18:02:42 probook obexd[3042]: CONNECT(0x0), (null)(0xffffffff)
Apr 05 18:02:42 probook obexd[3042]: CONNECT(0x0), (null)(0x0)
Apr 05 18:02:42 probook obexd[3042]: PUT(0x2), (null)(0xffffffff)
Apr 05 18:02:42 probook obexd[3042]: open(/home/olaf/.cache/obexd/1OLQFY): Operation not permitted (1)
Apr 05 18:02:42 probook obexd[3042]: PUT(0x2), FORBIDDEN(0x43)
Apr 05 18:02:42 probook obexd[3042]: DISCONNECT(0x1), (null)(0xffffffff)
Apr 05 18:02:42 probook obexd[3042]: DISCONNECT(0x1), SUCCESS(0x20)
Apr 05 18:02:42 probook bluetoothd[1520]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)
Apr 05 18:02:42 probook obexd[3042]: disconnected: Transport got disconnected
First I tried to remove /home/olaf/.cache/obexd, but nothing seems to
feel responsible to create this dir as seen with the first error. Then I
created it with mkdir -m07777, and that just gives the EPERM error as
before. strace shows that it gets some "forbidden" from dbus.
Is receiving files working for anyone else?
Also the rfkill thing does not work reliable. NetworkManager finds the
device according to syslog, but the GNOME bluetooth thing finds nothing.
Something softblocks it:
root@probook:~ # hciconfig -a hci0 reset
Can't init device hci0: Operation not possible due to RF-kill (132)
root@probook:~ # rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Need to run 'rfkill unblock 4' manually to get it going. Once that it
done its appearently possible to use the UMTS, and sending a file works
as well.
Olaf
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello!
After lastest updates in Tumbleweed I can't play mp3 files with Amarok
or Clementine, but VLC works fine.
If I launch Amarok via CLI I get this:
"Phonon::GStreamer::Backend: Failed to initialize GStreamer
WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no
objectName ) to Phonon::AudioDataOutput ( no objectName ).
WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no
objectName ) to Phonon::AudioOutput ( no objectName ). "
With Clementine I get this:
"GStreamer could not create the element: audioconvert. Please make sure
that you have installed all necessary GStreamer plugins (e.g. OGG and MP3)"
Any clue about this? Thanks in advance.
Greetings.
--
-------------------
GPG Key: 0xcc742e8dc9b7e22a
Aprende a proteger la privacidad de tu correo:
https://emailselfdefense.fsf.org/es/
Mi blog sobre openSUSE, GNU/Linux y software libre:
https://victorhckinthefreeworld.com/
Hello all,
I am looking for volunteers to maintain the two packages in $SUBJ.
We are cleaning up for SLE15 and these two will end up without
maintainer.
osc reqms network wvdial
osc reqms Base:System rzsz
As such if nobody steps up lets say until 26.8. I will fill up
droprequest for them (Later on of course they can be re-introduced by
someone who would care enough).
Cheers
Tom
In bsc#1052060 Freek de Kruij reports a bug in firmware loading at bootup for
b43 with Leap 42.3. I have confirmed the problem, and verified that Leap 42.2
and Tumbleweed work correctly.
This is not a kernel problem as my tests were all done with a 4.13-rcX kernel. I
suspect a udev problem; however, TW and 42.3 appear to be using the same
revision for udev. Can anyone tell me to whom the bug should be reassigned?
Thanks,
Larry
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi there,
I prefer AMD underdog over monopolists any day and I read interesting
stuff about new amd support on the 4.13 kernel, especially turbostat ,
changes made to /proc/cpuinfo not reflecting current MHz any more,
cpupower and maybe lot of other neat stuff.
Any chance for backport to 42.3 kernel and so on? Thanks lots.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org