openSUSE Bugs November 2012

bugs@lists.opensuse.org

1 participants
4657 discussions

[Bug 776075] New: Dolphin terminal (console) remembers su (root) login after closing
by bugzilla_noreply＠novell.com 01 Nov '12

01 Nov '12

https://bugzilla.novell.com/show_bug.cgi?id=776075 https://bugzilla.novell.com/show_bug.cgi?id=776075#c0 Summary: Dolphin terminal (console) remembers su (root) login after closing Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: me(a)kalenz.eu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 When closing a terminal emulator after switching to su mode (root), the expectation is that su has been logged out. In other words, when the terminal is reopened, it has local user privileges only. Reproducible: Always Steps to Reproduce: 1. Open Dolphin from a local user (non-root) KDE session. 2. Hit F4 to bring up the terminal panel. 3. Write "su" enter, type root password --> gain root privileges. 4. Hit F4 again --> terminal closes. 5. On the same Dolphin window, hit F4 again... Actual Results: ...surprise, you're still root!! Expected Results: Should have lost root privileges after closing the terminal panel. In everyday office work, many Dolphin windows can be open at once, and stay open for days or weeks. Due to this bug, a "hidden" root login can remain active for a long time on machines accessible to many users, and "reappear" when someone just happens to press F4 on the same window. Reporting as "Major" severity due to security concern. -- 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 786689] New: remove SuSEconfig calls from yast2-restore
by bugzilla_noreply＠novell.com 01 Nov '12

01 Nov '12

https://bugzilla.novell.com/show_bug.cgi?id=786689 https://bugzilla.novell.com/show_bug.cgi?id=786689#c0 Summary: remove SuSEconfig calls from yast2-restore Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: locilka(a)suse.com ReportedBy: jsuchome(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- please remove SuSEconfig and inst_suseconfig calls from yast2-restore -- 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 786014] New: File type associations are wrong
by bugzilla_noreply＠novell.com 01 Nov '12

01 Nov '12

https://bugzilla.novell.com/show_bug.cgi?id=786014 https://bugzilla.novell.com/show_bug.cgi?id=786014#c0 Summary: File type associations are wrong Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: ruchir.brahmbhatt(a)ecosmob.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4 After installing opensuse 12.2, I had issues with file type associations. My text files open in libreoffice calc so I have to right click and open in kwrite every time. Then I updated associations in control panel which solved it but every kde update seems to ruin it and I have to update file type associations every time. Another such bad association is pdf. PDF defaults to gimp instead of okular. 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 3

[Bug 784998] New: gdm does not start after update on 13.10.2012
by bugzilla_noreply＠novell.com 01 Nov '12

01 Nov '12

https://bugzilla.novell.com/show_bug.cgi?id=784998 https://bugzilla.novell.com/show_bug.cgi?id=784998#c0 Summary: gdm does not start after update on 13.10.2012 Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: mail(a)frank-ansari.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=509473) --> (http://bugzilla.novell.com/attachment.cgi?id=509473) gdm logfiles User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4 After I got the latest updates on 13.10.2012 the desktop fails to start after booting. This did not happen before with this version. I have no idea what is going on: the only "fix" so far was to put /usr/sbin/gdm in /etc/init.d/after.local which is a very crude workaround of course. Please fix this. Frank 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 14

[Bug 769020] New: OpenSUSE 12.2 Beta 2 apache2 worker wont start with php
by bugzilla_noreply＠novell.com 01 Nov '12

01 Nov '12

https://bugzilla.novell.com/show_bug.cgi?id=769020 https://bugzilla.novell.com/show_bug.cgi?id=769020#c0 Summary: OpenSUSE 12.2 Beta 2 apache2 worker wont start with php Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Apache AssignedTo: bnc-team-apache(a)forge.provo.novell.com ReportedBy: asemen(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Component Test Blocker: --- OpenSUSE 12.2 Beta 2 apache2 worker wont start with php I would like to use the apche2 worker, therefor did configure in /etc/sysconfig/apache2 # grep APACHE_MPM /etc/sysconfig/apache2 APACHE_MPM="worker" rpm -q apache2-worker apache2-prefork apache2-utils php5 apache2-worker-2.2.22-3.1.x86_64 apache2-prefork-2.2.22-3.1.x86_64 apache2-utils-2.2.22-3.1.x86_64 php5-5.3.13-1.1.x86_64 on start of apache2 we get: # rcapache2 start redirecting to systemctl Job failed. See system journal and 'systemctl status' for details. # rcapache2 status redirecting to systemctl apache2.service - apache Loaded: loaded (/lib/systemd/system/apache2.service; disabled) Active: failed (Result: exit-code) since Wed, 27 Jun 2012 11:42:09 +0200; 4s ago Process: 31304 ExecStart=/usr/sbin/start_apache2 -D SYSTEMD -k start (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/apache2.service Jun 27 11:42:09 d172 start_apache2[31304]: [Wed Jun 27 11:42:09 2012] [crit] Apache is running a threaded MPM, but your PHP Module is not compiled to be threadsafe. You need...compile PHP. Jun 27 11:42:09 d172 start_apache2[31304]: Pre-configuration failed apache starts fine without php therefore removing php in /etc/sysconfig/apache2: grep APACHE_MODULES /etc/sysconfig/apache2 APACHE_MODULES="actions alias auth_basic authn_file authz_host authz_groupfile authz_default authz_user autoindex cgi dir env expires include log_config mime negotiation setenvif ssl userdir reqtimeout rewrite" # rcapache2 stop redirecting to systemctl # rcapache2 start redirecting to systemctl # rcapache2 status redirecting to systemctl apache2.service - apache Loaded: loaded (/lib/systemd/system/apache2.service; disabled) Active: active (running) since Wed, 27 Jun 2012 11:44:02 +0200; 2s ago Process: 31358 ExecStart=/usr/sbin/start_apache2 -D SYSTEMD -k start (code=exited, status=0/SUCCESS) Main PID: 31374 (httpd2-worker) CGroup: name=systemd:/system/apache2.service â 31374 /usr/sbin/httpd2-worker -f /etc/apache2/httpd.conf -D SYSTEMD -k start â 31375 /usr/sbin/httpd2-worker -f /etc/apache2/httpd.conf -D SYSTEMD -k start â 31376 /usr/sbin/httpd2-worker -f /etc/apache2/httpd.conf -D SYSTEMD -k start â 31377 /usr/sbin/httpd2-worker -f /etc/apache2/httpd.conf -D SYSTEMD -k start â 31378 /usr/sbin/httpd2-worker -f /etc/apache2/httpd.conf -D SYSTEMD -k start so it looks like a php apache2 modul problem -- 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 780677] New: Installer creates invalid elilo.conf causing ELILO not to boot system
by bugzilla_noreply＠novell.com 01 Nov '12

01 Nov '12

https://bugzilla.novell.com/show_bug.cgi?id=780677 https://bugzilla.novell.com/show_bug.cgi?id=780677#c0 Summary: Installer creates invalid elilo.conf causing ELILO not to boot system Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dexter.1234(a)hotmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 On a UEFI x86_64 platform, when doing an UEFI install and selecting ELILO as the boot loader, any global ELILO option that is not assigned a value during installation is written to elilo.conf as just the option string alone. This causes elilo.efi to hang when run due to a syntax error. ELILO requires options be written in the form "option = value". For example, if a value is not specified in the installer for the option "verbose" then the installer writes to elilo.conf: verbose This syntax error causes elilo.efi to hang leaving system unbootable. The installer should not write any global option for which no value has been entered. Reproducible: Always Steps to Reproduce: 1. Start installer in UEFI mode 2. Select ELILO as the bootloader 3. Allow installer to reboot system Actual Results: ELILO reports multiple syntax errors and waits for user intervention. ELILO cannot load kernel. Expected Results: ELILO should have run elilo.efi, in other words, the installer must not emit options to elilo.conf that are not in the form "option = value" to avoid syntax errors and ELILO hanging. When ELILO is selected as the boot loader during a UEFI mode install, the installer also installs the GRUB2 UEFI loader at EFI/opensuse/grub2.efi - but does not configure grub2 nor write and entry for grub2 in the UEFI BOOTXXX variables. The ELILO UEFI loader is installed at EFI/SuSE/elilo.efi. It has been a while since I have read the UEFI spec but I vaguely recall that a vendor should use only one directory in the ESP, so two directories violate the spirit of the spec. There is really no reason to have two different boot loaders installed on a non-development (end-user) machine anyway. Also, rEFit and rEFInd boot managers will find the erroneous GRUB2 UEFI loader. If the user selects the GRUB2 UEFI loader these boot managers will load it. Since GRUB2 was not configured, GRUB2 configuration is run. This issue was discovered because GRUB2 failed to install due to some errors during installation, don't remember what they were, but they occurred every time the system installer was run. Switch to ELILO because it is reliable. This bug is not friendly to a non-technical user. -- 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 787081] New: Boot fails with kernel 3.7-rc2 from Kernel:HEAD - maybe nouveau related
by bugzilla_noreply＠novell.com 01 Nov '12

01 Nov '12

https://bugzilla.novell.com/show_bug.cgi?id=787081 https://bugzilla.novell.com/show_bug.cgi?id=787081#c0 Summary: Boot fails with kernel 3.7-rc2 from Kernel:HEAD - maybe nouveau related Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jorge.adriano(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 Boot fails. The log is revealed and the end is along the lines of: RIP [<ffffffffa01da16a>] noveau_bios_score (...) RSP <ffff8801c3e9d978> CR2 <0000000000000010> -- end trace udevd /sbin/modprobe -bv pci I'd like to paste the actual log, but couldn't find it (I have no /var/log/boot*). Where is it supposed to be? Reproducible: Always Steps to Reproduce: 1. Boot 2. Pick kernel 3.7rc2 3. Wait Actual Results: Boot fail Expected Results: Boot success -- 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

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs November 2012