June 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 815161] New: mount --no-canonical no longer works for output from 'mount"; (but does for df)
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=815161 https://bugzilla.novell.com/show_bug.cgi?id=815161#c0 Summary: mount --no-canonical no longer works for output from 'mount"; (but does for df) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: SUSE 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 When I use the no-canonical option in mount, it should take a dev-mapper file like this: /dev/mapper/HnS-Media_Back and change the display device name to /dev/HnS/Media_Back (which is what is listed in /etc/fstab). When I display this with mount, this no longer works. Maybe Mount no longer dispays values from /etc/mtab as it should: The programs mount and umount maintain a list of currently mounted filesystems in the file /etc/mtab. If no arguments are given to mount, this list is printed. Reproducible: Always Steps to Reproduce: 1. put a lvh volume in fstab by it's given name /dev/VolGroup/LogVolName in fstab. 2. Mount it with and without the --no-canonical 3. Try remounting it with "-f" as described in the man page: --no-canonicalize Don't canonicalize paths. The mount command canonicalizes all paths (from command line or fstab) and stores canonicalized paths to the /etc/mtab file. This option can be used together with the -f flag for already canonicalized absolut paths. Actual Results: the canonical name with "mapper" and dashes instead of slashes and double slashes instead of slashes, is shown in the mount command. Note: the "df" command shows the canonical name!! Expected Results: mount should display values from /etc/mtab not /proc/mounts. -- 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 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 852036] New: incorrect work of command _login_
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=852036 https://bugzilla.novell.com/show_bug.cgi?id=852036#c0 Summary: incorrect work of command _login_ Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Microsoft-SUXX(a)mail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.2; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 login by standart way in system type in console $login "username" 1) result in X - nothing 2) in console Alt-[F1-F6] result of this comman is LOGOUT but if username already loggeid in one of the other console - then rasult is also nothing Reproducible: Always Steps to Reproduce: 1. Add 2 or more user account in system 2. Get in X (graphic mode) console (terminal window) or 2A. Go to clear terminal in Alt-F1...Alt-F6 3. Type: login username Actual Results: In case 2. Nothing In case 2A. result of this command is LOGOUT. but if username already loggeid in one of the other console - then result is nothing Expected Results: Login with username account. -- 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 2

[Bug 856765] New: glmatrix process does not exit when xdcreensaver stops.
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=856765 https://bugzilla.novell.com/show_bug.cgi?id=856765#c0 Summary: glmatrix process does not exit when xdcreensaver stops. Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: carlos.e.r(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Situation: 13.1 system with XFCE desktop, freshly installed with all mandatory updates, nvidia proprietary driver (obviously, because it needs 3D to run this app) installed via rpm. Xscreensaver is configured to run GLmatrix screensaver. When the screensaver triggers, and I use the machine again, I see this in top: top - 11:40:06 up 2 days, 12:52, 10 users, load average: 0.10, 0.13, 0.14 Tasks: 249 total, 2 running, 247 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.5 us, 0.9 sy, 0.6 ni, 97.0 id, 1.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 8193444 total, 3444632 used, 4748812 free, 474056 buffers KiB Swap: 22017008 total, 334780 used, 21682228 free, 1524108 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7613 cer 39 19 128488 37036 22104 S 4.318 0.452 0:32.43 glmatrix 31774 root 20 0 344936 216676 35976 S 1.661 2.645 39:55.93 X 5105 cer 20 0 1598580 249768 42852 S 0.332 3.048 8:29.26 thunderbird-bin A process named 'glmatrix' is still running, using more CPU than any - which is why I noticed. It can not be killed normally, it has to be killed 9. See: cer@Elessar:~> killall glmatrix cer@Elessar:~> killall -9 glmatrix cer@Elessar:~> killall glmatrix cer@Elessar:~> killall glmatrix cer@Elessar:~> killall -9 glmatrix cer@Elessar:~> killall -9 glmatrix glmatrix: no process found cer@Elessar:~> -- 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 6

[Bug 858493] New: mount-by-device ceased to work properly in 13.1
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=858493 https://bugzilla.novell.com/show_bug.cgi?id=858493#c0 Summary: mount-by-device ceased to work properly in 13.1 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: mario.natiello(a)math.lth.se QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 The following fstab entries [CODE] /dev/sdb1 /mount/usbdisk vfat user,rw,noauto 0 0 remuser@IP:. /localuser/target fuse.sshfs users,allow_other,reconnect, follow_symlinks,rw, noauto,_netdev,idmap=user,uid=1000,gid=100, IdentityFile=/localuser/.ssh/id_rsa,ServerAliveInterval=60 0 0 [/CODE] should allow to mount the filesystems just by stating EITHER the device OR the mountpoint as in, e.g., [CODE] > mount /dev/sdb1 > mount /mount/usbdisk > mount /localuser/target [/CODE] All these work ok. However the following one does not work: [CODE] > mount remuser@IP:. mount: remuser@IP:.: No such file or directory > mount --source remuser@IP:. mount: remuser@IP:.: No such file or directory[/CODE] [/CODE] despite the fact that the syntax is supported by the man pages of fstab, mount and sshfs, and despite the fact that it did work in 12.2 and it currently works in other distros (I tried in ubuntu 13.04). Reproducible: Always Steps to Reproduce: 1. Put in fstab a remote device that is mounted by sshfs 2. mount the device by stating "mount device" or "mount --source device" 3. mount fails while "mount mountpoint" does not fail. Actual Results: [/CODE] > mount remuser@IP:. mount: remuser@IP:.: No such file or directory > mount --source remuser@IP:. mount: remuser@IP:.: No such file or directory [/CODE] [/CODE] Expected Results: Remote file system properly mounted -- 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

[Bug 877685] New: smartmontools can not read information from MegaRaid controller
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=877685 https://bugzilla.novell.com/show_bug.cgi?id=877685#c0 Summary: smartmontools can not read information from MegaRaid controller Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: svalx(a)svalx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:29.0) Gecko/20100101 Firefox/29.0 smartmontools-6.2-2.1.2.x86_64 I have a single MegaRaid 9240-8i controller with 8 disks on 2 RAID's. and want to get info about this disks. Reproducible: Always Steps to Reproduce: ---------- # smartctl -i /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.3-26.g2a280a3-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Smartctl open device: /dev/sdd failed: DELL or MegaRaid controller, please try adding '-d megaraid,N' --------- # smartctl -i -d megaraid,0 /dev/sdd smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.14.3-26.g2a280a3-desktop] (SUSE RPM) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Smartctl open device: /dev/sdd [megaraid_disk_00] failed: INQUIRY failed --------- $ man smartctl ... megaraid,N - [Linux only] the device consists of one or more SCSI/SAS disks connected to a MegaRAID controller. The non-negative integer N (in the range of 0 to 127 inclusive) denotes which disk on the controller is monitored. Use syntax such as: smartctl -a -d megaraid,2 /dev/sda smartctl -a -d megaraid,0 /dev/sdb smartctl -a -d megaraid,0 /dev/bus/0 The following entry in /proc/devices must exist: For PERC2/3/4 controllers: megadevN For PERC5/6 controllers: megaraid_sas_ioctlN ... --------- $ grep mega /proc/devices 250 megaraid_sas_ioctl --------- So I have megaraid_sas_ioctl instead megaraid_sas_ioctl0 and probably it case of failed inquiry. -- 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 2

[Bug 862739] New: openvpn creates non-functional client config
by bugzilla_noreply＠novell.com 26 Feb '18

26 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=862739 https://bugzilla.novell.com/show_bug.cgi?id=862739#c0 Summary: openvpn creates non-functional client config Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 I have recently upgraded our local openvpn endpoint to 13.1, which also meant upgrading openvpn to 2.3.2 . I copied over our existing configuration and added "topology subnet". The new configuration no longer works, it seems to be handing out an invalid client config. Previous config that worked: 2013-07-30T17:02:44.084956+02:00 toshi1 openvpn[5616]: PUSH: Received control message: 'PUSH_REPLY,route 192.168.0.0 255.255.0.0,route 192.168.13.1,ping 10,ping-restart 120,ifconfig 192.168.13.9 192.168.13.10' Current config which doesn't work: 2014-02-07T09:56:14.797888+01:00 toshi1 openvpn[8133]: PUSH: Received control message: 'PUSH_REPLY,route 192.168.0.0 255.255.240.0,topology p2p,ping 10,ping-restart 120,ifconfig 255.255.255.0 192.168.13.10' The "ifconfig 255.255.255.0 192.168.13.10" part looks particularly dodgy and presumably leads to this faulty network config: 4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100 link/none inet 255.255.255.0 peer 192.168.13.10/32 scope global tun0 valid_lft forever preferred_lft forever It is correctable by amending the addresses: ip addr add 192.168.13.9 peer 192.168.13.10 dev tun0 ip addr del 255.255.255.0/32 dev tun0 Reproducible: Always -- 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 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