https://bugzilla.novell.com/show_bug.cgi?id=737917https://bugzilla.novell.com/show_bug.cgi?id=737917#c0
Summary: very slow boot with systemd
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
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: wolfgang(a)rosenauer.org
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
Sorry that I cannot add much initial information but I don't know how to
diagnose anything in systemd.
My 11.4 boots to kdm within 25 seconds
12.1 with systemd needs 51 seconds to show me KDM on the same hardware.
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=738872https://bugzilla.novell.com/show_bug.cgi?id=738872#c0
Summary: release request created for new packages is wrong
Classification: Internal Novell Products
Product: openSUSE Build Service
Version: master
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: api
AssignedTo: adrian(a)suse.com
ReportedBy: dmueller(a)suse.com
QAContact: adrian(a)suse.com
Found By: ---
Blocker: ---
https://build.opensuse.org/request/show/98411
was created via webui as release request from openSUSE:Maintenance:81
release target is
maintenance_release: openSUSE:Maintenance:81/patchinfo ->
openSUSE:12.1:Update/patchinfo.81
maintenance_release:
openSUSE:Maintenance:81/parallel-printer-support.openSUSE_12.1 ->
openSUSE:12.1:Update/parallel-printer-support.openSUSE_12.1.81
it should be
maintenance_release: openSUSE:Maintenance:81/patchinfo ->
openSUSE:12.1:Update/patchinfo.81
maintenance_release:
openSUSE:Maintenance:81/parallel-printer-support.openSUSE_12.1 ->
openSUSE:12.1:Update/parallel-printer-support.81
the name can be determined from the _link file in
openSUSE:Maintenance:81/parallel-printer-support.openSUSE_12.1
<link project="openSUSE:12.1:Update" package="parallel-printer-support"
baserev="d41d8cd98f00b204e9800998ecf8427e" missingok="true">
<patches>
<branch/>
</patches>
</link>
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=736719https://bugzilla.novell.com/show_bug.cgi?id=736719#c0
Summary: xdm starts but no X server is running. root have to
run Xorg manually
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: X.Org
AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com
ReportedBy: petr(a)scribus.info
QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com
Found By: ---
Blocker: ---
Created an attachment (id=467384)
--> (http://bugzilla.novell.com/attachment.cgi?id=467384)
logs from boot, xdm, X, messages
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101
Firefox/8.0
upgrade from 11.4 went smoothly. And worked correctly. Then I did some 'zypper
up' last week (inluding new nvidia drivers) and sutdown the machine. Next
monday machine booted to runlevel 5 with no xdm screen shown.
The xdm service runs "waiting for X" forever.
When I, as root, start Xorg manually from the commandline, the xdm window
appears immediately and regular user can be logged in.
Cannot see anything special in logs (attached).
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.
https://bugzilla.novell.com/show_bug.cgi?id=730111https://bugzilla.novell.com/show_bug.cgi?id=730111#c0
Summary: digikam fails to open database at startup
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: KDE4 Applications
AssignedTo: kde-maintainers(a)suse.de
ReportedBy: pierre.5933(a)gmail.com
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML,
like Gecko) Chrome/15.0.874.106 Safari/535.2
please see this bug report
https://bugs.kde.org/show_bug.cgi?id=285994
because I think kde is slower and slower I Want to use SUSE 12.1 with Gnome 3 ,
but the best, for mee, is with Digikam
and in this case during the instal it seems that 2 packages are missing
libqt4 sqlite and
libqt4 sqlite 320 bit
Could change to avoid this problem
nota : I have tried also suse 12.1 kde and Digikam , no problem for this case
but the behaviour is slower than with Gnome
Thanks
Reproducible: Always
Steps to Reproduce:
1.launch digikam
2.The information that the data base is missing
3.
Actual Results:
solved for mee because I have added manualy the 2 missing packages
Expected Results:
has to be automatic
nothing
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=739092https://bugzilla.novell.com/show_bug.cgi?id=739092#c0
Summary: pinpoint crashed when showing video background slides
on the speaker screen
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
AssignedTo: bnc-team-gnome(a)forge.provo.novell.com
ReportedBy: glin(a)suse.com
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
Reproduce steps:
1. Create a 2 page slide2 and use the video background in the 2nd page:
#!/usr/bin/env pinpoint
[background.jpg]
-- [duration=4.448699]
Page 1
-- [video.ogg] [duration=3.393199]
Page 2
2. Show the slides
$ pinpoint test.pin
3. Press F1 to activate the speaker screen and click Page 2.
Expected result:
Page 2 was showed.
Actual result:
Pinpoint segfault
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=739079https://bugzilla.novell.com/show_bug.cgi?id=739079#c0
Summary: root privileges required for wireless networking &
shutdown & suspend etc.
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
AssignedTo: bnc-team-gnome(a)forge.provo.novell.com
ReportedBy: lipkab(a)citromail.hu
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101
Firefox/9.0
Symptoms pretty similar to #728970, but I'm on a fresh GNOME installation, and
my PERMISSION_SECURITY in /etc/sysconfig/security is "easy local"
Reproducible: Always
Steps to Reproduce:
1. Close laptop lid
2. suse prompts for privileges
-or-
1. connect to (open) wifi network
2. in one minutes or two, wifi disconnects, network essid disappears from
NetworkManager
Actual Results:
first problem: can't suspend, shutdown etc my machine without password
second: can't use wifi for more than two minutes
If I switch off wifi hardware then on, the failed network essid reappears.
if /etc/polkit-default-privs.local contains
org.freedesktop.upower.suspend yes:yes:yes
org.freedesktop.upower.hibernate yes:yes:yes
org.freedesktop.login1.power-off yes:yes:yes
org.freedesktop.login1.power-off-multiple-sessions yes:yes:yes
org.freedesktop.login1.reboot yes:yes:yes
org.freedesktop.login1.reboot-multiple-sessions yes:yes:yes
org.freedesktop.NetworkManager.enable-disable-network yes:yes:yes
org.freedesktop.NetworkManager.enable-disable-wifi yes:yes:yes
org.freedesktop.NetworkManager.enable-disable-wwan yes:yes:yes
org.freedesktop.NetworkManager.use-user-connections yes:yes:yes
then wifi & suspend works fine, however, I still can't shutdown without
password
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=705213https://bugzilla.novell.com/show_bug.cgi?id=705213#c0
Summary: cannot change time adjustment policy from manual to
NTP
Classification: openSUSE
Product: openSUSE 11.4
Version: Final
Platform: x86-64
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: bluedzins(a)wp.pl
QAContact: jsrain(a)novell.com
Found By: ---
Blocker: ---
I would like to set time adjustment to be done automatically via NTP.
So I run Yast -> Date and Time -> Change -> Synchronize with NTP Server.
I can for example force synchronizing time here, but when I click [OK] I get
helpful error saying "cannot update the dynamic configuration policy".
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=679078https://bugzilla.novell.com/show_bug.cgi?id=679078#c0
Summary: If I set the sceenresolution manualy it loost after a
logout
Classification: openSUSE
Product: openSUSE 11.4
Version: Factory
Platform: VMWare
OS/Version: Windows 7
Status: NEW
Severity: Major
Priority: P5 - None
Component: X.Org
AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com
ReportedBy: MSchmidt_glz(a)gmx.de
QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.10)
Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0C) Facicons
If I chance the resolution of the screen manualy in Configure Desktop, this
resolution is loost after a logout. After a newly login the screen has always a
not correct resolution from 800x600.
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.
https://bugzilla.novell.com/show_bug.cgi?id=738701https://bugzilla.novell.com/show_bug.cgi?id=738701#c0
Summary: zypper: symbol requirements must be more weighted
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: Linux
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: jengelh(a)medozas.de
QAContact: qa(a)suse.de
Found By: Beta-Customer
Blocker: ---
from 11.4 to 12.1, this can happen:
# zypper dup
Installerer: libreadline6- 6.2-1.8.1 [fullført]
Installerer: bash- 4.2-1.8.1 [fullført]
Installerer: openSUSE-release- 12.1-1.4 [fullført]
Flere rpm-resultater:
/bin/sh: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /bin/sh)
/bin/sh: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
/lib64/libreadline.so.6)
/bin/sh: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by
/lib64/libncurses.so.5)
warning: %post(openSUSE-release-12.1-1.4.x86_64) scriptlet failed, exit status
1
Therefore, glibc should always be installed first even in a dependency cycle
(that is then willingly broken or ignored)..
--
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.
https://bugzilla.novell.com/show_bug.cgi?id=736816https://bugzilla.novell.com/show_bug.cgi?id=736816#c0
Summary: Apper authorization window does not get focus
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: SuSE Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Other
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: rlee17.inceptorus(a)gmail.com
QAContact: qa(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.10 (KHTML,
like Gecko) Chrome/17.0.945.0 Safari/535.10 SUSE/17.0.945.0
When Apper (whether using through Update or on its own) comes to ask for root
password (authorization), the authorization window does not have focus and is
often hidden behind the Apper window.
Reproducible: Always
Steps to Reproduce:
1.Launch Apper (or Update)
2.Wait for Apper to ask for Authorization
3.Authorization window can be hidden behind main Apper window
Actual Results:
The authorization window does not have focus and is often hidden.
Expected Results:
Authorization window should have focus and therefore never be hidden behind
other windows when it first appears.
--
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.