openSUSE Factory July 2011

factory@lists.opensuse.org

105 participants
103 discussions

[opensuse-factory] KDE menus and gitorious
by Cristian Morales Vega 06 Nov '12

06 Nov '12

I created a merge request for desktop-data three weeks ago. It's just a minor patch that doesn't really fix anything but a warning from kbuildsycoca4. I'm not sure about how Gitorious works, maintainers are supposed to notice the "1" in the merge requests section or they receive an email notifying it? And since I'm on it. Since I updated my 11.3 system to KDE to 4.5 the "inline" part of the menu is not honored... Expected behavior? Known problem? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 6

[opensuse-factory] Kernel for 11.4?
by Jeff Mahoney 22 Sep '11

22 Sep '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all - Since technically we're in feature freeze for 11.4, I thought I'd put this out for discussion. Factory is currently using 2.6.36 which was released 3 weeks ago. Upstream versions tend to take about 10-11 weeks, on average, to release. The scheduled release for the first openSUSE RC is Jan 20. The scheduled release for the first RC is Jan 20. The typical development time for a kernel release, on average, is about 10-11 weeks. That puts the release of 2.6.37 around Dec 29 to Jan 12. That sounds like kind of a tight window, but the reality is that the differences in the later kernel RCs tend to be small and fix bugs. The "real" development happens in -rc1, which was released about two weeks ago. Later -rcs serve to stabilize the development that went into -rc1. So, the the feature freeze aspect of it will be a one-shot, when I update to -rc1. (Actually, I hardly ever update to -rc1 and instead use - -rc2 which tends to be more stable). I've already done the merge work for 2.6.37-rc1 since the master kernel always tracks the latest upstream. Xen is the lone exception, as it usually is, but Jan Beulich has been great about getting that completed shortly after I do the update. This time might be a little more difficult because much of the Xen code has been merged into the mainline kernel so there's some sorting out to be done. As far as testing goes, we're still early enough that we won't lose a lot of effort. I'd update Factory to 2.6.37-rc2 as soon as it is released upstream, which should be this week. Our usual corps of dedicated testers can dig in quickly. In my experience, though, the number of testers drastically increases around the RC1 release. I wish it weren't so, but it is. So revving the kernel now isn't likely to toss out a lot of testing. The biggest "feature" I'm going for is not having to backport fixes from 2.6.37. The BKL removal patches and the VFS scalability patches are going to improve performance on multicore systems. The removal of I/O barriers should also be pretty noticeable but I haven't had time to verify that yet. So, opinions? - -Jeff Features that are going into 2.6.37: - - The inode portion of the VFS scalability patches - - More BKL removal, including parts of the core kernel - - Block I/O can be throttled via cgroups - - Simple pNFS support - - In-kernel PPTP (tunneling) acceleration - - "Lazy" inode table creation for ext4 to allow faster fs creation - - Batched discard support, which allows the file system to advise the block layer to use the TRIM command. This allows online TRIMs, but is only implemented in ext4 so far. - - Xen dom0 support (mostly) - - The usual round of bug fixes. - - fanotify - - Block barriers have been removed[1] Drivers: - - Systems and processors: - Flexibility Connect boards - Telechips TCC ARM926-based systems - Telechips TCC8000-SDK development kits - Vista Silicon Visstrim_m10 i.MX27-based boards - LaCie d2 Network v2 NAS boards - Qualcomm MSM8x60 RUMI3 emulators - Qualcomm MSM8x60 SURF eval boards - Eukrea CPUIMX51SD modules - Freescale MPC8308 P1M boards - APM APM821xx evaluation boards - Ito SH-2007 reference boards - IBM "SMI-free" realtime BIOS's - MityDSP-L138 and MityDSP-1808 systems - OMAP3 Logic 3530 LV SOM boards - OMAP3 IGEP modules - taskit Stamp9G20 CPU modules - aESOP Samsung S5PV210-based Torbreck boards - - Block: - Chelsio T4 iSCSI offload engines - Cypress Astoria USB SD host controllers - Marvell PXA168/PXA910/MMP2 SD host controllers - ST Microelectronics Flexible Static Memory Controllers - - Input: - Roccat Pyra gaming mice - UC-Logic WP4030U, WP5540U and WP8060U tablets - several varieties of Waltop tablets - OMAP4 keyboard controllers - NXP Semiconductor LPC32XX touchscreen controllers - Hanwang Art Master III tablets - ST-Ericsson Nomadik SKE keyboards - ROHM BU21013 touch panel controllers - TI TNETV107X touchscreens - - Miscellaneous: - Freescale eSPI controllers - Topcliff platform controllher hub devices - OMAP AES crypto accelerators - NXP PCA9541 I2C master selectors - Intel Clarksboro memory controller hubs - OMAP 2-4 onboard serial ports - GPIO-controlled fans - Linear Technology LTC4261 Negative Voltage Hot Swap Controller I2C interfaces - TI BQ20Z75 gas gauge ICs - OMAP TWL4030 BCI chargers - ROHM ROHM BH1770GLC and OSRAM SFH7770 combined ALS and proximity sensors - Avago APDS990X combined ALS and proximity sensors - Intersil ISL29020 ambient light sensors - Medfield Avago APDS9802 ALS sensor modules - Basic, memory-mapped GPIO controllers - Intel Topcliff GPIO controllers - Intel Moorestown/Medfield i2c controllers - IDT CPS Gen.2 SRIO RapidIO switches - Freescale i.MX DMA engines - ARM PrimeCell PL080 or PL081 DMA engines - Cypress West Bridge Astoria controllers - USB ENE card readers - Asahi Kasei AK8975 3-axis magnetometers - OLPC XO display controller devices - Analog Devices AD799x analog/digital converters - Winbond/Nuvoton W83795G/ADG hardware monitoring chips - Flarion OFDM usb and pcmcia modems - Maxim MAX8952 and MAX8998 Power Management ICs - National Semiconductors LP3972 PMIC regulators - Broadcom BCM63xx hardware watchdogs - - Network: - Brocade 1010/1020 10Gb Ethernet cards - Conexant CX82310 USB ethernet ports - Atheros AR9170 "otus" 802.11n USB devices - Topcliff PCH Gigabit Ethernet controllers - Intel Topcliff platform controller hub CAN interfaces - Technologic Systems TS-CAN1 PC104 peripheral boards - SBE wanPMC-2T3E3 interfaces - RealTek RTL8712U (RTL8192SU) Wireless LAN NICs (replaces older rtl8712 driver) - Atheros AR6003 wireless interface controllers - Beeceem USB Wimax adapters - Broadcom bcm43xx wireless chipsets - - Sound: - Marvell 88pm860x codecs - TI WL1273 FM radio codecs - HP iPAQ RX1950 audio devices - Native Instruments Traktor Kontrol S4 audio devices - Aztech Sound Galaxy AZT1605 and AZT2316 ISA sound cards - Wolfson Micro WM8985 and WM8962 codecs - Wolfson Micro WM8804 S/PDIF transceivers - Samsung S/PDIF controllers - Cirrus Logic EP93xx AC97 controllers - Intel MID SST DSP devices - - USB: Intel Langwell USB OTG transceivers - YUREX "leg shake" sensors - USB-attached SCSI devices - - Video4Linux2: remotes using the RC-5 (streamzap) protocol - Konica chipset-based cameras - Sharp IX2505V silicon tuners - LME2510 DM04/QQBOX USB DVB-S boxes - Samsung s5h1432 demodulators - Several new Conexant cx23417-based boards - Nuvoton w836x7hg consumer infrared transceivers - OmniVision OV6650 sensors - OMAP1 camera interfaces - Siliconfile SR030PC30 VGA cameras - Sony imx074 sensors - VIA integrated chipset camera controllers - -Jeff [1] This is because they were a very big hammer that had a reputation for killing performance. They're necessary for safely using journals on devices with write caching enabled, but were implemented by flushing the entire I/O queue to physical media -- not just "to disk" which includes the disk's write cache. The new implementation will still use the flush-to-media feature but will not stall the i/o queue. - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkzhW0YACgkQLPWxlyuTD7JgBACbBfR+uJwfKKnEcBZIg/KeIj/S hikAnRiL9nG50QoKZkrn1AsmGljnGvYn =T/Hp -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

15 33

[opensuse-factory] IPV6 privacy in openSUSE
by Andreas Jaeger 13 Sep '11

13 Sep '11

I wonder whether our IPv6 settings are the right ones after reading the following article (sorry, German only): http://www.heise.de/newsticker/meldung/IPv6-Smartphones-gefaehrden-Privatsp… which references: http://www.heise.de/netze/hotline/IPv6-anonym-1100727.html We set use_tempaddr to 0 by default (disabling privacy extensions) and set it to 1 if enabled. The article advises to use 2. Background: By default (value 0) my IPv6 address will be derived from my hardware (macaddr) and therefore be the same independend how I connect to the internet. So, it's easy to track my computer... So, my proposal is to do the following two changes: * Use 2 instead of 1 in /etc/rc.d/boot.ipconfig for enabling the privacy extensions * Set IPV6_PRIVACY=yes in /etc/sysconfig/sysctl Any concerns with this change? Btw. here's an Ubuntu bugreport: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/176125 and Windows (since XP) is doing it the same way on desktops. Andreas -- Andreas Jaeger, Program Manager openSUSE, aj(a){novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

7 6

[opensuse-factory] Request for new project devel:languages:ocaml
by Andrew Psaltis 19 Aug '11

19 Aug '11

Objective Caml (OCaml) [1] is a multiparadigm language in the ML family of languages. OCaml is itself already in the openSUSE distribution, located in devel:languages:misc. I have located three other packages that use it: - lablgtk2 (in devel:languages:misc) - ocaml-facile (in KDE:Distro:Factory) - unison (in network) I have recently submitted a large patch to the ocaml package in devel:languages:misc, and I have 25 other OCaml library packages in my home project, accumulated over the last several months [2]. Upon approval, I will submit them there, excluding camlimages, which currently has a build problem on 64-bit architectures. Since there are already a large number of OCaml packages in Fedora, I have modified various spec files from there when packages from there already exist. Those that were derived from fedora are marked as such. The Fedora Contributor License Agreement [3] permits users to re-license them as seen fit. All spec files are placed under the MIT license, unless there was already a license upon them (as was the case with the ocaml package, which came from SUSE itself). As for packaging guidelines, I have attempted to follow those specified by the Fedora project [4]. As such, they tend to conform to whatever specifications that rpmlint uses. Furthermore, to ensure that inter-package dependencies resolve correctly, I have enabled the internal dependency generator on builds that were on openSUSE distributions before the current Factory build. Doing such enables features that essentially match what ocaml.attr does in RPM 4.9. ~Andrew [1] http://caml.inria.fr/ [2] https://build.opensuse.org/project/show?project=home:NaCl:ocaml [3] http://fedoraproject.org/wiki/Legal:Licenses/CLA [4] http://fedoraproject.org/wiki/Packaging:OCaml

3 8

[opensuse-factory] deprecation of xulrunner packages
by Wolfgang Rosenauer 18 Aug '11

18 Aug '11

Hi, because xulrunner as a stable platform is basically dead with Mozilla's new rapid release cycle we more or less need to remove the packages from Factory. This includes: mozilla-xulrunner192 mozilla-xulrunner20 Version 2.0 is already out of upstream support while 1.9.2 will live for some more weeks (not exactly sure for how long). According to OBS the following packages are still depending on these: mozilla-xulrunner192: google-gadgets libgluezilla0 libreoffice libreoffice-bootstrap libreoffice-components libreoffice-libs-extern moonlight moonshine mozilla-xulrunner20: PackageKit bundle-lang-gnome-extras chmsee icedtea-web libproxy-plugins rhythmbox There are probably only JS engine consumers (libproxy-plugins?) which should have a replacement already in Factory with the js package? Then there are NPAPI only consumers I guess which just need some header files? What else do those packages need? That's important to me to find out what exactly we need to provide in Factory to be able to remove the full xulrunner packages. Also if some package is missing in the above list for whatever reason, please let me know. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

5 9

[opensuse-factory] Integration of firewalld?
by Vincent Untz 09 Aug '11

09 Aug '11

Hi, I wonder: did anybody look at integrating firewalld (a firewall service daemon with D-BUS interface managing a dynamic firewall), or proposing a similar dbus API for what we have? I'm starting to see some applications making use of the dbus API, and it does improve user experience to have that. https://fedoraproject.org/wiki/FirewallD/ https://fedorahosted.org/firewalld/ Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

11 49

[opensuse-factory] inconsitent logfile permissions, logrotate
by Ruediger Meier 05 Aug '11

05 Aug '11

Hi, today I've noticed inconsistencies with logfile permissions and logrotate which leads me to think about a feature request. For example /var/log/localmessages seems to be created at installation time with 0644 root:root But the first log rotation changed this to 0640 and my users complained about that. The permission change is caused by /etc/logrotate.d/syslog: .... /var/log/warn /var/log/messages /var/log/allmessages /var/log/localmessages /var/log/firewall /var/log/acpid /var/log/NetworkManager { [...] create 640 root root [...] } So there are at least two places where these permissions are defined, one at installation time and the other in /etc/logrotate* Since "man logrotate" says: create mode owner group [...] Any of the log file attributes may be omitted, in which case those attributes for the new file will use the same values as the original log file for the omitted attributes. I would suggest to change logrotate config from "create 640 root root" to just "create" and to track these logfiles within /etc/permissions* too. This would make things more generic, simple and consistent. What do you think? cu, Rudi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 3

[opensuse-factory] Dell XPS1730 problem after Dup
by Bruce Ferrell 31 Jul '11

31 Jul '11

I can boot into safe mode but not into regular 3.0.0-38. I have an Nvidia video subsystem and what happens is the LCd seems to go into some sort of test mode flashing black, then red, green, then blue then white. Any suggestions? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

3 2

[opensuse-factory] Internal modem no longer works in 11.4 nor factory
by dt30 29 Jul '11

29 Jul '11

I have a modem on 11.2 (I've been trying to use 11.4 for the last several months but need the modem to work): 03:06.0 Communication controller [0780]: Agere Systems Venus Modem (V90, 56KFlex) [11c1:0480] Subsystem: Actiontec Electronics Inc Device [1668:0500] Flags: bus master, medium devsel, latency 0, IRQ 21 Memory at febffc00 (32-bit, non-prefetchable) [size=256] I/O ports at e800 [size=256] I/O ports at e400 [size=256] I/O ports at ec00 [size=8] Capabilities: [f8] Power Management version 2 Kernel driver in use: serial which works on /dev/ttyS4 in 11.1, 11.2, 11.3, but no longer works in 11.4 nor factory. Neither wvdial nor wvdialconf ran as root can find the modem at /dev/ttyS4: wvdialconf: Editing `/etc/wvdial.conf'. Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan<*1>: S1 S2 S3 ttyS4<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS4<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS4<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan<*1>: S5 S6 S7 When I used the program, minicom, on ttyS4 in 11.4, it could use the modem, dial, and actually connected. But neither wvdial nor wvdialconf could find it. I tried a different modem: 03:06.0 Modem [0703]: Broadcom Corporation BCM4212 v.90 56k modem [14e4:4212] (rev 02) (prog-if 00 [Generic]) Subsystem: Dell Device [1028:0001] Flags: bus master, fast devsel, latency 64, IRQ 21 Memory at febff000 (32-bit, non-prefetchable) [size=4K] I/O ports at ec00 [size=16] Capabilities: [40] Power Management version 2 Kernel driver in use: serial with no luck on 11.2 nor 11.4 of Opensuse nor with minicom, but it appears that may be a different issue with Broadcom modems. I've asked in the forums and after trying several things, it was suggested I ask here to see if the next release could support it if I'm not overlooking something. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

2 1

Re: [opensuse-factory] Internal modem no longer works in 11.4 nor factory
by dt30 29 Jul '11

29 Jul '11

On 07/29/2011 05:04 PM, Donn Washburn wrote: > Try hwinfo --modem and get the correct /dev/. This one is ttyS4 > Then try "minicom --help" and set it with -D. Some else is like going > to give you a problem is ppp. As I remember it needs a chmod operation > And have you run Yast2 > Hardware > modem Ok, I tried it with these results: 11:2 hwinfo --modem 45: Serial 00.0: 10200 Modem [Created at modem.447] Unique ID: 4gcD.KM1shMXflFC Parent ID: GiVB.3fyvFV+mbWD Hardware Class: modem Model: "AT Modem" Vendor: int 0x2000 "Unknown" Device: int 0x0001 "AT Modem" Device File: /dev/ttyS4 Device Files: /dev/ttyS4, /dev/char/4:68 Speed: 115.2 kbps Init1: ATZ Init2: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #36 (Serial controller) 11:4: hwinfo --modem 45: Serial 00.0: 10200 Modem [Created at modem.447] Unique ID: 4gcD.KM1shMXflFC Parent ID: GiVB.3fyvFV+mbWD Hardware Class: modem Model: "AT Modem" Vendor: int 0x2000 "Unknown" Device: int 0x0001 "AT Modem" Device File: /dev/ttyS4 Speed: 115.2 kbps Init1: ATZ Init2: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #36 (Serial controller) Notice the line which isn't in 11.4: Device Files: /dev/ttyS4, /dev/char/4:68 I checked and there is a device at /dev/char/4:68 on each one. I don't know want to make of it, though, other than there is finally a difference discovered. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

1 0

2023

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 2011