January 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1172891] New: autopatch breaks patches in linked patch
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1172891 Bug ID: 1172891 Summary: autopatch breaks patches in linked patch Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cornelis(a)solcon.nl QA Contact: adrian.schroeter(a)suse.com Found By: --- Blocker: --- In the buildservice when a package is linked a file "_link" is created with the content: <link project="Projectname" package="Packagename"> <patches>      </patches> </link> When I use "<add name='File.patch" />" to add a patch to my branch, a line is created in the spec like "%patch1" after %setup. This works fine except when the orginal spec file uses %autopatch. The line "%patch1" is still created, but this then means that during build the patch is applied two time, which gives an error. When %autopatch is use no additional line should be added after setup. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1193631] New: blender 3.0 update issue
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1193631 Bug ID: 1193631 Summary: blender 3.0 update issue Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: cornelis(a)solcon.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since blender's update to 3.0.0 zypper dup in TW gives the error that blender-lang and blender-demo do not have the right version needed for blender-3.0.0. The 3.0.0 version of these noarch packages are not available. The reason is probably that the i586 builds fail. The 3.0.0 version is available in the web interface of the buildservice, maar not synced to the downloads. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1192292] wine dlls contain mostly debug info
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192292 http://bugzilla.opensuse.org/show_bug.cgi?id=1192292#c11 --- Comment #11 from Alexei Sorokin <sor.alexei(a)meowr.ru> --- I reposted it here: https://build.opensuse.org/request/show/943296 , after I realised that the breaking change was an earlier request that got accepted into openSUSE:Factory already. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192292] wine dlls contain mostly debug info
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1192292 http://bugzilla.opensuse.org/show_bug.cgi?id=1192292#c10 Fabian Vogt <fabian(a)ritter-vogt.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fabian(a)ritter-vogt.de, | |sor.alexei(a)meowr.ru --- Comment #10 from Fabian Vogt <fabian(a)ritter-vogt.de> --- (In reply to OBSbugzilla Bot from comment #9) > This is an autogenerated message for OBS integration: > This bug (1192292) was mentioned in > https://build.opensuse.org/request/show/943297 Factory / wine XRevan86 commented on sr 943623 that wine is totally broken (but apparently deleted the comment, it's not visible in the Web UI anymore). FWICT, this is caused by this change, because i686-w64-mingw32-strip/x86_64-w64-mingw32-strip rewrite the DOS header without preserving the "Wine builtin DLL"/"Wine placeholder DLL" marker. For some reason this is preserved properly by plain "strip", which is why it worked in my testing. The output is pretty much identical otherwise (single byte differences in the section table?). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192751] Regression: suse-prime's nvidia mode broken since xorg-server 21.1.x
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1192751 https://bugzilla.suse.com/show_bug.cgi?id=1192751#c36 --- Comment #36 from Stefan Dirsch <sndirsch(a)suse.com> --- Meanwhile I've added the patch from https://gitlab.freedesktop.org/xorg/xserver/-/issues/1254#note_1205673 https://gitlab.freedesktop.org/xorg/xserver/uploads/2cd40ad0605a0a0855a0836… to https://build.opensuse.org/package/show/X11:XOrg/xorg-x11-server but I haven't tested it yet. Maybe somebody else affected could .... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194099] Sound using headphones does not work after update yesterday.
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194099 https://bugzilla.suse.com/show_bug.cgi?id=1194099#c5 --- Comment #5 from Alex Grasic <alexgrasic(a)gmail.com> --- 70 updates were installed, unless there is a logfile somewhere, I have no way of telling you which updates were installed. How do you switch to an older kernel? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194099] Sound using headphones does not work after update yesterday.
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194099 https://bugzilla.suse.com/show_bug.cgi?id=1194099#c4 --- Comment #4 from Alex Grasic <alexgrasic(a)gmail.com> --- Created attachment 854924 --> https://bugzilla.suse.com/attachment.cgi?id=854924&action=edit Alsa info unbroken state (headphone jack not in use) Alsa info unbroken state (headphone jack not in use) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1194099] Sound using headphones does not work after update yesterday.
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1194099 https://bugzilla.suse.com/show_bug.cgi?id=1194099#c3 --- Comment #3 from Alex Grasic <alexgrasic(a)gmail.com> --- Created attachment 854923 --> https://bugzilla.suse.com/attachment.cgi?id=854923&action=edit Alsa-info broken state Alsa from broken state -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1188970 https://bugzilla.suse.com/show_bug.cgi?id=1188970#c115 --- Comment #115 from Stefan Dirsch <sndirsch(a)suse.com> --- So it's a USB monitor with displaylink builtin. OMG. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1132926] Intel i915 graphics driver issues with external monitor when laptop in docking station
by bugzilla_noreply＠suse.com 03 Jan '22

03 Jan '22

https://bugzilla.suse.com/show_bug.cgi?id=1132926 https://bugzilla.suse.com/show_bug.cgi?id=1132926#c39 --- Comment #39 from Otrebor Igorig <otrebor(a)hispeed.ch> --- I now have upgraded the system to Leap 15.3 with Kernel 5.3.18-59.37-default. The behavior is different now. Better from a users perspective, but still not where I would expect it to be. I'm now able to initialize the external monitor and get it to work. However, this only works in a usable manner, when making the monitor a display mirror of the internal one with the very same resolution in place (1920x1080). Using any other resolution or making the external monitor a virtual screen extension does not work in any usable way. Also, the KDE screen config utility gets confused about the state of the monitor. When it *is* working, it reports it as disabled and vice versa. So, I need multiple attempts when activating it, to use it as a mirrored screen in the end. So I'm only doing it when I *really* do need it, which is less now as it used to be. I've also guessed, that it may have something to do, that the graphics chipset is rather old by now. But occasionally the monitor is able to display its full 4k resolution with the internal one being at 1920x1080, rarely though. btw. I've changed employer in the meantime. They handed me a MacBook Pro which is using the same monitor via a USB bridge and HDMI. The monitor works as expected. So it really *is* a driver issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 0