June 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1009637] New: games/ufoai: Game crashes with "Error: Received signal 11."
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1009637 Bug ID: 1009637 Summary: games/ufoai: Game crashes with "Error: Received signal 11." Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: dimstar(a)opensuse.org Reporter: bberberov+suse(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- UFO:AI consistently crashes now. This started occurring a couple of months ago, but I don't know which is the last working version. Steps to reproduce: - Start UFO:AI - Select "Single-Player" - Select "Skirmish" - Choose a map and "Start Game", I tested with the africa_small and a few others. The game loads, and the screen announcing the map and "Victory Conditions" shows up. You can move the map in the background and it renders fine with no errors or crashes with multiple graphics configurations. One the Start button is pressed it crashes after a couple of seconds. This is output from the console========== Starting the game... bberberov has joined team 1 Used inventory slots: 0 libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile Not enough spawn points for team 1 (actorsize: 1) Not enough spawn points for team 1 (actorsize: 1) Not enough spawn points for team 1 (actorsize: 1) Not enough spawn points for team 1 (actorsize: 1) Used inventory slots client bberberov spawn: 0 (player 0) It's team 1's turn! bberberov has taken control over team 1. Error: Received signal 11. ============================================= Don't know how to debug this, but I'd like to help, and finish my game in progress. :-) -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1050953] New: systemsetting5 -> Account Details does not give the option suggested in the title
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1050953 Bug ID: 1050953 Summary: systemsetting5 -> Account Details does not give the option suggested in the title Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 734130 --> http://bugzilla.opensuse.org/attachment.cgi?id=734130&action=edit screenshot of application Starting systemsetting5 and choosing Account Details -> User Manager shows the title: Add, remove or edit system users. However the only option it shows is New User. Editing a current user is impossible/not shown. See attached picture. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1074139] New: Using YaST to configure hardware sound looses information
by bugzilla_noreply＠novell.com 15 Apr '21

15 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1074139 Bug ID: 1074139 Summary: Using YaST to configure hardware sound looses information Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: freek(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Using YaST->hardware->Sound I configure one of the two sound devices: RV770 HDMI Audio [Radeon HD 4850/4870] First I delete the configuration, then I Edit the configuration and use the default Fast automatic configuration. I use Other and Volume to set/check the volume settings, which is quite a busy window with sliders. OK to exit. Start the Sound module in YaST again. Select the above device. In Other select Volume, which does not show the busy window anymore. Only at the top Master volume and a Test button. I assume this is a bug, not showing the sliders to set values. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1068469] New: package spamassassin contains obsolete file README.SuSE
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1068469 Bug ID: 1068469 Summary: package spamassassin contains obsolete file README.SuSE Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, Following a conversation in <https://lists.opensuse.org/opensuse-factory/2017-11/msg00346.html> about «Bulk renaming of "README.SuSE"», it was suggested to search for README.SuSE files in the distribution, find if the contents are valid or obsolete, and then suggest action to the package maintainer in a corresponding bugzilla. The package spamassassin-3.4.1-54.2.x86_64.rpmcontains an obsolete README.SuSE, as it applies to a Sys V init system, so in my opinion it should be simply removed. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1004453] New: [mga] no Xorg with Matrox gfxcard when valid vga= mode included on kernel cmdline to produce desirable vttys
by bugzilla_noreply＠novell.com 03 Apr '21

03 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1004453 Bug ID: 1004453 Summary: [mga] no Xorg with Matrox gfxcard when valid vga= mode included on kernel cmdline to produce desirable vttys Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: mrmazda(a)earthlink.net QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com CC: eich(a)suse.com Found By: --- Blocker: --- Created attachment 697145 --> http://bugzilla.opensuse.org/attachment.cgi?id=697145&action=edit Xorg.0.log from i586 TW host a-865 Mailing list thread starter: https://lists.opensuse.org/opensuse/2016-08/msg00322.html (same with kernels 4.7.x as with kernel 4.6.4) : # Xorg.0.log excerpts X.Org X Server 1.18.4 [ 57.691] Current Operating System: Linux a-865 4.7.4-1-default #1 SMP Thu Sep 15 09:03:59 UTC 2016 (6a5bbb1) i686 [ 57.691] Kernel command line: root=LABEL=os133SS25 ipv6.disable=1 net.ifnames=0 noresume splash=0 vga=791 video=1024x768@60 3 [ 58.342] (EE) open /dev/dri/card0: No such file or directory [ 58.382] (EE) MGA(0): Unable to map Framebuffer F0000000 2000000. Invalid argument (22) [ 58.382] (EE) MGA(0): Unable to detect video RAM. [ 58.382] (EE) Screen(s) found, but none have a usable configuration. [ 58.383] (EE) [ 58.383] (EE) no screens found(EE)... I didn't update this installation for many months, which explains large gap between installed kernels. Xorg and vttys work as expected with kernel-pae 4.2.3 and vga=791 on cmdline, but vga= needs to be omitted with the newer kernels for Xorg to start. Omitting vga= from cmdline results in far too few columns and rows on the vttys. I looked on bugs.freedesktop.org but found nothing like this. I tried a fresh zypper up, but kernel-default 4.7.6 with vga=788 proved no better, as did kernel-vanilla. Also didn't help adding to xorg.conf device section either VideoRam 16384 and/or Option "OldDmaInit" "On". # zypper se -si | egrep 'x11-serv|mga|kernel' il | kernel-default | package | 4.7.4-1.1 | i586 | (System Packages) il | kernel-default | package | 4.6.4-2.2 | i586 | (System Packages) il | kernel-default | package | 4.7.6-1.1 | i586 | OSS i | kernel-firmware | package | 20160913-1.1 | noarch | OSS il | kernel-pae | package | 4.2.3-1.4 | i686 | (System Packages) i | kernel-vanilla | package | 4.7.6-1.1 | i686 | OSS i | nfs-kernel-server | package | 1.3.4-2.2 | i586 | OSS i | xf86-video-mga | package | 1.6.4-2.2 | i586 | OSS i | xorg-x11-server | package | 7.6_1.18.4-1.2 | i586 | OSS # lspci | grep VGA 01:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. Millennium G550 (rev 01) -- You are receiving this mail because: You are on the CC list for the bug.

2 55

[Bug 911401] New: Wrong yast language when multiple languages specified in LANGUAGE env variable
by bugzilla_noreply＠novell.com 29 Mar '21

29 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=911401 Bug ID: 911401 Summary: Wrong yast language when multiple languages specified in LANGUAGE env variable Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: PVince81(a)yahoo.fr QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Steps to reproduce: 1. Make sure that neither LANG nor any LC_* variables are set 2. Run: export LANGUAGE="en_US:de:fr" (or set this language order in KDE's language settings) 3. Run: kdesu yast2 Expected result: Since English is the first language, Yast2 should be in English. Actual result: Yast2 is in German! More info: If you do: - export LANGUAGE="en_US" - kdesu yast2 Yast2 will be in English. It seems zypper is also affected partially. When LANGUAGE="en_US:de:fr" then zypper is in English, but the confirmation prompt is in German: Overall download size: 682.1 MiB. Already cached: 0 B After the operation, additional 753.3 MiB will be used. Fortfahren? [j/n/? zeigt alle Optionen] (j): Could be a duplicate of https://bugzilla.opensuse.org/show_bug.cgi?id=843573 but that one didn't have any details. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1028018] New: Updating postfix gives chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory
by bugzilla_noreply＠novell.com 29 Mar '21

29 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1028018 Bug ID: 1028018 Summary: Updating postfix gives chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I just `zypper dup`-ed a Tumbleweed installation and got the following: Installing: postfix-3.1.4-3.1.x86_64 ........[done] Additional rpm output: Executing upgrade-configuration. chown: cannot access '/usr/lib/postfix/dict_ldap.so': No such file or directory Updating /etc/sysconfig/postfix ... Updating /etc/sysconfig/mail ... Looking into /usr/lib/postfix indeed this file does not exist after the upgrade. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1045287] New: systemd: mounts using "nofail" option are not correctly ordered during shutdown
by bugzilla_noreply＠novell.com 24 Mar '21

24 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1045287 Bug ID: 1045287 Summary: systemd: mounts using "nofail" option are not correctly ordered during shutdown Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When a mount entry in fstab uses the "nofail" option, systemd doesn't order the corresponding mount unit with a "Before=local-fs.target" so if the mount unit takes time to be activated, it won't delay the whole boot process. However by doing this, we also remove ordering constraint for the shutdown process. This can lead to the mount unit being stopped while some applications are still using the corresponding mount point. This problem was discussed in bug 1036962 but this bug was more about NFS or remote fs. In this case the fix already exists since v218 and remote fs automatically gain a Before=remote-fs.target after they're mounted. A similar fix has been submitted upstream for local fs which can be found here: https://github.com/systemd/systemd/pull/6102 and is waiting for approval. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 934256] New: Passwords maintained by Filezilla are easily recovered in some cases
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=934256 Bug ID: 934256 Summary: Passwords maintained by Filezilla are easily recovered in some cases Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: Greg.Freemyer(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm testing with LaZagne: http://www.kitploit.com/2015/02/the-lazagne-project-recover-most-common.html Or in OBS @ home:gregfreemyer:Tools-for-forensic-boot-cd LaZagne Running LaZagne under my normal user account recovered one filezilla stored passwd. The amount of time taken was near instantaneous so I believe the password was simply decoded, not cracked in the sense of "John the ripper". The password was associated with a SFTP account, so it is a password I consider needing to be kept securely. I don't know if Filezilla simply handles passwords poorly or if it can be compiled differently to store passwords securely. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1084864] New: YaST module names are too similar to some desktop environment configuration modules
by bugzilla_noreply＠novell.com 19 Mar '21

19 Mar '21

http://bugzilla.suse.com/show_bug.cgi?id=1084864 Bug ID: 1084864 Summary: YaST module names are too similar to some desktop environment configuration modules Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: noahadvs(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 763361 --> http://bugzilla.suse.com/attachment.cgi?id=763361&action=edit How it should look when fixed YaST, GNOME, KDE Plasma and Enlightenment all have configuration modules named "Fonts" and a YaST module with the same exact name shows up when searching for "fonts" in all 3 DEs. This is not currently too much of a problem for users because the YaST Fonts module uses an icon representing X11 instead of an icon representing fonts, but there's no way to tell the difference without the icon. This will also be a problem for me because I am working on a KDE Breeze theme for YaST and intend to change the icon of the YaST Fonts module to a proper fonts icon. Fixing this problem will require changes to the code of yast-control-center and changes to the .desktop files shown for all YaST modules. 1. Every Name field needs to be prefixed with "YaST " or something similar to show association with YaST. However, this will cause every module name shown in the YaST Control Center to also have that prefix, which doesn't look good. 2. GenericName can be the field that YaST Control Center uses for module names instead. For example, the Name field could be "YaST Fonts" and the GenericName field could be "Fonts". 3. The GenericName field is currently used as if it was the Comment field, so YaST Control Center needs to display the Comment field instead of the GenericName field for module descriptions. All descriptions in the .desktop files need to be moved to the Comment field. -- You are receiving this mail because: You are on the CC list for the bug.

2 41