January 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1219070] Chromium won't play youtube videos
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219070 https://bugzilla.suse.com/show_bug.cgi?id=1219070#c7 --- Comment #7 from Avu Zel <avuzel(a)gmail.com> --- @Jan Engelhardt avc1.64002a (299) / mp4a.40.2 (140) works (Live stream) even in youtube. This could be pointing to opus processing library (or handling). Mplayer plays the file just fine, gstreamer based totem too. I checked, audio is opus-encoded. Surprisingly video codec is called VP9 though no transcoding has happened. Hope that helps. ok, investigated a bit further: avc1 is only shown as soon as the black "error" screen appears. During the time, when the preview picture is shown with the start button, VP9 is shown as codec. As soon as it changes to black error screen, it switches to avc1. This could mean the original stream is VP9/opus encoded and would explain why the file contains VP9 streams. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219070] Chromium won't play youtube videos
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219070 https://bugzilla.suse.com/show_bug.cgi?id=1219070#c6 --- Comment #6 from Avu Zel <avuzel(a)gmail.com> --- @Jan Engelhardt avc1.64002a (299) / mp4a.40.2 (140) works (Live stream) even in youtube. This could be pointing to opus processing library (or handling). Mplayer plays the file just fine, gstreamer based totem too. I checked, audio is opus-encoded. Surprisingly video codec is called VP9 though no transcoding has happened. Hope that helps. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219070] Chromium won't play youtube videos
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219070 https://bugzilla.suse.com/show_bug.cgi?id=1219070#c5 Jan Engelhardt <jengelh(a)inai.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jengelh(a)inai.de --- Comment #5 from Jan Engelhardt <jengelh(a)inai.de> --- Just to rule out issue... if you use yt-dlp to grab the file from youtube (use -F/-f to pick the right formats) and attempt to play it with ffplay or mplayer, does it succeed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1210959] Modula-2 compiler doesn’t compile
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1210959 https://bugzilla.suse.com/show_bug.cgi?id=1210959#c3 --- Comment #3 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1210959) was mentioned in https://build.opensuse.org/request/show/1141180 Factory / gcc13 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219031] Multiple cross-arm-none-gcc13 bugs
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219031 https://bugzilla.suse.com/show_bug.cgi?id=1219031#c6 --- Comment #6 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1219031) was mentioned in https://build.opensuse.org/request/show/1141180 Factory / gcc13 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219019] Nitrokey app 1.4.2 app (for Nitrokey 1 and 2) is not functional under Wayland
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219019 https://bugzilla.suse.com/show_bug.cgi?id=1219019#c2 --- Comment #2 from Stakanov Schufter <stakanov(a)disroot.org> --- (In reply to Santiago Zarate from comment #1) > Out of curiosity, how are you installing Nitrokey app? > > I was having trouble even starting it some time ago - > https://github.com/Nitrokey/nitrokey-app2/issues/67 > > (In reply to Stakanov Schufter from comment #0) > > Nitrokey app is a 35d party software provided by the producer Nitrokey. > > Its function should be as follows: > > app is resident in the tray > > insertion of the key triggers app to give notice "key connected" > > once you unlock the secure password and/or an TOTP key, this is temporarily > > copied into the clipboard, hence you can paste it into the respective > > application. > > > > Hence the core function of the app is, to provide the TOTP or password to > > the clipboard and make it available. > > > > Now under X-server sessions this works flawlessly, but to my dismay I > > discovered that it is broken under Wayland. While the generation of the > > TOTP/OTP and the availability of the passwords are given in Wayland, there > > seems to be no way to have them transferred to the clipboard, which remains > > blanc and hence the functionality is broken. I signed this as major because > > it breaks the function of the app itself and there is a potential damage to > > the user. Imagine you are in the middle of e.g. buying a ticket / time > > limited offer and you have to unlock the catch by payment now. Unfortunately > > you are under Wayland, so you will find out that e.g. you cannot pay. This I > > find it to be a major issue as it can cause financial loss to the user. > > Because in order to work around you have to logout the session and login the > > session as X, but now your offer/ticket etc is gone. (A lot of users I > > suppose use Wayland as default on laptops now). > > > > A further danger I see with this is, that we are talking of shifting to > > Wayland as default and that X-server is somewhat deprecated now. So a > > security conscious user may well find himself sitting on the fence to choose > > between using less safe X doing business, not to speak of maybe soon, not > > being able to use the key at all, because no X-session is available any > > more(although this is probably still to come in future editions of TW > > but...better to fix it as soon as possible). > > > > Steps to follow: > > wayland KDE Plasma session with the app2 > > insert key > > unlock password > > tell to copy to clipboard > > clipboard remains blanc > > > > counter proof: log into the X-session version and it works. activate the "security" repo in Tumbleweed. Install the rpm done. The 1.4.2 app works flawlessly under TW as long as you use X-server. It technically works in Plasma/Wayland but you are currently not able to copy it to the clipboard. You get no errors though. While the 1.4.2 can run in the tray, the follower app nitrokey app2 can currently not run in the tray, has no icon and you have to start it with nitrokeyapp as a command in terminal (as opposed to nitrokey-app for the first version when you start it from terminal). Hope that answers your question. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219129] Nitrokey 2.1.2 app does not reduce to tray
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219129 Santiago Zarate <santiago.zarate(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1219019 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219019] Nitrokey app 1.4.2 app (for Nitrokey 1 and 2) is not functional under Wayland
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219019 Santiago Zarate <santiago.zarate(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.suse.com/s | |how_bug.cgi?id=1219129 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1218848] Unable to install wine in slowroll fresh install.
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1218848 https://bugzilla.suse.com/show_bug.cgi?id=1218848#c2 Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #2 from Bernhard Wiedemann <bwiedemann(a)suse.com> --- Publishing was broken from an unrelated issue. wine-32bit-9.0~rc3-5.10 reached download.opensuse.org on 2024-01-22 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1219019] Nitrokey app 1.4.2 app (for Nitrokey 1 and 2) is not functional under Wayland
by bugzilla_noreply＠suse.com 24 Jan '24

24 Jan '24

https://bugzilla.suse.com/show_bug.cgi?id=1219019 https://bugzilla.suse.com/show_bug.cgi?id=1219019#c1 Santiago Zarate <santiago.zarate(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |santiago.zarate(a)suse.com --- Comment #1 from Santiago Zarate <santiago.zarate(a)suse.com> --- Out of curiosity, how are you installing Nitrokey app? I was having trouble even starting it some time ago - https://github.com/Nitrokey/nitrokey-app2/issues/67 (In reply to Stakanov Schufter from comment #0) > Nitrokey app is a 35d party software provided by the producer Nitrokey. > Its function should be as follows: > app is resident in the tray > insertion of the key triggers app to give notice "key connected" > once you unlock the secure password and/or an TOTP key, this is temporarily > copied into the clipboard, hence you can paste it into the respective > application. > > Hence the core function of the app is, to provide the TOTP or password to > the clipboard and make it available. > > Now under X-server sessions this works flawlessly, but to my dismay I > discovered that it is broken under Wayland. While the generation of the > TOTP/OTP and the availability of the passwords are given in Wayland, there > seems to be no way to have them transferred to the clipboard, which remains > blanc and hence the functionality is broken. I signed this as major because > it breaks the function of the app itself and there is a potential damage to > the user. Imagine you are in the middle of e.g. buying a ticket / time > limited offer and you have to unlock the catch by payment now. Unfortunately > you are under Wayland, so you will find out that e.g. you cannot pay. This I > find it to be a major issue as it can cause financial loss to the user. > Because in order to work around you have to logout the session and login the > session as X, but now your offer/ticket etc is gone. (A lot of users I > suppose use Wayland as default on laptops now). > > A further danger I see with this is, that we are talking of shifting to > Wayland as default and that X-server is somewhat deprecated now. So a > security conscious user may well find himself sitting on the fence to choose > between using less safe X doing business, not to speak of maybe soon, not > being able to use the key at all, because no X-session is available any > more(although this is probably still to come in future editions of TW > but...better to fix it as soon as possible). > > Steps to follow: > wayland KDE Plasma session with the app2 > insert key > unlock password > tell to copy to clipboard > clipboard remains blanc > > counter proof: log into the X-session version and it works. -- You are receiving this mail because: You are on the CC list for the bug.

1 0