May 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1220775] Kernel oops on aws M6g.metal
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220775 https://bugzilla.suse.com/show_bug.cgi?id=1220775#c37 --- Comment #37 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2024:1490-1: An update that solves 183 vulnerabilities, contains three features and has 38 security fixes can now be installed. Category: security (important) Bug References: 1177529, 1192145, 1194869, 1200465, 1205316, 1207948, 1209635, 1209657, 1212514, 1213456, 1214852, 1215221, 1215322, 1217339, 1217829, 1217959, 1217987, 1217988, 1217989, 1218321, 1218336, 1218479, 1218643, 1218777, 1219126, 1219169, 1219170, 1219264, 1219834, 1220114, 1220176, 1220237, 1220251, 1220320, 1220337, 1220340, 1220365, 1220366, 1220398, 1220411, 1220413, 1220439, 1220443, 1220445, 1220466, 1220478, 1220482, 1220484, 1220486, 1220487, 1220492, 1220703, 1220775, 1220790, 1220797, 1220831, 1220833, 1220836, 1220839, 1220840, 1220843, 1220870, 1220871, 1220872, 1220878, 1220879, 1220883, 1220885, 1220887, 1220898, 1220901, 1220915, 1220918, 1220920, 1220921, 1220926, 1220927, 1220929, 1220932, 1220935, 1220937, 1220938, 1220940, 1220954, 1220955, 1220959, 1220960, 1220961, 1220965, 1220969, 1220978, 1220979, 1220981, 1220982, 1220983, 1220985, 1220986, 1220987, 1220989, 1220990, 1221009, 1221012, 1221015, 1221022, 1221039, 1221040, 1221044, 1221045, 1221046, 1221048, 1221055, 1221056, 1221058, 1221060, 1221061, 1221062, 1221066, 1221067, 1221068, 1221069, 1221070, 1221071, 1221077, 1221082, 1221090, 1221097, 1221156, 1221162, 1221252, 1221273, 1221274, 1221276, 1221277, 1221291, 1221293, 1221298, 1221337, 1221338, 1221375, 1221379, 1221551, 1221553, 1221613, 1221614, 1221616, 1221618, 1221631, 1221633, 1221713, 1221725, 1221777, 1221791, 1221814, 1221816, 1221830, 1221951, 1222011, 1222033, 1222051, 1222056, 1222060, 1222070, 1222073, 1222117, 1222247, 1222266, 1222274, 1222291, 1222300, 1222304, 1222317, 1222331, 1222355, 1222356, 1222360, 1222366, 1222373, 1222416, 1222422, 1222427, 1222428, 1222431, 1222437, 1222445, 1222449, 1222503, 1222520, 1222536, 1222549, 1222550, 1222557, 1222585, 1222586, 1222596, 1222609, 1222610, 1222619, 1222630, 1222632, 1222660, 1222662, 1222664, 1222669, 1222677, 1222678, 1222680, 1222706, 1222720, 1222724, 1222726, 1222727, 1222764, 1222772, 1222781, 1222784, 1222798, 1222801, 1222952, 1223030, 1223067, 1223068 CVE References: CVE-2021-46925, CVE-2021-46926, CVE-2021-46927, CVE-2021-46929, CVE-2021-46930, CVE-2021-46931, CVE-2021-46933, CVE-2021-46936, CVE-2021-47082, CVE-2021-47087, CVE-2021-47091, CVE-2021-47093, CVE-2021-47094, CVE-2021-47095, CVE-2021-47096, CVE-2021-47097, CVE-2021-47098, CVE-2021-47099, CVE-2021-47100, CVE-2021-47101, CVE-2021-47102, CVE-2021-47104, CVE-2021-47105, CVE-2021-47107, CVE-2021-47108, CVE-2021-47181, CVE-2021-47182, CVE-2021-47183, CVE-2021-47185, CVE-2021-47189, CVE-2022-4744, CVE-2022-48626, CVE-2022-48629, CVE-2022-48630, CVE-2023-0160, CVE-2023-28746, CVE-2023-35827, CVE-2023-4881, CVE-2023-52447, CVE-2023-52450, CVE-2023-52453, CVE-2023-52454, CVE-2023-52469, CVE-2023-52470, CVE-2023-52474, CVE-2023-52476, CVE-2023-52477, CVE-2023-52481, CVE-2023-52484, CVE-2023-52486, CVE-2023-52488, CVE-2023-52492, CVE-2023-52493, CVE-2023-52494, CVE-2023-52497, CVE-2023-52500, CVE-2023-52501, CVE-2023-52502, CVE-2023-52503, CVE-2023-52504, CVE-2023-52507, CVE-2023-52508, CVE-2023-52509, CVE-2023-52510, CVE-2023-52511, CVE-2023-52513, CVE-2023-52515, CVE-2023-52517, CVE-2023-52518, CVE-2023-52519, CVE-2023-52520, CVE-2023-52523, CVE-2023-52524, CVE-2023-52525, CVE-2023-52528, CVE-2023-52529, CVE-2023-52532, CVE-2023-52561, CVE-2023-52563, CVE-2023-52564, CVE-2023-52566, CVE-2023-52567, CVE-2023-52569, CVE-2023-52574, CVE-2023-52575, CVE-2023-52576, CVE-2023-52582, CVE-2023-52583, CVE-2023-52587, CVE-2023-52591, CVE-2023-52594, CVE-2023-52595, CVE-2023-52597, CVE-2023-52598, CVE-2023-52599, CVE-2023-52600, CVE-2023-52601, CVE-2023-52602, CVE-2023-52603, CVE-2023-52604, CVE-2023-52605, CVE-2023-52606, CVE-2023-52607, CVE-2023-52608, CVE-2023-52612, CVE-2023-52615, CVE-2023-52617, CVE-2023-52619, CVE-2023-52621, CVE-2023-52623, CVE-2023-52627, CVE-2023-52628, CVE-2023-52632, CVE-2023-52636, CVE-2023-52637, CVE-2023-52639, CVE-2023-6356, CVE-2023-6535, CVE-2023-6536, CVE-2023-7042, CVE-2023-7192, CVE-2024-0841, CVE-2024-2201, CVE-2024-22099, CVE-2024-23307, CVE-2024-23850, CVE-2024-25739, CVE-2024-25742, CVE-2024-26599, CVE-2024-26600, CVE-2024-26602, CVE-2024-26612, CVE-2024-26614, CVE-2024-26620, CVE-2024-26627, CVE-2024-26629, CVE-2024-26642, CVE-2024-26645, CVE-2024-26646, CVE-2024-26651, CVE-2024-26654, CVE-2024-26659, CVE-2024-26660, CVE-2024-26664, CVE-2024-26667, CVE-2024-26670, CVE-2024-26680, CVE-2024-26681, CVE-2024-26684, CVE-2024-26685, CVE-2024-26689, CVE-2024-26695, CVE-2024-26696, CVE-2024-26697, CVE-2024-26704, CVE-2024-26717, CVE-2024-26718, CVE-2024-26722, CVE-2024-26727, CVE-2024-26733, CVE-2024-26736, CVE-2024-26737, CVE-2024-26743, CVE-2024-26744, CVE-2024-26745, CVE-2024-26747, CVE-2024-26749, CVE-2024-26751, CVE-2024-26754, CVE-2024-26760, CVE-2024-26763, CVE-2024-26766, CVE-2024-26769, CVE-2024-26771, CVE-2024-26776, CVE-2024-26779, CVE-2024-26787, CVE-2024-26790, CVE-2024-26793, CVE-2024-26798, CVE-2024-26805, CVE-2024-26807, CVE-2024-26848 Jira References: PED-5759, PED-7167, PED-7619 Maintenance Incident: [SUSE:Maintenance:33538](https://smelt.suse.de/incident/33538/) Sources used: openSUSE Leap 15.5 (src): kernel-source-azure-5.14.21-150500.33.48.1, kernel-syms-azure-5.14.21-150500.33.48.1 Public Cloud Module 15-SP5 (src): kernel-source-azure-5.14.21-150500.33.48.1, kernel-syms-azure-5.14.21-150500.33.48.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1207948] Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1207948 https://bugzilla.suse.com/show_bug.cgi?id=1207948#c95 --- Comment #95 from Maintenance Automation <maint-coord+maintenance-robot(a)suse.de> --- SUSE-SU-2024:1490-1: An update that solves 183 vulnerabilities, contains three features and has 38 security fixes can now be installed. Category: security (important) Bug References: 1177529, 1192145, 1194869, 1200465, 1205316, 1207948, 1209635, 1209657, 1212514, 1213456, 1214852, 1215221, 1215322, 1217339, 1217829, 1217959, 1217987, 1217988, 1217989, 1218321, 1218336, 1218479, 1218643, 1218777, 1219126, 1219169, 1219170, 1219264, 1219834, 1220114, 1220176, 1220237, 1220251, 1220320, 1220337, 1220340, 1220365, 1220366, 1220398, 1220411, 1220413, 1220439, 1220443, 1220445, 1220466, 1220478, 1220482, 1220484, 1220486, 1220487, 1220492, 1220703, 1220775, 1220790, 1220797, 1220831, 1220833, 1220836, 1220839, 1220840, 1220843, 1220870, 1220871, 1220872, 1220878, 1220879, 1220883, 1220885, 1220887, 1220898, 1220901, 1220915, 1220918, 1220920, 1220921, 1220926, 1220927, 1220929, 1220932, 1220935, 1220937, 1220938, 1220940, 1220954, 1220955, 1220959, 1220960, 1220961, 1220965, 1220969, 1220978, 1220979, 1220981, 1220982, 1220983, 1220985, 1220986, 1220987, 1220989, 1220990, 1221009, 1221012, 1221015, 1221022, 1221039, 1221040, 1221044, 1221045, 1221046, 1221048, 1221055, 1221056, 1221058, 1221060, 1221061, 1221062, 1221066, 1221067, 1221068, 1221069, 1221070, 1221071, 1221077, 1221082, 1221090, 1221097, 1221156, 1221162, 1221252, 1221273, 1221274, 1221276, 1221277, 1221291, 1221293, 1221298, 1221337, 1221338, 1221375, 1221379, 1221551, 1221553, 1221613, 1221614, 1221616, 1221618, 1221631, 1221633, 1221713, 1221725, 1221777, 1221791, 1221814, 1221816, 1221830, 1221951, 1222011, 1222033, 1222051, 1222056, 1222060, 1222070, 1222073, 1222117, 1222247, 1222266, 1222274, 1222291, 1222300, 1222304, 1222317, 1222331, 1222355, 1222356, 1222360, 1222366, 1222373, 1222416, 1222422, 1222427, 1222428, 1222431, 1222437, 1222445, 1222449, 1222503, 1222520, 1222536, 1222549, 1222550, 1222557, 1222585, 1222586, 1222596, 1222609, 1222610, 1222619, 1222630, 1222632, 1222660, 1222662, 1222664, 1222669, 1222677, 1222678, 1222680, 1222706, 1222720, 1222724, 1222726, 1222727, 1222764, 1222772, 1222781, 1222784, 1222798, 1222801, 1222952, 1223030, 1223067, 1223068 CVE References: CVE-2021-46925, CVE-2021-46926, CVE-2021-46927, CVE-2021-46929, CVE-2021-46930, CVE-2021-46931, CVE-2021-46933, CVE-2021-46936, CVE-2021-47082, CVE-2021-47087, CVE-2021-47091, CVE-2021-47093, CVE-2021-47094, CVE-2021-47095, CVE-2021-47096, CVE-2021-47097, CVE-2021-47098, CVE-2021-47099, CVE-2021-47100, CVE-2021-47101, CVE-2021-47102, CVE-2021-47104, CVE-2021-47105, CVE-2021-47107, CVE-2021-47108, CVE-2021-47181, CVE-2021-47182, CVE-2021-47183, CVE-2021-47185, CVE-2021-47189, CVE-2022-4744, CVE-2022-48626, CVE-2022-48629, CVE-2022-48630, CVE-2023-0160, CVE-2023-28746, CVE-2023-35827, CVE-2023-4881, CVE-2023-52447, CVE-2023-52450, CVE-2023-52453, CVE-2023-52454, CVE-2023-52469, CVE-2023-52470, CVE-2023-52474, CVE-2023-52476, CVE-2023-52477, CVE-2023-52481, CVE-2023-52484, CVE-2023-52486, CVE-2023-52488, CVE-2023-52492, CVE-2023-52493, CVE-2023-52494, CVE-2023-52497, CVE-2023-52500, CVE-2023-52501, CVE-2023-52502, CVE-2023-52503, CVE-2023-52504, CVE-2023-52507, CVE-2023-52508, CVE-2023-52509, CVE-2023-52510, CVE-2023-52511, CVE-2023-52513, CVE-2023-52515, CVE-2023-52517, CVE-2023-52518, CVE-2023-52519, CVE-2023-52520, CVE-2023-52523, CVE-2023-52524, CVE-2023-52525, CVE-2023-52528, CVE-2023-52529, CVE-2023-52532, CVE-2023-52561, CVE-2023-52563, CVE-2023-52564, CVE-2023-52566, CVE-2023-52567, CVE-2023-52569, CVE-2023-52574, CVE-2023-52575, CVE-2023-52576, CVE-2023-52582, CVE-2023-52583, CVE-2023-52587, CVE-2023-52591, CVE-2023-52594, CVE-2023-52595, CVE-2023-52597, CVE-2023-52598, CVE-2023-52599, CVE-2023-52600, CVE-2023-52601, CVE-2023-52602, CVE-2023-52603, CVE-2023-52604, CVE-2023-52605, CVE-2023-52606, CVE-2023-52607, CVE-2023-52608, CVE-2023-52612, CVE-2023-52615, CVE-2023-52617, CVE-2023-52619, CVE-2023-52621, CVE-2023-52623, CVE-2023-52627, CVE-2023-52628, CVE-2023-52632, CVE-2023-52636, CVE-2023-52637, CVE-2023-52639, CVE-2023-6356, CVE-2023-6535, CVE-2023-6536, CVE-2023-7042, CVE-2023-7192, CVE-2024-0841, CVE-2024-2201, CVE-2024-22099, CVE-2024-23307, CVE-2024-23850, CVE-2024-25739, CVE-2024-25742, CVE-2024-26599, CVE-2024-26600, CVE-2024-26602, CVE-2024-26612, CVE-2024-26614, CVE-2024-26620, CVE-2024-26627, CVE-2024-26629, CVE-2024-26642, CVE-2024-26645, CVE-2024-26646, CVE-2024-26651, CVE-2024-26654, CVE-2024-26659, CVE-2024-26660, CVE-2024-26664, CVE-2024-26667, CVE-2024-26670, CVE-2024-26680, CVE-2024-26681, CVE-2024-26684, CVE-2024-26685, CVE-2024-26689, CVE-2024-26695, CVE-2024-26696, CVE-2024-26697, CVE-2024-26704, CVE-2024-26717, CVE-2024-26718, CVE-2024-26722, CVE-2024-26727, CVE-2024-26733, CVE-2024-26736, CVE-2024-26737, CVE-2024-26743, CVE-2024-26744, CVE-2024-26745, CVE-2024-26747, CVE-2024-26749, CVE-2024-26751, CVE-2024-26754, CVE-2024-26760, CVE-2024-26763, CVE-2024-26766, CVE-2024-26769, CVE-2024-26771, CVE-2024-26776, CVE-2024-26779, CVE-2024-26787, CVE-2024-26790, CVE-2024-26793, CVE-2024-26798, CVE-2024-26805, CVE-2024-26807, CVE-2024-26848 Jira References: PED-5759, PED-7167, PED-7619 Maintenance Incident: [SUSE:Maintenance:33538](https://smelt.suse.de/incident/33538/) Sources used: openSUSE Leap 15.5 (src): kernel-source-azure-5.14.21-150500.33.48.1, kernel-syms-azure-5.14.21-150500.33.48.1 Public Cloud Module 15-SP5 (src): kernel-source-azure-5.14.21-150500.33.48.1, kernel-syms-azure-5.14.21-150500.33.48.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1198817] Firefox 99 and Thunderbird 91 unusable (extremly slow) without a IPv6 network
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1198817 https://bugzilla.suse.com/show_bug.cgi?id=1198817#c8 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE CC| |Andreas.Stieger(a)gmx.de --- Comment #8 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Upstream bug closed due to insufficient information. It has been two years, let’s assume this is either gone or no longer relevant -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1213574] New: Thunderbird OAUTH2 broken
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213574 Bug ID: 1213574 Summary: Thunderbird OAUTH2 broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Firefox Assignee: factory-mozilla(a)lists.opensuse.org Reporter: aaron.w2(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Recent Thunderbird updates broke OAUTH2 and this seems to be a common problem with Thunderbird 102. With this update it no longer presents an OAUTH2 dialog for IMAP. My employer uses Microsoft Office365 and OAUTH2 is essential. This used to work. Even with a clean install and nuking the previous configuration it will never prompt for OAUTH2 authentication like it used to. Note that the OAUTH2 dialog DOES work with SMTP, but not IMAP. Searching the Internet reveals that this is a common problem with this release. Please upgrade Thunderbird to a newer release for 15.4. I'm not quite ready to upgrade to 15.5 just yet since I use this machine for heavy development work. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1221883] Dependency resolution failure during update
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221883 https://bugzilla.suse.com/show_bug.cgi?id=1221883#c7 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Flags|needinfo?(jechojekov@gmail. | |com) | Status|NEW |RESOLVED CC| |Andreas.Stieger(a)gmx.de --- Comment #7 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- closing as this was resolved by user action -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1217704] ovmf: reproducible builds problem in ovmf-riscv64-code.bin
by bugzilla_noreply＠suse.com 03 May '24

03 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217704 https://bugzilla.suse.com/show_bug.cgi?id=1217704#c13 Joey Lee <jlee(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo? | --- Comment #13 from Joey Lee <jlee(a)suse.com> --- (In reply to Joey Lee from comment #11) > (In reply to Bernhard Wiedemann from comment #10) > > OBS already sets SOURCE_DATE_EPOCH for Leap/SLE-15 and later to the last > > date in .changes, so do not need to do anything in the .spec. > > Thanks! I have sent change to openSUSE:Factory/ovmf. The ovmf-EmbeddedPkg-Library-Support-SOURCE_DATE_EPOCH-in-Vir.patch be merged to factory. I am still waiting upstream for reviewing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1215663] # CONFIG_SCHED_AUTOGROUP is not set causes Fossilize INFO: Autogroup scheduling is not enabled on this kernel. Will rely entirely on nice().
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1215663 https://bugzilla.suse.com/show_bug.cgi?id=1215663#c5 Michal Koutný <mkoutny(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkoutny(a)suse.com, | |vvedomil(a)protonmail.com Flags| |needinfo?(vvedomil@protonma | |il.com) --- Comment #5 from Michal Koutný <mkoutny(a)suse.com> --- (In reply to Vědomil Vildomec from comment #0) > Could I ask to change that? Change config, build a kernel with > CONFIG_SCHED_AUTOGROUP=y, and make the OpenSUSE kernel and the whole distro > more friendly to gaming through Steam. I'd suggest digging deeper for possible causes of the issue. Can you quantify the friendliness in comparison with basic enablement of CPU controller? [1] Or roughly describe what's the expected behavior? Would autogroup be needed nowadays at all? SCHED_AUTOGROUP was poorly justified feature (already in 2010) that can be realized purely in userspace by creating respective groups manually (or implicitly e.g. via PAM as would happen with pam_systemd when CPU controller is enabled). Don't let me start on combination of autogroups and regular groups (consider containers) in one system. I admit, I'm not a fan of enabling this config today. [1] E.g. override /usr/lib/systemd/system/user@.service.d/20-defaults-SUSE.conf with > cat >/etc/systemd/system/user@.service.d/60-cpu-delegation.conf <<EOD > [Service] > Delegate=cpu > EOD -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1211012] helix editor not properly packaged?
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211012 https://bugzilla.suse.com/show_bug.cgi?id=1211012#c6 --- Comment #6 from Soc Virnyl Estela <uncomfy+openbuildservice(a)uncomfyhalomacro.pl> --- i was expecting the latest fix was merged. is there a reason why it got revoked? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1223618] New: Retroarch missing fonts and icons
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223618 Bug ID: 1223618 Summary: Retroarch missing fonts and icons Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: frtherien(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 874612 --> https://bugzilla.suse.com/attachment.cgi?id=874612&action=edit Screenshot I've just installed Retroarch on OpenSUSE Tumbleweed, a mostly fresh install of the OS. Text appears in a pixel-type font, and all icons are replaced by a black box. It seems like it is missing assets, or a similar issue. I have attached a screenshot. Here is the output from starting `retroarch --verbose`: [INFO] [Config]: Looking for config in: "/home/francis/.config/retroarch/retroarch.cfg". [INFO] === Build ======================================= [INFO] CPU Model Name: Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz [INFO] Capabilities: MMX MMXEXT SSE SSE2 SSE3 SSSE3 SSE4 SSE42 AES AVX AVX2 [INFO] Version: 1.18.0 [INFO] Built: Mar 23 2024 [INFO] ================================================= [INFO] [Input]: Found input driver: "x". [INFO] [Environ]: SET_PIXEL_FORMAT: RGB565. [INFO] [Core]: Version of libretro API: 1, Compiled against API: 1 [INFO] [Core]: Geometry: 320x240, Aspect: 1.333, FPS: 60.00, Sample rate: 48000.00 Hz. [INFO] [Audio]: Set audio input rate to: 48000.00 Hz. [INFO] [Video]: Set video size to: 960x720. [ERROR] [Wayland]: Failed to connect to Wayland server. [INFO] [GLX]: GLX_EXT_swap_control_tear supported. [INFO] [GL]: Found GL context: "x". [INFO] [GL]: Detecting screen resolution: 1920x1080. [INFO] [GLX]: X = 0, Y = 0, W = 960, H = 720. [INFO] [GLX]: Found swap function: glXSwapIntervalEXT. [INFO] [GL]: Vendor: Intel, Renderer: Mesa Intel(R) HD Graphics 4400 (HSW GT2). [INFO] [GL]: Version: 4.6 (Compatibility Profile) Mesa 24.0.5. [INFO] [GL]: Using resolution 960x720. [INFO] [GL]: Default shader backend found: glsl. [INFO] [Shader driver]: Using GLSL shader backend. [INFO] [GLSL]: Checking GLSL shader support ... [WARN] [GL]: Stock GLSL shaders will be used. [INFO] [GLSL]: Found GLSL vertex shader. [INFO] [GLSL]: Found GLSL fragment shader. [INFO] [GLSL]: Linking GLSL program. [INFO] [GLSL]: Found GLSL vertex shader. [INFO] [GLSL]: Found GLSL fragment shader. [INFO] [GLSL]: Linking GLSL program. [INFO] [GLSL]: Found GLSL vertex shader. [INFO] [GLSL]: Found GLSL fragment shader. [INFO] [GLSL]: Linking GLSL program. [INFO] [GL]: Using 4 textures. [INFO] [GL]: Loaded 1 program(s). [INFO] [GL]: Using GL_RGB565 for texture uploads. [INFO] [Joypad]: Found joypad driver: "udev". [INFO] [DBus]: Suspended screensaver via DBus. [INFO] [Video]: Found display server: "x11". [INFO] [PulseAudio]: Requested 24576 bytes buffer, got 18432. [INFO] [Audio]: Started synchronous audio driver. [INFO] [ALSA] Using ALSA version 1.2.11 [INFO] [Microphone]: Initialized microphone driver. [INFO] [Display]: Found display driver: "gl". [INFO] [Playlist]: Loading history file: "/home/francis/.config/retroarch/content_history.lpl". [INFO] [Playlist]: Loading history file: "/home/francis/.config/retroarch/content_music_history.lpl". [INFO] [Playlist]: Loading history file: "/home/francis/.config/retroarch/content_video_history.lpl". [INFO] [Playlist]: Loading history file: "/home/francis/.config/retroarch/content_image_history.lpl". [INFO] [Playlist]: Loading favorites file: "/home/francis/.config/retroarch/content_favorites.lpl". -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1223773] zypper does not accept option: break <package> by ignoring some of its dependencies
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1223773 https://bugzilla.suse.com/show_bug.cgi?id=1223773#c1 Michael Andres <ma(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gcomes.obs(a)gmail.com Flags| |needinfo?(gcomes.obs@gmail. | |com) --- Comment #1 from Michael Andres <ma(a)suse.com> --- @Giacomo, please create a solver testcase: > zypper in --debug-solver musescore Then pack the testcase directory together with the /var/log/zypper.log and attach it to the bugreport: > cd /tmp > tar cvjf zypper-testcase.bz2 /var/log/zypper.solverTestCase /var/log/zypper.log In case the testcase exceeds the 10MB limit for bugzilla uploads, you can use 'split' to divide the file into smaller pieces: > cd /tmp > split -b 10M --additional-suffix=-zypper-testcase.bz2 zypper-testcase.bz2 The created pieces will be named: xaa-zypper-testcase.bz2 xab-zypper-testcase.bz2 xac-... -- You are receiving this mail because: You are on the CC list for the bug.

1 0