openSUSE Factory July 2010

factory@lists.opensuse.org

118 participants
93 discussions

[opensuse-factory] Re: [opensuse-project] Logging related

by Per Jessen

"Horváth Gergely J. (Ottó)" wrote: > I have done a little research among distributions, to have a bigger > perspective, and based on that, I have some ideas and questions. More > important ones first: > > * OpenSUSE should log auth and authpriv messages separately (like > "all" other distributions do). > > We certainly can not start a great debate on what to log and where, > but I would like to mention some other points too: > > * OpenSUSE does not log crond messages separately (while nearly "all" > other ditros do). Note: This might seem like a "what to log separately > and what not to" question, but considering mail as a general service > and thus logging it in a separate file - in contrast to crond - make > me think of an advise: "Add a filter to crond if you plan to use that > special service a lot - thus spamming your messages log file" :) > > * Logging some messages to other files, should not we filter them out > from messages? (I did not check this one, it might be daemon specific > (like ntp), but one with a deeper insight could check it). With a few excpetions, I find the current syslog settings to be quite good. For desktops and laptops, I don't touch them, for servers, I have one or two standard modifications. Overall, an optimal syslog setup depends entirely on what a system is used for. wrt your suggestions - I would prefer keeping crond messages in /var/log/messages - on a default system I don't see enough crond activity to warrant a separate file. (but there is already a commented out entry in syslog-ng.conf). Log auth and authpriv separately - yeah, why not. Filtering out messages from /var/log/messages if logged elsewhere - it's already being done for some, e.g. firewall. To me, that depends mostly on volume and somewhat on purpose. Logging changes I usually do for a production system: disable separate logging for mail.<level>, disable separate logging for news.*, amend logrotate for our log archiving, to use lzma compression and to run at midnight. -- Per Jessen, Zürich (23.9°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

[opensuse-factory] Re: [opensuse-buildservice] Can we please get ARM builds for 11.3+1?

by Jimmy Pierre

>>Naming of the next release is a separate discussion we might have. I'm opposed to both 11.4 and 12.0 and look forward to great proposals openSUSE 2.0 ? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

[opensuse-factory] Name for next release [WAS: Re: [opensuse-buildservice] Can we please get ARM builds for 11.3+1?]

by Greg Freemyer

On Fri, Jul 2, 2010 at 11:05 AM, Andreas Jaeger <aj(a)novell.com> wrote: > On Friday 02 July 2010 16:56:04 Thomas Schmidt wrote: > >> Shouldn't we call this 12.0? >> Reassigning the features afterwards would be additional work. > > Naming of the next release is a separate discussion we might have. I'm > opposed to both 11.4 and 12.0 and look forward to great proposals, > > Andreas "Armchair", because working with the next openSUSE release will be so relaxing. Everything just works! Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

[opensuse-factory] pulse audio: pavucontrol - _still_ missing icons on KDE4 desktop

by madworm_de.novell＠spitzenpfeil.org

Same as: http://bugzilla.novell.com/show_bug.cgi?id=555600 Installed from: openSUSE-KDE-LiveCD-Build0694-i686.iso Are those icons just missing or is it a dependency problem? There's got to be 2 icons sitting somewhere waiting to be used. R. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

[opensuse-factory] perl_bootloader

by Günther J. Niederwimmer

Hello, is this a known problem Warning: GRUB::GrubDev2UnixDev: No partition found /dev/md126 with 12627? I installed a fresh RC2 in a Intel Raid1 System, I installed before WIN7 on this system. By installing, a message for Intel Matrix System is popup, I say yes to the question, Install. -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

[opensuse-factory] build 694 results in rc1

by Dale Ritchey

I downloaded openSUSE11.3 rc2 from software.opensuse.org: Download openSUSE 11.3 RC2 <http://software.opensuse.org/developer/en> checked the md5sum 82bec376aa27e622a2c01cec531dddd9 /dist/install/openSUSE-11.3-RC2/iso/Build0694/openSUSE-DVD-Build0694-i586.iso did a isohybrid openSUSE-DVD-Build0694-i586.iso dd to usb stick installed from stick and the result was openSUSE 11.3rc1 reguiring a multi gig update to get to rc2?? Dale Intel Atom n270 graphics Moile 945GM/GMS/GME, 943/940GML integrated graphics controller -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

[opensuse-factory] Critical RC2 bug: quitting quadrapassel kills x-server

by Atri Bhattacharya

Hi! Could someone test this bug https://bugzilla.novell.com/show_bug.cgi?id=617651 with Gnome in RC2 and confirm if he/she can see it regularly too? Also I don't understand clearly what a "shipstopper" means, but if this crash is indeed so clearly reproducible and brings down X every time, would this be a shipstopper? Thanks -- Atri -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

[opensuse-factory] Unable to launch Firefox after upgrade to 3.6.6

by Rastislav Krupanský

Hi all. I can´t launch Firefox after upgrade to 3.6.6-1.2 in RC2 from Mozilla repository. Command line gives me output: Couldn´t load XPCOM Could you please verify, whether it works for you after upgrade and it´s worth filling a bug? Thanks a lot. -- S pozdravom / Best regards, Rasto -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

Re: [opensuse-factory] Two Huawei modems fail the same way

by Bin Li

HI, So does each one works fine lonely? >>> Vahis 06/30/10 2:22 AM >>> I have Two Huawei sticks, E169 and E160. Both work fine in 11.2 (already got them to work in 11.0) When plugged into 11.2 VBox host they both work fine, both in XP and W7 guests. But in 11.3 factory guest they both fail. Here's a few lines from messages: ***************************** Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.604386] usb 1-1: new high speed USB device using ehci_hcd and address 6 Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.852392] usb 1-1: New USB device found, idVendor=12d1, idProduct=140c Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.852396] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0 Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.852408] usb 1-1: Product: HUAWEI Mobile Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.852417] usb 1-1: Manufacturer: HUAWEI Technology Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.864049] option 1-1:1.0: GSM modem (1-port) converter detected Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.864286] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0 Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.864501] option 1-1:1.1: GSM modem (1-port) converter detected Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.864568] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1 Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.864736] option 1-1:1.2: GSM modem (1-port) converter detected Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.864831] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2 Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.865836] option 1-1:1.3: GSM modem (1-port) converter detected Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.866321] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3 Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.868435] scsi270 : usb-storage 1-1:1.4 Jun 29 20:50:59 a88-112-18-38 kernel: [ 7712.873061] scsi271 : usb-storage 1-1:1.5 So they get recognized, but then there's a problem, this comes first: Jun 29 20:51:00 a88-112-18-38 modem-manager: (Huawei): (ttyUSB2) deferring support check Jun 29 20:51:00 a88-112-18-38 modem-manager: (Huawei): (ttyUSB3) deferring support check Jun 29 20:51:00 a88-112-18-38 modem-manager: (Huawei): (ttyUSB1) deferring support check Then this: Jun 29 20:51:00 a88-112-18-38 udevd-work[23391]: exec of program '/lib/udev/' failed Jun 29 20:51:00 a88-112-18-38 udevd-work[23394]: exec of program '/lib/udev/' failed Jun 29 20:51:00 a88-112-18-38 udevd-work[23393]: exec of program '/lib/udev/' failed Jun 29 20:51:00 a88-112-18-38 udevd-work[23396]: exec of program '/lib/udev/' failed Jun 29 20:51:01 a88-112-18-38 udevd-work[23405]: exec of program '/lib/udev/' failed So they get recognized but they "defer support check". Apparently because "udev fails". Unfortunately I haven't tried them between 11.2 and current factory so I don't know if this has been there all the way thru milestones, sorry for that. Any ideas anybody? Vahis -- http://waxborg.servepics.com openSUSE 11.2 (x86_64 2.6.31.12-0.2-default 21:15pm up 17 days 5:47, 12 users, load average: 0.64, 0.29, 0.28 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

[opensuse-factory] RFT: upgrade from 11.2 to M7 via wagon

by Greg Freemyer

All, in addition to "zypper dup", "yast2 wagon" is a supported dist upgrade path. (Or it was for 11.1 to 11.2) I don't have a 11.2 machine I want to move to factory right now, so I tried to upgrade a test machine from M3 to M7 via "yast2 wagon" and it segfaulted half way thru. (wagon is a gui tool to handle "yast2 dup") see http://en.opensuse.org/Wagon https://bugzilla.novell.com/show_bug.cgi?id=613820 The wagon version from 11.3 M3 first upgraded itself to M7 and then started the actual distribution upgrade. I don't know if the version in 11.2 does that or not. Since Wagon is a supported upgrade tool, it really needs to work before the general release, but I don't have a good way to test it. I marked the bug major, but if it also occurs with 11.2, I think it should be critical. And if it doesn't then likely it is just a normal bug for 11.3 at this point. Note: I'm not the author. I was just testing. Thanks Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

12 years

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory July 2010