Bug 1960829
| Summary: | after upgrade from fedora 33 to fedora 34 volume applet on lxpanel 0.10.1 disappear after 1st or 2th reboot if system have 1 or more cards with "UCM is not supported" on alsa but works with pulsaudio | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | a.trubitsyn |
| Component: | lxpanel | Assignee: | Christoph Wickert <christoph.wickert> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 34 | CC: | christoph.wickert, david_costanzo, mtasaka, pschmidt.gaz |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lxpanel-0.10.1-2.fc34 lxpanel-0.10.1-2.fc35 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-09-14 14:59:08 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
Created attachment 1783508 [details]
get this file by command sudo cp /etc/xdg/lxpanel/LXDE/panels/panel etc_xdg_lxde_panel.$CUR_DATE
Created attachment 1783509 [details]
get this file by command cp /home/$USER/.config/lxpanel/LXDE/panels/panel $USER_config_panel.$CUR_DATE
typo "allign" exists in live usb from may 13th 2021 # Fedora-LXDE-Live-x86_64-34-1.2.iso: 1371701248 bytes SHA256 (Fedora-LXDE-Live-x86_64-34-1.2.iso) = ac166d49f404a315cd3922a8e014e4cba19cf8f37242c1a4fd9c3ecba4bc269a how to reproduce: 1. get lxde iso 2. flash it on usb stick 3. boot any comuter 4. try sudo cat /etc/xdg/lxpanel/default/panels/panel | grep allign First of all, I don't understand what you want to do with - "get this file by command cp /home/$USER/.config/lxpanel/LXDE/panels/panel $USER_config_panel.$CUR_DATE" - "get this file by command sudo cp /etc/xdg/lxpanel/LXDE/panels/panel etc_xdg_lxde_panel.$CUR_DATE" or so. Copying the file, and after that, what to do? For historical reason, allign is supported. So, would you make it clear the issue you see? (In reply to Mamoru TASAKA from comment #4) i copy 3 config files from /home/$USER/.config/lxpanel/LXDE/panels/panel /etc/xdg/lxpanel/LXDE/panels/panel /etc/xdg/lxpanel/default/panels/panel and add it into this bug i don't understand why volume applet disappear after upgrade from fedora 33 to fedora 34 or after manually add it on panel and reboot fedora 34 and how to change this behaviour. i want to volume applet stay visible on panel after reboot. I cannot reproduce your issue. Even if I use your config file, after reboot volume applet appears on lxpanel as expected. By the way, are you using alsa on Fedora 34? lxpanel volume control tries to detect alsa, so maybe if you are using pipewire, no alsa daemon maybe running. In such case, lxpanel volume control cannot detect alsa and it closes immediately. Created attachment 1784860 [details]
lsof | grep lxpanel
(In reply to Mamoru TASAKA from comment #7) Thank you. > By the way, are you using alsa on Fedora 34? may be. I first set up this pc with rfremix 14 then upgrade to rfremix 15 ... 29, then fedora 30 ... 33. And it works perfectly. After upgrade to fedora 34 every time i want to change volume, i must click right mouse button on panel, add volume applet, adjust it position and use it. But after reboot volume applet removed from lxpanel. > lxpanel volume control tries to detect alsa, so maybe if you are using > pipewire, no alsa daemon maybe running. may be, but i see alsa-pipe in lsof. How to check it? > In such case, lxpanel volume control cannot detect alsa and it closes > immediately. I can use volume applet, but only before reboot. Then need to add it on lxpanel to use one more time. I sometime see tv programs on Behold TV 509 FM with 04:02.0 Multimedia controller: Philips Semiconductors SAA7131/SAA7133/SAA7135 Video Broadcast Decoder (rev d1) Subsystem: Beholder International Ltd. Behold TV 509 FM Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 32 (21000ns min, 8000ns max) Interrupt: pin A routed to IRQ 18 Region 0: Memory at fbdff000 (32-bit, non-prefetchable) [size=2K] Capabilities: <access denied> Kernel driver in use: saa7134 Kernel modules: saa7134 and use headset connected to audio out of motherboard with 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) Subsystem: Gigabyte Technology Co., Ltd Device a002 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 31 Region 0: Memory at fbff4000 (64-bit, non-prefetchable) [size=16K] Capabilities: <access denied> Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel So anyway you are using pipewire. Currently I don't use pipewire (although I use Fedora 34), I have not tried pipewire and to reproduce this, perhaps I may have to try it, and so debugging this will perhaps take so looooong time. And I think it is beyond the task of Fedora "maintainer", it is the upstream task. I would suggest you file a bug report against the upstream. I have been experiencing this issue as well, should have reported sooner but I manually changed from pulse to pipewire with "dnf --allowerasing" after the upgrade to fc34 so I was looking at some dependency I might have messed. However, after the update below the volume applet is no longer working (does not even appear), it is still listed in the panel items as an add option but nothing happens when trying to add it.
I created a new user to ensure it is a system issue, not a config issue, and confirmed that even with a fresh new user the volume applet is not working.
The pulseaudio session autostart option does not make any difference.
The update that made the bug change from vanishing after each restart to no longer working at all:
Upgrade pipewire-0.3.31-2.fc34.x86_64 @updates
Upgraded pipewire-0.3.30-4.fc34.x86_64 @@System
Upgrade pipewire-alsa-0.3.31-2.fc34.x86_64 @updates
Upgraded pipewire-alsa-0.3.30-4.fc34.x86_64 @@System
Upgrade pipewire-gstreamer-0.3.31-2.fc34.x86_64 @updates
Upgraded pipewire-gstreamer-0.3.30-4.fc34.x86_64 @@System
Upgrade pipewire-jack-audio-connection-kit-0.3.31-2.fc34.x86_64 @updates
Upgraded pipewire-jack-audio-connection-kit-0.3.30-4.fc34.x86_64 @@System
Upgrade pipewire-libs-0.3.31-2.fc34.x86_64 @updates
Upgraded pipewire-libs-0.3.30-4.fc34.x86_64 @@System
Upgrade pipewire-pulseaudio-0.3.31-2.fc34.x86_64 @updates
Upgraded pipewire-pulseaudio-0.3.30-4.fc34.x86_64 @@System
Checking the journal there is only one error that seems related, see below, but it is odd since the service itself is active and running (plus I can hear sounds correctly and control volume with pavucontrol):
pipewire-media-session[9388]: GetManagedObjects() failed: org.freedesktop.DBus.Error.ServiceUnknown
To be sure I also checked dbus and only found one warning:
dbus-broker-launch[1090]: Service file '/usr/share/dbus-1/services/gnome-vfs-daemon.service' is not named after the D-Bus name 'org.gnome.GnomeVFS.Daemon'.
I also see this bug. The Volume Control applet worked for me on FC32 but after I upgraded from FC32 to FC34, the Volume Control applet was always removed after reboot (as reported in the bug description). I was able to add it after lxpanel started until a few days ago. Now adding it does nothing, as reported in the previous comment. I don't know what changed in the meantime, but I expect it was a "dnf upgrade" As a work-around, I've added an application launcher for PulseAudio Volume Control. It's not as nice as the Volume Control applet, of course. I thought I might be able to help investigate by stepping through the code in a debugger on a system that has the problem, but I haven't been able to figure out where to set a breakpoint. Is the Volume Control applet in lxpanel or some other package? I was able to stumble around in gdb and I think I made progress. For my case, the problem is that asound_initialize is failing. It fails because the mixer has no elements. So when asound_initialize goes to look for { "Master", "Front", "PCM", "LineOut" }, it can't find any of them.
Once I realized this, I could see the problem clearly by running "alsamixer". There was nothing to mix and the sound card was listed as "pipewire".
I don't know anything about how audio works on a GNU/Linux system. I don't understand what ALSA, pulseaudio, or pipewire are, nor how they interact. However, I was able to get Volume Control to work by uninstalling most of the pipewire packages. Probably, the only one that mattered was uninstalling pipewire-alsa. After doing this, "alsamixer" showed all of the devices that you'd expect and I could add the volume control to lxpanel. I only just did this now (and rebooted to confirm that the volume control stays in place), so I don't know how much I'll regret not having pipewire-alsa. I've confirmed that Rythmbox can play audio and the volume can be controlled by lxpanel, but YouTube videos on Firefox don't have any audio.
This might not be a bug in lxpanel "Volume Control", but the end-user experience could be improved. For example, if it displayed a message like "Unable to find any devices in alsamixer", it might have led me to run "aslamixer" without resorting to a debugger. Then I would have seen pipewire is somehow interfering.
(In reply to David Costanzo from comment #13) > Probably, the only one that mattered was uninstalling pipewire-alsa. (In reply to Mamori Tasaka from comment #6) > lxpanel volume control cannot detect alsa and it closes immediately. Thank you both. sudo dnf remove pipewire-alsa, then add "volume control" and reboot works for me. With pipewire-alsa installed, alsamixer 1.2.5.1 in both "Card" & "Chip" show "Pipewire", then say something like "No any control available" (I don't remember this sentence exactly) Should this bug remain as a lxpanel bug? On one hand lxpanel should be able to recognize pipewire instead of ALSA, on the other pipewire-alsa should be a drop in ALSA replacement. To me it seems like this is a feature request against lxpanel and a bug against pipewire-alsa. Now with pipewire-alsa-0.3.32-1.fc34.x86_64 alsamixer find "Master". Card=PipeWare, Chip=Pipewire, Item=Master. But lxpanel "Volume Control" again disappear after reboot. Folks on this bug: Would you try $ sudo dnf copr enable mtasaka/lxpanel-bz1960829 $ sudo dnf upgrade lxpanel Then reboot and try to check if this works? (In reply to Mamoru TASAKA from comment #17) > Folks on this bug: > > Would you try > $ sudo dnf copr enable mtasaka/lxpanel-bz1960829 > $ sudo dnf upgrade lxpanel > > Then reboot and try to check if this works? Note that to try this, probably pipewire-alsa has to be installed with updated to the latest. Thank you! "Volume Control" not disappear any more after reboot. But it not work in my current configuration. May be it is a subject of another bug. 1. Volume control on xawtv or mpv is independent of lxpanel volume control. Volume control in alsamixer started from lxterminal works ( it change volume on both xawtv and mpv). 2. I can change volume with "Volume Control" in lxpanel, but after reboot it set to 0. (but "off" checkbox not checked) I see some strange behaviour. In comment 19 i wrote that volume control in lxpanel don't work. It is not always true. I install mtasaka/lxpanel-bz1960829, upgrade, add "Volume control", reboot. "Volume control" is in lxpanel, but don't change real volume. Then i try to change volume in alsamixer from lxterminal. it works. Then i change Card from Default to "HDA intel MID" in lxpanel applet. Now "Volume control" can change volume in xawtv & mpv, but after reboot it disappear again. Then i add "Volume control" applet one more time. It set "default" card automatically. But i can change real volume only with "HDA intel MID". After first card change in lxapplet it disappear after reboot. May be it will work on 2th or 3th try. I test it another 2-3 days. 1. "Volume control" don't disappear if it uses default card in its settings, but decrease volume to 0% after reboot. 2. If i change card from "Default" to "HDA intel MID" "Volume Control" applet disappear after 1th ot 2th reboot. If add this applet again and don't change default card, it's stay visible after several reboots, but in my case it is not useful in this configuration. After following comment #19 it did work for me including remembering the volume level. It is set to Default and Master and the system has, besides both pipewire and pipewire-alsa installed, also the following: alsa-lib-1.2.5.1-1.fc34.i686 alsa-lib-1.2.5.1-1.fc34.x86_64 alsa-ucm-1.2.5.1-1.fc34.noarch alsa-utils-1.2.5.1-1.fc34.x86_64 About the volume issue, maybe something happened to the alsa-state service of a.trubitsyn? How is this service supposed to interact with pipewire now? (In reply to pschmidt.gaz from comment #22) > About the volume issue, maybe something happened to the alsa-state service > of a.trubitsyn? How is this service supposed to interact with pipewire now? do you mean check systemctl status alsa-state.service ? on my machine it get this output: ● alsa-state.service - Manage Sound Card State (restore and store) Loaded: loaded (/usr/lib/systemd/system/alsa-state.service; static) Active: active (running) since Tue 2021-08-03 19:31:18 MSK; 3h 13min ago Main PID: 766 (alsactl) Tasks: 1 (limit: 9162) Memory: 432.0K CPU: 14ms CGroup: /system.slice/alsa-state.service └─766 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main rdaemon авг 03 19:31:18 xxx systemd[1]: Started Manage Sound Card State (restore and store). авг 03 19:31:18 xxx alsactl[766]: alsactl 1.2.5.1 daemon started авг 03 19:31:18 xxx alsactl[766]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 авг 03 19:31:18 xxx alsactl[766]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA Intel MID at 0xfbff4000 irq 31) авг 03 19:31:18 xxx alsactl[766]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6 i see something similar about UCM is not supported for this HDA model in this question: https://ask.fedoraproject.org/t/alsa-does-not-recognize-my-sound-card-any-more/14967 my configuration works well until 01.04.2021 then i start system-upgrade upgrade (171 in dnf history). i can send dnf history 171 output. on fedora 33 it works with pulseaudio.
This is output (with russian words) of
"dnf history info 171"
on
"system-upgrade upgrade"
at 01.04.2021
...
Установка pipewire-alsa-0.3.24-4.fc34.x86_64 @fedora
Исключено alsa-plugins-pulseaudio-1.2.2-4.fc33.x86_64 @@System
Установка pipewire-gstreamer-0.3.24-4.fc34.x86_64 @fedora
Установка pipewire-jack-audio-connection-kit-0.3.24-4.fc34.x86_64 @fedora
Исключено jack-audio-connection-kit-1.9.14-5.fc33.x86_64 @@System
Установка pipewire-pulseaudio-0.3.24-4.fc34.x86_64 @fedora
Исключено pulseaudio-14.0-2.fc33.x86_64 @@System
Исключено pulseaudio-module-x11-14.0-2.fc33.x86_64 @@System
Установка pipewire-utils-0.3.24-4.fc34.x86_64 @fedora
...
Вывод скриптлета:
6 Created symlink /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket → /usr/lib/systemd/user/pipewire-pulse.socket.
9 Removed /etc/systemd/user/sockets.target.wants/pulseaudio.socket.
Where "Установка" may be "Install",
"Исключено" may be "Remove",
"Вывод скриптлета:" may be "Scriptlet output" or something.
Looking at google, it seems that "UCM is not supported for this HDA model" error is due to "alsa-lib 1.2.5" issue. Can you try alsa-lib 1.2.4 version? For example: https://koji.fedoraproject.org/koji/buildinfo?buildID=1674578 Thank you very much.
I download alsa-lib-1.2.4-5.fc34.i686.rpm & alsa-lib-1.2.4-5.fc34.x86_64.rpm from your link.
Then do
sudo dnf downgrade alsa-lib-1.2.4-5.fc34.i686.rpm alsa-lib-1.2.4-5.fc34.x86_64.rpm
[sudo] пароль для aa:
Последняя проверка окончания срока действия метаданных: 0:12:17 назад, Чт 12 авг 2021 13:19:14.
Зависимости разрешены.
======================================================================================================================================================================================================
Пакет Архитектура Версия Репозиторий Размер
======================================================================================================================================================================================================
Откат версии:
alsa-lib i686 1.2.4-5.fc34 @commandline 504 k
alsa-lib x86_64 1.2.4-5.fc34 @commandline 474 k
alsa-ucm noarch 1.2.4-5.fc34 fedora 59 k
alsa-utils x86_64 1.2.4-2.fc34 fedora 1.1 M
Результат транзакции
======================================================================================================================================================================================================
Откат версии 4 Пакета
Общий размер: 2.1 M
Объем загрузки: 1.2 M
Продолжить? [д/Н]: y
Загрузка пакетов:
(1/2): alsa-ucm-1.2.4-5.fc34.noarch.rpm 511 kB/s | 59 kB 00:00
(2/2): alsa-utils-1.2.4-2.fc34.x86_64.rpm 3.0 MB/s | 1.1 MB 00:00
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Общий размер 1.2 MB/s | 1.2 MB 00:00
Проверка транзакции
Проверка транзакции успешно завершена.
Идет проверка транзакции
Тест транзакции проведен успешно.
Выполнение транзакции
Подготовка : 1/1
Откат версии : alsa-lib-1.2.4-5.fc34.x86_64 1/8
Откат версии : alsa-ucm-1.2.4-5.fc34.noarch 2/8
Запуск скриптлета: alsa-utils-1.2.4-2.fc34.x86_64 3/8
Откат версии : alsa-utils-1.2.4-2.fc34.x86_64 3/8
Запуск скриптлета: alsa-utils-1.2.4-2.fc34.x86_64 3/8
Откат версии : alsa-lib-1.2.4-5.fc34.i686 4/8
Запуск скриптлета: alsa-utils-1.2.5.1-1.fc34.x86_64 5/8
Очистка : alsa-utils-1.2.5.1-1.fc34.x86_64 5/8
Запуск скриптлета: alsa-utils-1.2.5.1-1.fc34.x86_64 5/8
Очистка : alsa-ucm-1.2.5.1-1.fc34.noarch 6/8
Очистка : alsa-lib-1.2.5.1-1.fc34.i686 7/8
Очистка : alsa-lib-1.2.5.1-1.fc34.x86_64 8/8
Запуск скриптлета: alsa-lib-1.2.5.1-1.fc34.x86_64 8/8
Проверка : alsa-ucm-1.2.4-5.fc34.noarch 1/8
Проверка : alsa-ucm-1.2.5.1-1.fc34.noarch 2/8
Проверка : alsa-utils-1.2.4-2.fc34.x86_64 3/8
Проверка : alsa-utils-1.2.5.1-1.fc34.x86_64 4/8
Проверка : alsa-lib-1.2.4-5.fc34.i686 5/8
Проверка : alsa-lib-1.2.5.1-1.fc34.i686 6/8
Проверка : alsa-lib-1.2.4-5.fc34.x86_64 7/8
Проверка : alsa-lib-1.2.5.1-1.fc34.x86_64 8/8
Возвращен к предыдущей версии:
alsa-lib-1.2.4-5.fc34.i686 alsa-lib-1.2.4-5.fc34.x86_64 alsa-ucm-1.2.4-5.fc34.noarch alsa-utils-1.2.4-2.fc34.x86_64
Выполнено!
now
systemctl status alsa-state.service
get:
alsa-state.service - Manage Sound Card State (restore and store)
Loaded: loaded (/usr/lib/systemd/system/alsa-state.service; static)
Active: active (running) since Thu 2021-08-12 13:56:37 MSK; 3min 15s ago
Main PID: 761 (alsactl)
Tasks: 1 (limit: 9162)
Memory: 396.0K
CPU: 10ms
CGroup: /system.slice/alsa-state.service
└─761 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main rdaemon
авг 12 13:56:37 xxx alsactl[761]: alsactl 1.2.4 daemon started
авг 12 13:56:37 xxx systemd[1]: Started Manage Sound Card State (restore and store).
--
1. "Volume control" disappears again several times if set card from "Default" to "HDA Intel MID".
2. But if set "Default" card and don't change it, then:
- It change volume in mpv or xawtv, not only by "HDA Intel MID"
- It not zeroed volume between reboots.
- it not disappears
I try to use my pc some more time with "Default" card and see if "Volume control" disappear again at some point or not.
Note that after you downgrade alsa-lib, you have to reboot. Ok. I reboot 6 or 7 times.
First i add volume control after downgrade and before reboot. It's disappear after reboot.
Second i add volume control once more time, but set not default card ("HDA Intel MID" as in comment #20). It's disappear after reboot again.
I try this 2 or 3 times with constant fail to see volume control after reboot.
Then i add volume control & don't change card from "Default" to "HDA Intel MID". At this time volume control works & it don't disappear after reboot.
So, the successful order of operation is:
1. "sudo dnf copr enable mtasaka/lxpanel-bz1960829"
2. "sudo dnf upgrade lxpanel"
3. download alsa-lib-1.2.4-5.fc34.i686.rpm & alsa-lib-1.2.4-5.fc34.x86_64.rpm from https://koji.fedoraproject.org/koji/buildinfo?buildID=1674578
4. downgrade alsa-lib to alsa-lib-1.2.4-5 by "sudo dnf downgrade alsa-lib-1.2.4-5.fc34.i686.rpm alsa-lib-1.2.4-5.fc34.x86_64.rpm"
5. reboot
6. add "Volume Control" to lxpanel, don't change default card.
7. test if volume control works with all needed application
8. reboot & test if "Volume Control" remain on lxpanel.
9. if "Volume Control" disappear, try 6-8 one more time.
it works for me even after update to pipewire-0.3.34-1
this is a
dnf history info 307
log:
...
Код возврата : Успешно
Выпускаемая версия : 34
Команда : update -x alsa-lib-1.2.5-2.fc34,alsa-lib-1.2.5.1-1.fc34,alsa-plugins-1.2.5-1.fc34,alsa-tools-1.2.5-1.fc34,alsa-ucm-1.2.5.1-1.fc34,alsa-utils-1.2.5.1-1.fc34.x86_64,alsa-utils-1.2.5-2.fc34
Комментарий :
Пакеты изменены:
Установка libjxl-0.5-1.fc34.i686 @updates
Исключено jpegxl-libs-0.3.7-3.fc34.x86_64 @@System
Исключено jpegxl-libs-0.3.7-3.fc34.i686 @@System
Установка libjxl-0.5-1.fc34.x86_64 @updates
Upgrade gimp-jxl-plugin-0.5-1.fc34.x86_64 @updates
Upgraded gimp-jxl-plugin-0.3.7-3.fc34.x86_64 @@System
Upgrade jxl-pixbuf-loader-0.5-1.fc34.x86_64 @updates
Upgraded jxl-pixbuf-loader-0.3.7-3.fc34.x86_64 @@System
Upgrade pango-1.48.9-2.fc34.i686 @updates
Upgraded pango-1.48.9-1.fc34.i686 @@System
Upgrade pango-1.48.9-2.fc34.x86_64 @updates
Upgraded pango-1.48.9-1.fc34.x86_64 @@System
Upgrade perl-GSSAPI-0.28-35.fc34.x86_64 @updates
Upgraded perl-GSSAPI-0.28-33.fc34.x86_64 @@System
Upgrade pipewire-0.3.34-1.fc34.x86_64 @updates
Upgraded pipewire-0.3.33-3.fc34.x86_64 @@System
Upgrade pipewire-alsa-0.3.34-1.fc34.x86_64 @updates
Upgraded pipewire-alsa-0.3.33-3.fc34.x86_64 @@System
Upgrade pipewire-gstreamer-0.3.34-1.fc34.x86_64 @updates
Upgraded pipewire-gstreamer-0.3.33-3.fc34.x86_64 @@System
Upgrade pipewire-jack-audio-connection-kit-0.3.34-1.fc34.x86_64 @updates
Upgraded pipewire-jack-audio-connection-kit-0.3.33-3.fc34.x86_64 @@System
Upgrade pipewire-libs-0.3.34-1.fc34.x86_64 @updates
Upgraded pipewire-libs-0.3.33-3.fc34.x86_64 @@System
Upgrade pipewire-pulseaudio-0.3.34-1.fc34.x86_64 @updates
Upgraded pipewire-pulseaudio-0.3.33-3.fc34.x86_64 @@System
Upgrade pipewire-utils-0.3.34-1.fc34.x86_64 @updates
Upgraded pipewire-utils-0.3.33-3.fc34.x86_64 @@System
I use sudo update -x alsa-lib-1.2.5-2.fc34,alsa-lib-1.2.5.1-1.fc34,alsa-plugins-1.2.5-1.fc34,alsa-tools-1.2.5-1.fc34,alsa-ucm-1.2.5.1-1.fc34,alsa-utils-1.2.5.1-1.fc34.x86_64,alsa-utils-1.2.5-2.fc34 for ignoring any updates from alsa-lib-1.2.4 to 1.2.5
(In reply to Mamoru TASAKA from comment #17) > Would you try > $ sudo dnf copr enable mtasaka/lxpanel-bz1960829 > $ sudo dnf upgrade lxpanel > > Then reboot and try to check if this works? Origato, Mamoru! Do you plan to provide your changes in main fedora repo? (I plan to upgrade several notebooks of my friend and his children from fedora 33 to fedora34 and don't want to see this bug on there machines) If you can say you are okay with lxpanel-0.10.1-1.1.fc34 , I can push it to Fedora updates repo. Yes, i am. And yes, push it to Fedora updates repo, please. FEDORA-2021-0b9647a1a3 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-0b9647a1a3 FEDORA-2021-7b6ca57c98 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-7b6ca57c98 FEDORA-2021-0b9647a1a3 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-0b9647a1a3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0b9647a1a3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-7b6ca57c98 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-7b6ca57c98` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-7b6ca57c98 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. I dunno how to update lxpanel without update or downgrade alsa. "sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-0b9647a1a3" try to update alsa-lib and alsa-ucm "sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-0b9647a1a3 -x alsa-lib-1.2.5-2.fc34,alsa-lib-1.2.5.1-1.fc34,alsa-plugins-1.2.5-1.fc34,alsa-tools-1.2.5-1.fc34,alsa-ucm-1.2.5.1-1.fc34,alsa-utils-1.2.5.1-1.fc34.x86_64,alsa-utils-1.2.5-2.fc34" don't work "sudo dnf update --enablerepo=updates-testing --advisory=FEDORA-2021-0b9647a1a3 -x alsa-lib-1.2.5-2.fc34,alsa-lib-1.2.5.1-1.fc34,alsa-plugins-1.2.5-1.fc34,alsa-tools-1.2.5-1.fc34,alsa-ucm-1.2.5.1-1.fc34,alsa-utils-1.2.5.1-1.fc34.x86_64,alsa-utils-1.2.5-2.fc34" don't work too. update from update-testing now lxpanel x86_64 0.10.1-2.fc34 updates-testing 1.3 M "volume control" disappear after reboot. Add it to lxpanel & set "HDA Intel MID" card (not default). It disappear after reboot again. Add it to lxpanel & set default card. After reboot "volume control" is on lxpanel (but in my case audio it works only if set "HDA Intel MID"). If i set not default card "volume control" disappear after reboot. With lxpanel-0.10.1-1.1.fc34 from your repository it somehow works. Created attachment 1822506 [details]
"dnf info xxx" for latest update from update-testing repository
FEDORA-2021-7b6ca57c98 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-0b9647a1a3 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. |
Created attachment 1783507 [details] get this file by command sudo cp /etc/xdg/lxpanel/default/panels/panel etc_xdg_default_panel.$CUR_DATE Description of problem: i use fedora 33 with lxde and add volume applet on lxpanel 0.10.1. it's works. after upgrade from fedora 33 to fedora 34 this applet disappear from panel. If i add it manualy, it disappear after next reboot. I see some typo in /etc/xdg/lxpanel/default/panels/panel allign=left instead of align=left but i don't check if it exist in previous version of fedora. Version-Release number of selected component (if applicable): fedora 34, lxpanel 0.10.1 How reproducible: i see it on 2 computers after upgrade Steps to Reproduce: 1.install fedora 33 with lxde 2.add volume applet on lxpanel 3.reboot 4.check if volume applet not disappear 5.upgrade from fedora 33 to fedora 34 6.volume applet is disappear 7.add volume applet on lxpanel 8.reboot 9.volume applet is disappear Actual results:volume applet is disappear Expected results:volume applet remains visible Additional info: to check if typo exists try sudo cat /etc/xdg/lxpanel/default/panels/panel | grep allign