April 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 813031] New: Lock desktop )panel reopens desktop for simple CRLF( simple press enter, no password)
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=813031 https://bugzilla.novell.com/show_bug.cgi?id=813031#c0 Summary: Lock desktop )panel reopens desktop for simple CRLF( simple press enter, no password) Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure AssignedTo: mrueckert(a)suse.com ReportedBy: frankguz(a)verizon.net QAContact: lrupp(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Once you select "lock Desktop", go away from your work, and return, all you need to do is press enter and the desktop will be there for you. No password required! Reproducible: Always Steps to Reproduce: 1. Lock desktop 2. go to bathroom or whatever 3. return and press enter or touch the "mousepad" 4. You are ready to go to work no error message, just a very compliant "non-safety" issue. This worked fine in 12.2, not in 12.3 -- 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 803997] New: partitioner names a partition unbootable which boots perfectly fine.
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=803997 https://bugzilla.novell.com/show_bug.cgi?id=803997#c0 Summary: partitioner names a partition unbootable which boots perfectly fine. Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jw(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- I have three partitions that i use for alternative root partitions /dev/sda6,7,8 while the mbr resides in the extended partition /dev/sda3 Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x122ff57e Device Boot Start End Blocks Id System /dev/sda1 63 62910602 31455270 7 HPFS/NTFS/exFAT /dev/sda2 62912512 71297023 4192256 82 Linux swap / Solaris /dev/sda3 * 71297024 625141759 276922368 f W95 Ext'd (LBA) /dev/sda5 71299072 176152575 52426752 83 Linux /dev/sda6 176154624 281008127 52426752 83 Linux /dev/sda7 281010176 385865727 52427776 83 Linux /dev/sda8 385867776 625121279 119626752 83 Linux both sda6 and sda7 triggered a warning message, saying there are sectors above 1024 which my bios cannot handle. I did not test sda5, this is a 12.2 system that should survive. Chossing sda6 despite the warning works fine, the system happily boots into my new 12.3 -- 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 812406] New: vsftpd dies on attemt to download file
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=812406 https://bugzilla.novell.com/show_bug.cgi?id=812406#c0 Summary: vsftpd dies on attemt to download file Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Critical Priority: P5 - None Component: Network AssignedTo: mvyskocil(a)suse.com ReportedBy: mvyskocil(a)suse.com QAContact: qa-bugs(a)suse.de Blocks: 786024 Found By: --- Blocker: --- vsftpd with sandbox enabled and patch for audit issue in bnc#786024 ftp ftp://test:test@localhost/hello Trying ::1... Connected to localhost. 220 (vsFTPd 3.0.2) 331 Please specify the password. 230 Login successful. Remote system type is UNIX. Using binary mode to transfer files. 200 Switching to Binary mode. local: hello remote: hello 229 Entering Extended Passive Mode (|||30023|). 500 OOPS: priv_sock_get_cmd 421 Service not available, remote server has closed connection. /var/log/messages 2013-03-29T09:33:23.559824+01:00 linux-xtv2 systemd[1]: Starting Vsftpd ftp daemon... 2013-03-29T09:33:23.562134+01:00 linux-xtv2 systemd[1]: Started Vsftpd ftp daemon. 2013-03-29T09:33:28.095789+01:00 linux-xtv2 vsftpd[22841]: [test] OK LOGIN: Client "::1" 2013-03-29T09:33:28.116495+01:00 linux-xtv2 kernel: [84590.368752] type=1326 audit(1364546008.115:11): auid=4294967295 uid=17021 gid=100 ses=4294967295 pid=22845 comm="vsftpd" sig=31 syscall=72 compat=0 ip=0x7fdcc2c68d62 code=0x0 disabling seccomp sandbox is a workaround -- 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 807360] New: efi boot loader is not detectet during installation
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=807360 https://bugzilla.novell.com/show_bug.cgi?id=807360#c0 Summary: efi boot loader is not detectet during installation Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: 64bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jordirelats(a)terra.es QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.97 Safari/537.22 I have a Lenovo Yoga, that have installed windows 8, I tried to install opensuse 12.3 the efi partition is on sda2, aparently the efi boot is not detected during installation, when is selected manualy the GRUB2-efi then apper the indication, hardware incompatibility with grub2-efi Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 810022] New: nVidia proprietary drivers broken for 12.3
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=810022 https://bugzilla.novell.com/show_bug.cgi?id=810022#c0 Summary: nVidia proprietary drivers broken for 12.3 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: X11 3rd Party Driver AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tonysu(a)su-networking.com QAContact: sndirsch(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Scope of affected Users Unknown. I would guess should affect at least all who have avoided nouveau drivers in the past due to the notorious "kaleidescope" problem which has existed from approx openSUSE versions 11.1-12.2 Affects CUDA users Both KMS on/off Included are all the relevant logfiles I used to troubleshoot All logfiles were retrieved during the failed graphical boot by dropping into a command line console. Each of the logfiles were modified by adding as the first line the command used to retrieve that logfile Summary: Cause of problem appears to be Attempt to load non-existent "nevidia module" NOTE: Secondary issue, when changing from nVidia driver to nouveau or nv drivers, the xorg.conf file is not automatically modified or deleted, manual User intervention is required. apparently this is a long-standing unaddressed issue and unlike when the User is prompted to run nvidia.config when installing the proprietary nvidia driver, the User is not prompted or given any clue this is required when installing the nouveau or nv drivers. For this reason, although this is primarily a 3rd party driver problem, IMO the xorg.conf issue should be fixed by either whoever develops kdm or however the xorg-conf file is managed. Reproducible: Always Steps to Reproduce: Install or upgrade with nVidia Repo enabled. ftp://download.nvidia.com/opensuse/12.3/ As prompted, run nvidia-config to create the required xorg.config When booting, normally, click ESC to view the bootup sequence Immediately before reaching the Plymouth startup screen, note that bootup hangs on "Reached graphical user interface" This is where most people cannot proceed further Actual Results: System bootup hangs Expected Results: Proceed to Plymouth Proceeding from when the system hangs, It is at this point that the accompanying logs were retrieved Do not wait too long to escape to console by entering ALT-F1, otherwise after a minute or so the system will freeze. The following commands were used to retrieve the logs systemctl --all --type=target cat /var/log/boot.log journalctl -b systemctl status plymouth-start.service cat /var/log/Xorg.0.log IMO most important information from these logs, clearly the X server starts and an attempt is made to [LoadModule: "nvidia"] but failing that the Xserver stops. The system then attempts to connect to graphical.target and unable to find a running X server hangs (maybe there should also be a graceful fallback like automatically escape to console?) journal.log Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK xdm[736]: Starting service kdm..done Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Started LSB: X Display Manager. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK acpid[580]: client connected from 801[0:0] Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK acpid[580]: 1 client rule loaded Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK kdm[771]: X server died during startup Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK kdm[771]: X server for display :0 cannot be started, session disabled Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK fail2ban[734]: Starting fail2ban ..done Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Started LSB: Bans IPs with too many authentication failures. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Starting Multi-User. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Reached target Multi-User. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Starting Graphical Interface. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Reached target Graphical Interface. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Starting Stop Read-Ahead Data Collection 10s After Completed Startup. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Starting Update UTMP about System Runlevel Changes... Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Started Update UTMP about System Runlevel Changes. Mar 17 18:12:44 SUSEMACHINE.LOCALNETWORK systemd[1]: Startup finished in 3s 576ms 851us (kernel) + 4s 647ms 496us (userspace) = 8s 224ms 347us. Mar 17 18:12:51 SUSEMACHINE.LOCALNETWORK acpid[580]: client 801[0:0] has disconnected Xorg.0.log 7.899] Loading extension GLX [ 7.899] (II) LoadModule: "nvidia" [ 7.900] (WW) Warning, couldn't open module nvidia [ 7.900] (II) UnloadModule: "nvidia" [ 7.900] (II) Unloading nvidia [ 7.900] (EE) Failed to load module "nvidia" (module does not exist, 0) [ 7.900] (EE) No drivers available. [ 7.900] Fatal server error: [ 7.900] no screens found [ 7.900] (EE) -- 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 807078] New: Installation in german textmode renders yast unusable
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=807078 https://bugzilla.novell.com/show_bug.cgi?id=807078#c0 Summary: Installation in german textmode renders yast unusable Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kollix(a)aon.at QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; i686 Linux; en_US, de; rv:1.9.2) Gecko/20100115 Firefox/3.6 On a new PC I started 12.3RC1 installation and chose the german language in the boot menu. I selected "nomodeset" (due to Xorg not starting) and the installation was doing fine in textmode. After reboot I logged into the text console as root and had a locale setting of all LC_XXX set to POSIX but LC_CTYPE=de_DE.utf8 Starting yast brings up the textmode version but all the special graphical characters (lines, corners) are displayed as multiple wrong characters, which not only looks ugly but the main problem is that yast becomes unusable as the multi-characters overlap the following lines so one can not read what yast writes. unset LC_CTYPE solves the problem, but the installation should not leave only this variable in the wrong setting. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: yast should be usable after a fresh (german) install in textmode also without the need to fiddle with settings (and to invest time in finding out the root cause) -- 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 813293] New: locate finds files in btrfs snapshots
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=813293 https://bugzilla.novell.com/show_bug.cgi?id=813293#c0 Summary: locate finds files in btrfs snapshots Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: herbert(a)women-at-work.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 The file /var/adm/fillup-templates/sysconfig.locate from findutils-locate-4.5.10-10.1.1.x86_64 has a wrong default for UPDATEDB_PRUNEPATHS. The variable contains "/.snapshot" while it should contain "/.snapshots". So updatedb walks through all btrfs snapshots and locate finds everything multiple times. Reproducible: Always Steps to Reproduce: Execute "locate etc/fstab" Actual Results: Found in every snapshot Expected Results: Only one file is found: /etc/fstab -- 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 780918] New: updatedb indexes all btrfs snapshots by default
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=780918 https://bugzilla.novell.com/show_bug.cgi?id=780918#c0 Summary: updatedb indexes all btrfs snapshots by default Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: erwin.vandevelde(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 I am using btrfs as a root filesystem, so on a default installation I have /.snapshots with all snapper snapshots. When running updatedb, currently /.snapshots is not excluded, so all snapshots are indexed, resulting in a very long updatedb run and way too many results when using locate. Reproducible: Always Steps to Reproduce: 1. use btrfs as rootfs 2. install findutils-locate 3. run updatedb Actual Results: Very long updatedb, all snapshots are indexed, so way too many results in a locate search afterwards Expected Results: Exclusion of /.snapshots by default, so only the 'current system' and not all snapshots are indexed findutils-locate 4.5.10-5.1.3 -- 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 10

[Bug 813988] New: [wqy-bitmap-fonts] fontconfig error: invalid attribute 'equal'
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=813988 https://bugzilla.novell.com/show_bug.cgi?id=813988#c0 Summary: [wqy-bitmap-fonts] fontconfig error: invalid attribute 'equal' Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: i(a)marguerite.su QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Reported by Chinese forum users. Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 28: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 45: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 62: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 79: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 96: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 113: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 130: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 147: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 164: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 181: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 198: invalid attribute 'equal' Fontconfig error: "/etc/fonts/conf.d/85-wqy-bitmapsong.conf", line 215: invalid attribute 'equal' Actually `equal` is not a standard fontconfig attribute. So seems it's a packager's typo. 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 811434] New: embedded terminal could not be loaded in gedit
by bugzilla_noreply＠novell.com 15 Apr '13

15 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=811434 https://bugzilla.novell.com/show_bug.cgi?id=811434#c0 Summary: embedded terminal could not be loaded in gedit Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: hendrikkunert(a)freenet.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 The embedded terminal from package 'gedit-plugins' could not be loaded in gedit. Reproducible: Always Steps to Reproduce: 1. install package 'gedit-plugins' 2. open gedit 3. go to 'edit/preferences/plugins' 4. click on 'embedded terminal' Actual Results: Error Message: Embedded Terminal could not be loaded. Expected Results: should load the Embedded Terminal It seems that there is a deprecated version of the plugin in the repo. In Linux Mint with Cinnamon (should also be GTK3) the Embedded Terminal is working. output from console: File "/usr/lib64/gedit/plugins/terminal.py", line 23, in <module> from gi.repository import GObject, GLib, Gio, Pango, Gdk, Gtk, Gedit, Vte File "/usr/lib64/python2.7/site-packages/gi/importer.py", line 76, in load_module dynamic_module._load() File "/usr/lib64/python2.7/site-packages/gi/module.py", line 242, in _load version) File "/usr/lib64/python2.7/site-packages/gi/module.py", line 97, in __init__ repository.require(namespace, version) gi.RepositoryError: Requiring namespace 'Gtk' version '2.0', but '3.0' is already loaded (gedit:2771): libpeas-WARNING **: Error loading plugin 'terminal' -- 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 9