October 2012 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] kernel panic listed on openSUSE-NET-x86_64-Build0123
by doiggl＠velocitynet.com.au 29 Oct '12

29 Oct '12

Hello, I saw this on openqa kernel panic listed on openSUSE-NET-x86_64-Build0123 http://openqa.opensuse.org/viewimg/openqa/testresults/openSUSE-NET-x86_64-B… http://openqa.opensuse.org/viewimg/openqa/testresults/openSUSE-NET-x86_64-B… Glenn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Can't boot 12.3 GNOME live CD
by Jon Cosby 29 Oct '12

29 Oct '12

I can't boot to the Gnome live CD for 12.3. I can't even do a media check, it stops at the line "sr 2:0:0:0 Attached scsi generic sg1 type 5." Booting to Gnome, I only get as far as the green wallpaper and wait 10-15 minutes, but it goes no further. It seems to quit, looking at my CPU monitor. I'm trying to run 12.3 in VirtualBox OSE with 1536MB RAM. The image passes the checksum. Are there any known issues with this? Jon Cosby -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 13

[opensuse-factory] mkinitrd failure
by Sid Boyce 29 Oct '12

29 Oct '12

/lib/mkinitrd/setup/02-start.sh: line 21: test: !=: unary operator expected Bug #787085 submitted. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] KDM: /usr/share/kde4/apps/kdm/themes/ is not the 'real' path.
by Oddball 29 Oct '12

29 Oct '12

Hi, Yast has another default path that it uses, because in /usr/share/kde4/apps/kdm/themes/ Are all the themes that can not be selected, so which path is used, instead of the standard? That is probably also the reason why the System manager > Login screen does not work. There is an extreme ugly theme that replaces the 'default' openSUSE theme, no matter what theme is selected. -- Have a nice day, Oddball. OS: Linux 3.7.0-rc2-1-desktop i686 Huidige gebruiker: oddball@EeePc-Rob-SFN9 Systeem: openSUSE 12.2 (i586) KDE: 4.8.5 (4.8.5) "release 2" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 1

[opensuse-factory] Re: [opensuse-kernel] kernel panic listed on openSUSE-NET-x86_64-Build0123
by Cristian Rodríguez 28 Oct '12

28 Oct '12

On 28/10/12 15:22, Bruno Friedmann wrote: > On Saturday 27 October 2012 12.52:14 Cristian Rodríguez wrote: > Same here, one factory vm is lost then :-( > Desktop loss here.. ;) laptop comes handy in this case, I have no idea why this happends, I tried stracing mkinitrd but apparently didnt try hard enough .. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] checking for glib >= 1.2.0... Package glib was not found in the pkg-config search path.
by Ilya Chernykh 28 Oct '12

28 Oct '12

I've got the following error: checking for glib >= 1.2.0... Package glib was not found in the pkg-config search path. Perhaps you should add the directory containing `glib.pc' to the PKG_CONFIG_PATH environment variable No package 'glib' found This is the relevant configure section: echo $ECHO_N "checking for glib >= 1.2.0... $ECHO_C" >&6 if $PKG_CONFIG --exists "glib >= 1.2.0" ; then echo "$as_me:$LINENO: result: yes" >&5 echo "${ECHO_T}yes" >&6 succeeded=yes -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] file appears on http://download.opensuse.org/factory/iso/ but not tested on openqa
by doiggl＠velocitynet.com.au 28 Oct '12

28 Oct '12

Hello, File[1] appears on [2] but not tested on openqa[3], is something busted ? -Glenn [1]File: openSUSE-NET-x86_64-Build0127-Media.iso 28-Oct-2012 05:39 253M [2] http://download.opensuse.org/factory/iso/ [3] http://openqa.opensuse.org/results/?sort=-7&hours=96&match= -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Introducing Sawfish WindowManager to Factory
by Togan Muftuoglu 27 Oct '12

27 Oct '12

Hi, Shortly I wil be submitting sawfish and its required libraries for Factory inclusion, hence some background info. I have inherited the package maintenance from Vincent Untz [1][2] and the development is now in X11:windowmanagers taking place. Sawfish {3] is an extensible window manager using a Lisp-based scripting language. Its policy is very minimal compared to most window managers. Its aim is simply to manage windows in the most flexible and attractive manner possible. All high-level WM functions are implemented in Lisp for future extensibility or redefinition. These are some of the features that set Sawfish apart from other window managers: Powerful key-binding: Virtually every function provided by Sawfish can be bound to keys (or mouse buttons). Event hooking: For many events (moving windows etc.) you can customize the way Sawfish will respond. Window matching: When windows are created you can match them to a set of rules and automatically perform actions on them. Flexible theming: Sawfish allows for very different themes to be created and a variety of third-party themes are readily available. Sawfish can be used as the windowmanager for the following desktop environments KDE, GNOME Togan [1]<http://lists.opensuse.org/opensuse-packaging/2012-05/msg00179.html> [2]<http://lists.opensuse.org/opensuse-packaging/2012-05/msg00191.html> [3]<http://sawfish.wikia.com/> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Helping Coolo
by Cristian Morales Vega 27 Oct '12

27 Oct '12

Since I am not it Prague any more. My POV about the "Release Schedule Discussion". Basically people mostly cares about his particular work, and not about the distribution as a whole. The work in the distribution as a whole is left to Coolo and few more people. Since what we need is more people to look at it, some problems/things to do: - Make https://build.opensuse.org/project/status?project=openSUSE%3AFactory the homepage of more people Too many clicks are required to reach the Factory status page. It's like if someone wanted to hide it. Not that I think it actually makes such a difference, but we should try to make it more visible. But the big problem is that it takes 30+ seconds to load it. Sometimes I actually don't look at it just because I don't want to wait. There is nothing that can be done about it? Caching? Make it fast and visible and more people will know about Factory status. The essential first step to get people to help. - Make people want to work on the problems Now I already loaded the Factory status page. I look at the list and I usually find two kind of entries: the ones that are so important that I am sure somebody else is already working on it (or is already fixed but lacks a rebuild), and the ones I don't care about. I mean, yast2-network has been failing to build for 11 days??? It can't actually be true, is it? And if it is for sure it's just because it's a complex problem, but somebody has been working on it for 10 days. I guess something similar is happening with libreoffice. But "qutim"? Yet another instant messenger? It's the first time I listen about it. I just can't find the motivation to look into it. For the first problem we need some easy and visible way to see if somebody else already took responsibility to fix a problem. Without this people just doesn't help because they don't think their help is needed. The Factory status page needs an extra column with the name of the person working on the problem. For the second problem we need a defined policy for dropping packages. If a package doesn't build for a long time and nobody fixes it... well, just drop it. It's clear nobody cares enough. I am sure it could be improved, but let's say: "If a package doesn't build for 30 days mark it for dropping. Announce it, with a list of all the current packages marked for dropping everywhere. Send the announcement to -factory/-packaging. Put it in news.opensuse.org. Have it in the forums so users also now. Perhaps let forum users vote for the packages they actually care. If after 60 days it still fails to build the package gets dropped, with also an announcement." - Inform maintainers when their update breaks other packages Sure, perhaps the kernel maintainer doesn't care if an out-of-tree module breaks. But some people *may* actually care if their update of a library breaks an application. Let's send an automatic email to them. If they don't care they will just ignore the email, if they care... great! I guess it's not so obvious to automatically know what package broke another one. But we can know the problem was caused by a package in a subset, at the very least "the whole list of modified packages". -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 20

[opensuse-factory] 12.3 m0, observations
by Patrick Shanahan 26 Oct '12

26 Oct '12

although it *is* configured, restarting/rebooting in kde does *not* restore previous applications/windows. bug report ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1