openSUSE Bugs September 2013

bugs@lists.opensuse.org

1 participants
4505 discussions

[Bug 815322] New: device of "$PWD" not in output of mount if on 'root' (/dev/rootfs not in mount output)
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=815322 https://bugzilla.novell.com/show_bug.cgi?id=815322#c0 Summary: device of "$PWD" not in output of mount if on 'root' (/dev/rootfs not in mount output) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 I have a simple util program that has worked until recently -- I'm not sure if it went into 12.3 (I think so), or if it is in factory. These 3 lines demonstrate the problem: dev=$(df /bin |tail -1|cut -d\ -f1) mountline=$(mount|grep "$dev"); [[ -z ${mountline:-} ]] && mountline=ERROR echo "mounted with /etc/fstab line: '$mountline'" For some reason, the devices shown by 'mount' don't seem to be the devices shown in 'df' nor in /etc/fstab, yet both are documented to use /etc/mtab. Reproducible: Always Steps to Reproduce: 1. Try above script lines -- note that dev for root = /dev/root 2. But note that output of mount doesn't show /dev/root -- (only rootfs). 3. mount doesn't recognize 'rootfs' as a block device or special type: # mount rootfs /mnt mount: special device rootfs does not exist Ishtar:/bin# mount rootfs /mnt -t rootfs mount: wrong fs type, bad option, bad superblock on rootfs, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so Actual Results: mount claims root is on a non-existent device. Expected Results: mount should list values in mtab that show existing devices, not non-existent device aliases. -- 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 15

[Bug 819514] New: After update pushed 5/10/2013, network unavailable after resuming from sleep
by bugzilla_noreply＠novell.com 20 Feb '18

20 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=819514 https://bugzilla.novell.com/show_bug.cgi?id=819514#c0 Summary: After update pushed 5/10/2013, network unavailable after resuming from sleep Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tonysu(a)su-networking.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 First reported in this Forum thread http://forums.opensuse.org/english/get-technical-help-here/network-internet… For others in the thread, unknown whether recommendations were helpful. Note that others in the thread were not using Network Manager, whereas I am. For myself, my wireless networking was not functional (for that matter any networking) was functional resuming from sleep. Attempted to systemctl stop|start|restart network.service systemctl status network service returned Active with no errors after each above attempt. Service was verified stopped and restarted without errors. After rebooting, my network was still unavailable. Attampted again to stop|start|restart services. Then, I did a hardware NIC disable/re-enable which resulted in NM reporting networking enabled, but wireless "undetermined" (no check or unchecked box, a weird white box). Using NM, unchecked, re-checked "networking" and the wireless box was "normal, unchecked" Checked the box an wireless is working. After the wireless working was working again, I re-ran "systemctl status network.service" with the following results NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Sat 2013-05-11 14:35:15 PDT; 56s ago Main PID: 26829 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service └─26829 /usr/sbin/NetworkManager --no-daemon May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr0): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> ModemManager available in the bus The above may not be helpful, I suspect that the errors only refer to a number of virtual device bridges I have configured on this machine, but of course NM does not support managing those. Reproducible: Always Steps to Reproduce: 1. zypper up 5/10/2013 2. Put machine to sleep 3. resume machine Actual Results: Networking unavailable. Expected Results: Network should re-connect to available networks automatically Assigning Major, but impact likely depends on whether the User is able to regain networking either by restarting the network service or re-booting. If there are critical programs which would be adversely affected by a re-boot, then the problem is very serious, maybe even critical. -- 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 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 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 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 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

[Bug 782368] New: pcsc-lite should require libpcsclite1
by bugzilla_noreply＠novell.com 09 Oct '17

09 Oct '17

https://bugzilla.novell.com/show_bug.cgi?id=782368 https://bugzilla.novell.com/show_bug.cgi?id=782368#c0 Summary: pcsc-lite should require libpcsclite1 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jaanvajakas(a)hot.ee QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.8 (KHTML, like Gecko) Chrome/23.0.1255.0 Safari/537.8 SUSE/23.0.1255.0 Package pcsc-lite 1.8.3-2.1.3 in the repository http://download.opensuse.org/distribution/12.2/repo/oss/ currently does not require the libpcsclite1 package. Without the latter package, however, pcsc-lite seems pretty much useless: at least on my computer, pcscd is unable to detect my smartcard reader if libpcsclite1 is not installed. On Fedora, the analogous pcsc-lite package does require pcsc-lite-libs which is the analog of libpcsclite1: http://www.rpmfind.net//linux/RPM/fedora/devel/rawhide/i386/p/pcsc-lite-1.8… http://www.rpmfind.net//linux/RPM/fedora/devel/rawhide/i386/p/pcsc-lite-lib… So I guess the pcsc-lite package should require libpcsclite1. Reproducible: Always Steps to Reproduce: Install pcsc-lite package in YaST Software Manager. Actual Results: The libpcsclite1 package is not automatically installed when pcsc-lite is installed. Expected Results: libpcsclite1 should be automatically installed whenever pcsc-lite is installed. Actually I found this problem when I installed the Estonian ID card package (estonianidcard) from its official repository (https://installer.id.ee/media/opensuse); pcsc-lite is its (indirect) dependency but not libpcsclite1 so after installing estonianidcard I had to manually install libpcsclite1. -- 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 794744] New: samba4 package is missing the 'samba-tool'
by bugzilla_noreply＠novell.com 25 Sep '17

25 Sep '17

https://bugzilla.novell.com/show_bug.cgi?id=794744 https://bugzilla.novell.com/show_bug.cgi?id=794744#c0 Summary: samba4 package is missing the 'samba-tool' Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Samba AssignedTo: samba-maintainers(a)SuSE.de ReportedBy: rob.verduijn(a)gmail.com QAContact: samba-maintainers(a)SuSE.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 Hello, While giving samba4 I found that the 'samba-tool' command is not included. This command is required to set up a samba4 environment. (according to : https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC ) Regards Rob Verduijn Reproducible: Always Steps to Reproduce: 1. install samba4 from http://software.opensuse.org/package/samba 2. issue : rpm -ql samba4|grep samba-tool 3. Actual Results: missing samba-tool Expected Results: samba-tool should be included in the rpm -- 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 24

[Bug 661410] New: zypper ar vs. mr: different short option for --refresh
by bugzilla_noreply＠novell.com 22 Sep '17

22 Sep '17

https://bugzilla.novell.com/show_bug.cgi?id=661410 https://bugzilla.novell.com/show_bug.cgi?id=661410#c0 Summary: zypper ar vs. mr: different short option for --refresh Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- To enable --refresh for a repo, zypper has different short options: - zypper ar -f - zypper mr -r That's higly confusing. Please allow the same short option for both ar and mr in future versions. (For backward compatibility I'd recommend to allow -f _and_ -r as long as those aren't needed for different functions.) -- 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 5

← Newer
1
2
3
4
5
6
7
8
9
...
451
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs September 2013