June 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 802892] New: Num lock does not start with X
by bugzilla_noreply＠novell.com 15 Jun '13

15 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=802892 https://bugzilla.novell.com/show_bug.cgi?id=802892#c0 Summary: Num lock does not start with X Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 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: clayzanfolin(a)bol.com.br QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 PT-BR Olá! verifique que não esta sendo possível iniciar o X com o num lock ativado, mesmo tendo marcado nas opções de teclado no momento da instalação para ativar o num lock junto com o X. Notei que o software numlockx esta instalado por tanto creio que seja que a opção do layout do teclado do sistema no yast que não esteja marcando o evento que chama o num lock no inicio do X. EN-Google Hello! finds that not being able to start X with the num lock on, even scoring in keyboard options at installation to activate the num lock together with X. I noticed that the software is installed numlockx therefore believe it is the choice of keyboard layout system in yast that is not marking the event that calls the num lock at the beginning of X. openSUSE 12.3 RC1 Reproducible: Always Steps to Reproduce: 1.Yast2 2.Hardware 3.layout keyboard 4.advanced Configurtacões 5.startup states 6.Mumlok active Actual Results: 1.Yast2 2.Hardware 3.layout keyboard 4.advanced Configurtacões 5.startup states 6.Mumlok active 7.yes 9.ok 10.ok 8.X.org ctrl+alt+backspace 2x or reboot Expected Results: Should a Iniciá the num lock Along with X.org but nothing happens. -- 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 825130] New: Login to bugzilla.novell.com loops - clearing out all *novell* and *attachmate* cookies resolves the problem
by bugzilla_noreply＠novell.com 15 Jun '13

15 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=825130 https://bugzilla.novell.com/show_bug.cgi?id=825130#c0 Summary: Login to bugzilla.novell.com loops - clearing out all *novell* and *attachmate* cookies resolves the problem Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=544247) --> (http://bugzilla.novell.com/attachment.cgi?id=544247) tcpdump with filter 'host 130.57.66.9' User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Every now and then, maybe every 3-4 months, it becomes impossible to get access to bugzilla. When I try to log in, the browser keeps getting redirected, and eventually gives up. So far, the way to resolve it has been to clear out all *novell* and all *attachmate* cookies, then reload the URL. A similar issue seems to also affect openFATE (https://features.opensuse.org) Reproducible: Sometimes -- 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 825054] New: libkgeomap1 version mismatch if using KUSC and KUP
by bugzilla_noreply＠novell.com 14 Jun '13

14 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=825054 https://bugzilla.novell.com/show_bug.cgi?id=825054#c0 Summary: libkgeomap1 version mismatch if using KUSC and KUP Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: johannesobermayr(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.21 (KHTML, like Gecko) rekonq/2.3.0 Safari/537.21 If you want to update digikam & co. via YaST2 you get version mismatch errors: digikam from KUP depends on a 3.2.0+ version of libkgeomap1 KUSC provides a higher 4.10.41_ version which YaST2 wants to install by default. 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 1

[Bug 751038] New: password promot for encryption is buried among booting messages
by bugzilla_noreply＠novell.com 14 Jun '13

14 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=751038 https://bugzilla.novell.com/show_bug.cgi?id=751038#c0 Summary: password promot for encryption is buried among booting messages Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: bluedzins(a)wp.pl QAContact: jsrain(a)suse.com Found By: --- Blocker: --- password promot for encryption is buried among booting messages *Ok, short version because the timeouts from this website are killing me.* You have encrypted partition, you should enter password for it, when booting up computer. You should see something like this ON BLANK SCREEN: please enter password: |_______________ Actually you see: booting messages mess please enter password more booting messages mess | Since there is timeout for entering password it is easy to miss the fact, that computer does not think long, but it waits for the input, however thanks to complete mess on the screen it is not clearly readable. -- 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 790246] New: zypper dup from 12.2 to Factory hangs restarting YaST2-Second-Stage service
by bugzilla_noreply＠novell.com 14 Jun '13

14 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=790246 https://bugzilla.novell.com/show_bug.cgi?id=790246#c0 Summary: zypper dup from 12.2 to Factory hangs restarting YaST2-Second-Stage service Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 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: arvidjaar(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.10) Gecko/20100101 Firefox/10.0.10 The following was observed when trying to do online update from 12.2 to Factory - installation hung in yast2-installation post script. Some relevant information: UID PID PPID C STIME TTY TIME CMD root 7322 5968 0 15:51 tty1 00:00:00 -bash root 10436 7322 0 17:45 tty1 00:01:38 zypper dup root 12072 10436 0 22:05 tty1 00:00:00 rpm --root / --dbpath /var/lib/rpm -U --percent --force --nodeps -- /var/cache/zypp/packages/repo-oss/suse/noarch/yast2-installation-2.23.3-1.1.noarch.rpm root 12080 12072 0 22:05 tty1 00:00:00 /bin/sh /var/tmp/rpm-tmp.eFpzf6 1 root 12081 12080 0 22:05 tty1 00:00:00 /bin/systemctl try-restart YaST2-Second-Stage.service YaST2-Firstboot.service systemctl status YaST2-Second-Stage.service - YaST2 Second Stage Loaded: loaded (/lib/systemd/system/YaST2-Second-Stage.service; enabled) Active: deactivating (stop-sigterm) since Sat, 2012-11-17 22:05:55 MSK; 10min ago Main PID: 462 (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/YaST2-Second-Stage.service Nov 17 19:50:52 linux-m0sc SuSEfirewall2[4994]: Firewall rules unloaded. Nov 17 19:50:52 linux-m0sc SuSEfirewall2[5003]: Setting up rules from /etc/sysconfig/SuSEfirewall2 ... Nov 17 19:50:52 linux-m0sc SuSEfirewall2[5129]: Firewall rules successfully set Nov 17 19:50:57 linux-m0sc ifdown[5693]: eth0 device: Intel Corporation 82545EM Gigabit Ethernet Co Nov 17 19:50:57 linux-m0sc dhcpcd[5719]: eth0: sending signal 15 to pid 4642 Nov 17 19:50:57 linux-m0sc dhcpcd[4642]: eth0: received SIGTERM, stopping Nov 17 19:50:57 linux-m0sc dhcpcd[4642]: eth0: removing default route via 192.168.92.2 metric 0 Nov 17 19:50:57 linux-m0sc dhcpcd[4642]: eth0: removing IP address 192.168.92.128/24 Nov 17 19:50:57 linux-m0sc dhcpcd[5719]: eth0: exiting Nov 17 19:50:57 linux-m0sc dhcpcd[4642]: eth0: exiting Warning: Unit file changed on disk, 'systemctl --system daemon-reload' recommended. systemctl list-jobs 665 YaST2-Second-Stage.service restart running I had to use "systemctl cancel" to allow it to proceed. 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 7

[Bug 790069] New: ssh session does not close on shutdown
by bugzilla_noreply＠novell.com 14 Jun '13

14 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=790069 https://bugzilla.novell.com/show_bug.cgi?id=790069#c0 Summary: ssh session does not close on shutdown Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: rschweikert(a)suse.com QAContact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com Found By: --- Blocker: --- With the latest update to systemd in Factory an ssh session no longer closes when a shutdown command is issued. Reproduce: - login via ssh to factory system with the latest systemd version - issue shutdown command Result: - The terminal is now "hung", i.e. the ssh client has no idea that the server went away Expected result: - The ssh client recognizes that the server is no longer there and exits The expected result was observed with previous versions of systemd, in the latest version this does no longer happen. -- 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 798793] New: NetworkManager no longer connects to 802.1x networks (Novell network)
by bugzilla_noreply＠novell.com 14 Jun '13

14 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=798793 https://bugzilla.novell.com/show_bug.cgi?id=798793#c0 Summary: NetworkManager no longer connects to 802.1x networks (Novell network) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: idonmez(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.27 (KHTML, like Gecko) Chrome/26.0.1385.0 Safari/537.27 In the Nuremberg office I am trying to connect to "Novell" network which uses Protected EAP MSCHAPv2 What happens is, 1. I enter my username/password 2. Click "Connect". 3. It shows the warning dialog "No Certificate Authority Certificate chosen" 4. I click "Ignore" and nothing happens, nothing in the NetworkManager log either (with log level DEBUG). 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 28

[Bug 802952] New: Installation settings/Booting - enable/disable links are non functional
by bugzilla_noreply＠novell.com 14 Jun '13

14 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=802952 https://bugzilla.novell.com/show_bug.cgi?id=802952#c0 Summary: Installation settings/Booting - enable/disable links are non functional 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: arvidjaar(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=524020) --> (http://bugzilla.novell.com/attachment.cgi?id=524020) Bootloader screen summary User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 On installation summary screen Booting section got new possibility - enable/disable booting from MBR or root partition without going into full bootloader configuration (see screenshot). Booting Boot from MBR (enable/disable) Boot from / partition (enable/disable) These links are non-functional. Clicking on them does not change anything. 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 4

[Bug 824826] New: [openSUSE goes SLE12]: xfig: Change and/or patches may lost
by bugzilla_noreply＠novell.com 13 Jun '13

13 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=824826 https://bugzilla.novell.com/show_bug.cgi?id=824826#c0 Summary: [openSUSE goes SLE12]: xfig: Change and/or patches may lost Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: All OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: werner(a)suse.com ReportedBy: werner(a)suse.com QAContact: qa-bugs(a)suse.de CC: patch-lost-in-sle(a)suse.de Found By: --- Blocker: --- This is a simple test -- 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 386330] <hosts> entries does not seem to work properly in AutoYaST
by bugzilla_noreply＠novell.com 13 Jun '13

13 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=386330 https://bugzilla.novell.com/show_bug.cgi?id=386330#c6 Michal Svec <msvec(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |jsrain(a)suse.com, | |locilka(a)suse.com Resolution| |FIXED --- Comment #6 from Michal Svec <msvec(a)suse.com> 2013-06-13 12:48:21 CEST --- (In reply to comment #5) > This problem also exists in SLES 10 SP4. Thanks for the report. Please open a Service Request with SUSE Support. Thank you! -- 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 0