October 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 640407] New: SDL: erroneously uses xrandr-style mode switching
by bugzilla_noreply＠novell.com 09 Feb '18

09 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=640407 https://bugzilla.novell.com/show_bug.cgi?id=640407#c0 Summary: SDL: erroneously uses xrandr-style mode switching Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Beta-Customer Blocker: --- Starting with 11.3, I am seeing a new issue with my "oversize" desktop (2944x2208 VirtualSize on a 1280x1024 resolution). Problem: SDL-1.2.14. When SDL switches to fullscreen 640x480 - for example, because the game is configured to run in such resolution - or back, it changes the desktop size too by means of xrandr or something along the lines of that. Actual results: Windows on my desktop are reordered, which is usually a result of the WM being forced to do so because the desktop size (virtualsize) changed. Resolution switching also takes significantly longer than it did before — this is another sign that it switches desktop size (too), not just resolution. First the screen goes black-with-backlight and after roughly 500ms, the TFT screen finally gets the new 640x480 mode signal (I use VGA), which is evidenced by the backlight going briefly off. Expected results: Previous behavior. In other worsd, leave desktop size as-is (and subsequently keep my windows where they are) and _only_ change the resolution. The old switching style is also way faster in that there is no black-with-backlight delay. Additional information: Not all programs are affected. The entire group of Doom engines exhibits the behavior for example, though I found that UnrealTournament99 does not. Both Doom and UT use libSDL-1.2.so.0 (no static SDL as far as I can see). Overriding the system SDL 1.2.14 libraries and using LD_LIBRARY_PATH to point to SDL-1.2.13 libraries brings back the desired behavior. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 901361] New: IMAP+ plugin forces SSL 3.0
by bugzilla_noreply＠novell.com 30 Jan '18

30 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=901361 Bug ID: 901361 Summary: IMAP+ plugin forces SSL 3.0 Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Evolution Assignee: bnc-team-evolution(a)forge.provo.novell.com Reporter: sionescu(a)cddr.org QA Contact: lakhil(a)novell.com Found By: --- Blocker: --- Today(2014-10-15), FastMail disabled SSL 3.0 on all their servers because of a recently discovered vulnerability, and Evolution cannot connect to the imap server because it apparently forces SSL 3.0 on the outbound connection. I'm using Evolution 3.10.4-24.1 on x86_64 and the account is configured as follows: plugin IMAP+ on host "mail.messagingengine.com", port 993, encryption method "SSL on a dedicated port" The exact error message I get is "Could not connect to 'mail.messagingengine.com:993': Cannot communicate securely with peer: no common encryption algorithm(s)." -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 897422] New: systemd ignores swap options in fstab
by bugzilla_noreply＠novell.com 08 Jan '18

08 Jan '18

https://bugzilla.novell.com/show_bug.cgi?id=897422 https://bugzilla.novell.com/show_bug.cgi?id=897422#c0 Summary: systemd ignores swap options in fstab Classification: openSUSE Product: openSUSE Factory Version: 201409* Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa-bugs(a)suse.de Found By: Third Party Developer/Partner Blocker: --- Because I'm running on a SSD, I added the following to my fstab: susi:~ # grep swap /etc/fstab /dev/sda5 swap swap discard=once 0 0 This works well, if I do "swapon -a"; Sep 19 08:19:31 susi kernel: [583832.054201] Adding 2093052k swap on /dev/sda5. Priority:-1 extents:1 across:2093052k SSDsFS But during boot, it is not honored: susi:~ # dmesg|grep swap [ 8.339693] Adding 2093052k swap on /dev/sda5. Priority:-1 extents:1 across:2093052k SSFS (the missing "Ds" flags) Searching for who activates swap during boot, I looked through /var/log/boot.log: /var/log/boot.log: Activating swap /dev/sda5... /var/log/boot.log:[ OK ] Activated swap /dev/sda5. so I looked in the usual suspect for that string: susi:~ # rpm -ql systemd | xargs grep "Activating swap" 2>/dev/null Binary file /bin/systemd matches Binary file /usr/lib/systemd/systemd matches => systemd bug? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 736093] New: Logitech WebCam microphone produces squeaky "chipmunk" audio
by bugzilla_noreply＠novell.com 18 Dec '17

18 Dec '17

https://bugzilla.novell.com/show_bug.cgi?id=736093 https://bugzilla.novell.com/show_bug.cgi?id=736093#c0 Summary: Logitech WebCam microphone produces squeaky "chipmunk" audio Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: nils(a)ellmenreich.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20100101 Firefox/8.0 A regression in the linux kernel prevent some Logitech webcam microphones (notably C270, C300, C310) to be properly initialized. As a result, audio playback of recordings are way too fast, producing a "chipmunk" effect. Here is the patch: http://article.gmane.org/gmane.linux.usb.general/52027 Fedorea fixed this alread. References in: https://bugzilla.redhat.com/show_bug.cgi?id=729269 https://bugzilla.redhat.com/show_bug.cgi?id=742010 https://bugs.archlinux.org/task/26528 https://bugzilla.kernel.org/show_bug.cgi?id=35922 Reproducible: Always Steps to Reproduce: 1.Record audio using Logitech webcan (e.g. with skype test call) 2.listen 3. Actual Results: Chipmunk audio Expected Results: normal audio -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 509945] New: Enforce packaging of static libraries by rpmlint check
by bugzilla_noreply＠novell.com 09 Dec '17

09 Dec '17

http://bugzilla.novell.com/show_bug.cgi?id=509945 Summary: Enforce packaging of static libraries by rpmlint check Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: dmueller(a)novell.com ReportedBy: prusnak(a)novell.com QAContact: qa(a)suse.de CC: ro(a)novell.com, mrueckert(a)novell.com, crrodriguez(a)novell.com Found By: Development We are trying to adopt the static libraries packaging scheme described on http://en.opensuse.org/Packaging/Guidelines#Packaging_Static_Libraries By adding rpmlint check we will enforce the correct packaging. rpmlint should check whether the package contains *.{a,la} files and perform these steps: a) package contains *.la files, does not contain *.a files -> throw error suggesting the packager to remove *.la files in %install phase b) package contains only *.la and *.a files -> check if the name ends with "-devel-static", throw error otherwise, suggesting the rename c) package contains *.la, *.a files AND *.so files (and probably some includes) -> check if the name ends with "-devel" AND package also provides "-devel-static" symbol, throw error otherwise, suggesting the addition of symbol -> also point out that packager has to be sure that static libraries are absolutely needed in the system. If not the package should be built with --disable-static and *.la files removed in %install phase -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 8

[Bug 884004] New: bzip2 -dcf skips the first block if fed uncompressed data
by bugzilla_noreply＠novell.com 09 Dec '17

09 Dec '17

https://bugzilla.novell.com/show_bug.cgi?id=884004 https://bugzilla.novell.com/show_bug.cgi?id=884004#c0 Summary: bzip2 -dcf skips the first block if fed uncompressed data Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnweiger(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ echo hello world | bzip2 -dcf returns nothing. I'd expect to see 'hello world'. According to the manual, the effects of -f include: "bzip2 normally declines to decompress files which don't have the correct magic header bytes. If forced (-f), however, it will pass such files through unmodified. This is how GNU gzip behaves. strace includes: read(0, "hello world\n", 4096) = 12 read(0, "", 4096) = 0 lseek(0, 0, SEEK_SET) = -1 ESPIPE (Illegal seek) read(0, "", 4096) = 0 close(0) = 0 I assume, the failing lseek() should be acted on. Possibly already an upstream issue? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 709260] New: package bzip2 missing documentation
by bugzilla_noreply＠novell.com 09 Dec '17

09 Dec '17

https://bugzilla.novell.com/show_bug.cgi?id=709260 https://bugzilla.novell.com/show_bug.cgi?id=709260#c0 Summary: package bzip2 missing documentation Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i686 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB7.1) The documentation for package bzip2 is not installed. Reproducible: Always Steps to Reproduce: 1. Read /usr/share/doc/packages/bzip2/README. 2. Find the referenced documentation. Actual Results: 1. Complete documentation is available in Postscript form (manual.ps), PDF (manual.pdf) or html (manual.html). A plain-text version of the manual page is available as bzip2.txt. 2. Nope. Expected Results: 2. /usr/share/doc/packages/bzip2/manual.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 4

[Bug 875373] New: systemd-tmpfiles-setup.service runs before all filesystems are mounted
by bugzilla_noreply＠novell.com 06 Nov '17

06 Nov '17

https://bugzilla.novell.com/show_bug.cgi?id=875373 https://bugzilla.novell.com/show_bug.cgi?id=875373#c0 Summary: systemd-tmpfiles-setup.service runs before all filesystems are mounted Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: systemd-maintainers(a)suse.de ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- - Factory, last updated yesterday - last known-working version: Factory from 2014-04-13 systemd-tmpfiles-setup.service runs before all filesystems are mounted. (Probably) since the change that makes /var/run a symlink to /run, the tmpdirs below /var/run can't be created on my system. Note: I have an encrypted /home partition, and /var is a symlink to /home/sys-var. This means /var becomes available after /home has been mounted. systemd-tmpfiles-setup.service should wait until _all_ filesystems are mounted. # systemctl status systemd-tmpfiles-setup.service systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static) Active: active (exited) since So 2014-04-27 11:44:45 CEST; 29min ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 1491 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=0/SUCCESS) Main PID: 1491 (code=exited, status=0/SUCCESS) CGroup: /system.slice/systemd-tmpfiles-setup.service Apr 27 11:44:45 geeko systemd-tmpfiles[1491]: Failed to create directory /var/run/samba: No such file or directory Apr 27 11:44:45 geeko systemd-tmpfiles[1491]: Failed to create directory /var/run/svnserve: No such file or directory [... and some more /var/run/* directories with similar error message ...] Apr 27 11:44:45 geeko systemd[1]: Started Create Volatile Files and Directories. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 900376] New: Upgrading OpenSuse 13.1 using zipper or yast2 triggers network failures
by bugzilla_noreply＠novell.com 22 Oct '17

22 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900376 Bug ID: 900376 Summary: Upgrading OpenSuse 13.1 using zipper or yast2 triggers network failures Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: foolishewe(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 609401 --> http://bugzilla.opensuse.org/attachment.cgi?id=609401&action=edit Tar bundle of command output and log files from the initial bug report I have a Toshiba P855-S200 laptop that ran OpenSuse 12.1 (or was it 12.2) without incident. I recently brought it back on line and updated the to OpenSuse 13.1 from installation media (DVD) which went very smoothly. However when I do the post install upgrade of packages, the networking fails (both wireless and wired). The wireless adapter sees routers and connects using Network Manager (on KDE). It appears that DNS is working (e.g. nslookup cnn.com has the expected results), however actually retrieving data fails (e.g. wget cnn.com fails). This causes the online update to fail to download packages about 2/3 of the way through (always at the same point). Rebooting does not fix this. I am able to reproduce this, since I can use the install media to "Update" which actually reverts the updated packages. I've tried this several times and it appears to fail at the same point. What information is needed to track this down? How can I successfully upgrade my packages so that I get bug fixes and (more importantly) security updates? Please find attached a file name failedupgrade.tgz, which contains the following information tar tzvf ./failedupgrade.tgz drwxr-xr-x dummy/users 0 2014-10-08 21:25 ./failedupgradeinfo/ -rw-r--r-- dummy/users 524 2014-10-08 07:51 ./failedupgradeinfo/iwconfig.log -rw-r--r-- dummy/users 995 2014-10-08 21:23 ./failedupgradeinfo/wget.log -rw-r--r-- dummy/users 1367 2014-10-08 08:01 ./failedupgradeinfo/resolv.conf -rw-r--r-- dummy/users 126 2014-10-08 07:52 ./failedupgradeinfo/uname.log -rw-r--r-- dummy/users 61382 2014-10-08 08:07 ./failedupgradeinfo/dmesg.log -rw-r--r-- dummy/users 143734 2014-10-08 08:00 ./failedupgradeinfo/rpmqa.log -rw-r--r-- dummy/users 930961 2014-10-08 08:22 ./failedupgradeinfo/wpa_supplicant.log iwconfig.log - the output of iwconfig wget.log - the output of nslookup cnn.com and wget cnn.com after the failed on-line update resolv.conf - the actual resolv.conf file (I changed it to use faster dns servers). uname.log - the output of uname -a after the failed on-line update demesg.log - the output of dmesg after the failed on-line update rpmqa.log - the output of rpm -q -a after the failed on-line update wpa_supplicant.log - the wpa_supplicant.log file zypperlr.log - the output of zypper lr after the failed on-line upgrade attempt. Steps to reproduce: 1) Install 13.1 from media and upgrade the existing installation. 2) If necessary, remove the apper package, it interferes with zypper and yast2's software management. 3) Do Yast on-line update. Observe loss of network connectivity. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 830239] New: home:HighwayStar:sandbox:pf-kernel/kernel-postfactum: Bug
by bugzilla_noreply＠novell.com 16 Oct '17

16 Oct '17

https://bugzilla.novell.com/show_bug.cgi?id=830239 https://bugzilla.novell.com/show_bug.cgi?id=830239#c0 Summary: home:HighwayStar:sandbox:pf-kernel/kernel-postfactum: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: 32bit OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: highwaystar.ru(a)gmail.com ReportedBy: fanfan(a)bmail.ru QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- When you connect, for example, the flashdrive, is not installed automatically. I am loaded in the distributive kernel - all normal. In the setting of KDE automounting enabled. I look at dmesg, udevadm - all perfect, system sees the device, I look it in / dev . I can mount flashdrive manually. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1