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
-----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
openSUSE 11.3 on one box and openSUSE 11.4 Milestone 4 on the other.
I have a message that says the built modules not found. When I check
e.g /lib/modules/2.7.37-rc3-git7-smp, most modules are zero bytes long.
I have to "make modules_install" and use modprobe on each.
To get the network up on the 11.3 box "modprobe r6189" then "rcnetwork
restart", "modprobe rtl8187", "/etc/init.d/network-remotefs start",
etc., etc.
Then ifconfig is OK for those devices.
eth_s1_0 Link encap:Ethernet HWaddr 00:1C:F0:BB:14:E1
inet addr:192.168.10.10 Bcast:192.168.10.255 Mask:255.255.255.0
inet6 addr: fe80::21c:f0ff:febb:14e1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1927 errors:0 dropped:0 overruns:0 frame:0
TX packets:1923 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:287532 (280.7 Kb) TX bytes:283044 (276.4 Kb)
Interrupt:17 Base address:0xe000
wlan0 Link encap:Ethernet HWaddr 00:15:AF:23:04:37
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::215:afff:fe23:437/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4324 (4.2 Kb) TX bytes:18470 (18.0 Kb)
On 11.3 module-init-tools-3.12-1.3.x86_64
On 11.4 Milestone 4 module-init-tools-3.12-5.3.x86_64
tindog:/usr/src/linux-2.6.37-rc3-git7 # grep MODULE .config
CONFIG_MODULES=y
# CONFIG_MODULE_FORCE_LOAD is not set
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODULE_SRCVERSION_ALL=y
Another guy has emailed me saying he's seen the same.
11.3
====
gcc version 4.5.0 20100604 [gcc-4_5-branch revision 160292] (SUSE Linux)
11.4 Milestone 4
================
gcc version 4.5.1 20101116 [gcc-4_5-branch revision 166793] (SUSE Linux)
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
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I know the rescue option in the dvd had to be dropped. Too problematic,
and no maintainer.
Could some of it be "rescued"?
The thing that fails most is grub. Just a repair grub, perhaps a repair
missing kernel/initrd?
Once the system boots, the user should be able to repair the rest (hope).
:-)
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
iEYEARECAAYFAkyodsMACgkQtTMYHG2NR9W3mACeL4xQWJevZF3nzSzbYWKtz3dP
yQMAnjtrUrfJRGrGfoyEouiJN6Q2XH37
=T2Uo
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I'd like to add two packages to Factory, libdbi and libdbi-drivers. Both
were already available in Contrib, moving them to factory would enable
me to add database support to syslog-ng.
URL : http://libdbi.sourceforge.net/
Summary : Database Independent Abstraction Layer for C
Description :
libdbi implements a database-independent abstraction layer in C, similar
to the
DBI/DBD layer in Perl. Writing one generic set of code, programmers can
leverage the power of multiple databases and multiple simultaneous database
connections by using this framework.
And libdbi-drivers provides the actual drivers for different databases
(sqlite3, mysql, pgsql).
Both packages were around for a very long time and worked without any
problems so far.
I tested it with syslog-ng and logging to database worked fine using
libdbi and libdbi-drivers.
Bye,
--
Peter Czanik (CzP) <czanik(a)balabit.hu>
BalaBit IT Security / syslog-ng upstream
http://czanik.blogs.balabit.com/
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hi,
I have to handle a (now outdated) diskless openSUSE 11.1 desktop
installation of about 30 systems in a company network. One of the
customizations is Firefox 3.6.12 from the mozilla repo, consisting of
MozillaFirefox-3.6.12-1.2, mozilla-xulrunner192-1.9.2.12-1.2, ...
Kernel is a 2.6.31.13 also based on the openSUSE trees on gitorious.
Unfortunately, I'm getting complains of Firefox crashing often during
the day without any user interaction, just displaying occasionly
updated sites (without flash content), and I do suffer from these
crashes, too.
A few data points:
Previous versions from that repo doesn't show this behavior.
In that installation, only Firefox, flash and acrobat reader were
updated lately, everything else was being kept as is for a few month
running (rock solid!), therefor I can say, that this problem is
triggered by changes in firefox related packages.
For the record, these are the latest changes:
acroread-9.4-0.1.1 Di 16 Nov 2010 13:50:26
flash-player-10.1.102.64-0.1.1 Di 16 Nov 2010 13:48:57
MozillaFirefox-translations-common-3.6.12-1.2 Di 16 Nov 2010 13:37:12
MozillaFirefox-3.6.12-1.2 Di 16 Nov 2010 13:37:07
mozilla-kde4-integration-0.6.2-14.2 Di 16 Nov 2010 13:37:05
mozilla-xulrunner192-translations-common-1.9.2.12-1.2 Di 16 Nov 2010
13:37:03
mozilla-xulrunner192-1.9.2.12-1.2 Di 16 Nov 2010 13:36:59
libnsssharedhelper0-1.0.9-1.8 Di 16 Nov 2010 13:36:49
mozilla-nss-3.12.8-4.1 Di 16 Nov 2010 13:36:48
libsoftokn3-3.12.8-4.1 Di 16 Nov 2010 13:36:47
mozilla-js192-1.9.2.12-1.2 Di 16 Nov 2010 13:36:46
mozilla-nss-certs-3.12.8-4.1 Di 16 Nov 2010 13:36:45
libfreebl3-3.12.8-4.1 Di 16 Nov 2010 13:36:44
mozilla-nspr-4.8.6-1.1 Di 16 Nov 2010 13:36:41
gpg-pubkey-ee454f98-4c58185b Di 16 Nov 2010 13:35:37
gpg-pubkey-766da614-4c57f9d9 Di 16 Nov 2010 13:35:26
gpg-pubkey-1abd1afb-4c97c60c Di 16 Nov 2010 13:34:54
gpg-pubkey-7c99e700-4c4eba16 Di 16 Nov 2010 13:34:46
Last night, I've kept Firefox running under gdb control with just the
build system monitor (where I was logged in) and a few of my project
pages. The only "active" content was the monitor page occasionly
updating. Today, I found:
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0xb43ffb90 (LWP 8683)]
0xffffe424 in __kernel_vsyscall ()
(gdb) bt
#0 0xffffe424 in __kernel_vsyscall ()
#1 0xb7f9e078 in send () at ../sysdeps/unix/sysv/linux/i386/socket.S:97
#2 0xb77b7b4e in pt_Send (fd=0xa580c740, buf=0xa583c000, amount=23,
flags=0, timeout=4294967295) at ptio.c:1931
#3 0xb63ee34c in ssl_DefSend (ss=0xa56f3000, buf=0xa583c000 "\025\003",
len=23, flags=0) at ssldef.c:128
#4 0xb63dd155 in ssl3_SendRecord (ss=0xa56f3000, type=<value optimized
out>, pIn=0xb43feffa "\001", nIn=2, flags=0)
at ssl3con.c:2280
#5 0xb63dd696 in SSL3_SendAlert (ss=0xa56f3000, level=alert_warning,
desc=<value optimized out>) at ssl3con.c:2535
#6 0xb63f2a12 in ssl_SecureClose (ss=0xa56f3000) at sslsecur.c:1067
#7 0xb63f7b77 in ssl_Close (fd=0xab2a9020) at sslsock.c:1570
#8 0xb6cf2ecc in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#9 0xb6ce2fd4 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#10 0xb6cf009e in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#11 0xb779c341 in PR_Close (fd=0xab2a9020) at priometh.c:136
#12 0xb668e284 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#13 0xb668ea6e in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#14 0xb6691c31 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#15 0xb669219a in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#16 0xb66922d8 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#17 0xb6f41716 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#18 0xb6f100a2 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#19 0xb6691d8e in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#20 0xb6f41772 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#21 0xb6f1000c in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#22 0xb6f41ebf in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so
#23 0xb77ba551 in _pt_root (arg=0xb7a565e0) at ptthread.c:228
#24 0xb7f971b5 in start_thread (arg=0xb43ffb90) at pthread_create.c:297
#25 0xb7d0162e in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Does this rings a bell for somebody? Any advice, how to circumvent this
problem?
Thanks in advance,
Pete
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
Hello,
I prepared updated syslog-ng packages with the close supervision of
Marius Tomaschewski, the maintainer of the syslog-ng package. They are
available in home:czanik in the openSUSE BS. I would like to see these
packages included in Factory, to replace the ancient 2.0 syslog-ng, but
MT seems to have disappeared (no response to e-mails in the past two weeks).
Questions:
- it works fine on my machines, but could anybody else test it?
- what is the proper way to get syslog-ng updated in factory, if the
maintainer seems to be unavailable?
- I have now both 3.0 and 3.1 packages there, called syslog-ng and
syslog-ng31. The ultimate goal is to include 3.1. Should I drop the
current syslog-ng package and rename syslog-ng31 to syslog-ng?
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all -
I haven't seen this topic come up in a while, so I'd like to start a new
discussion about it.
I understand the reasons we don't install Codecs with openSUSE - we
don't have licenses for them, they may be patent encumbered, blah blah..
but we also have infrastructure for other data and software that have
similar conditions. We can help the user find what they need even if we
can't distribute it ourselves.
So, we already pull in flash player. We already pull in the MS TrueType
fonts. We already provide infrastructure to automatically locate and
install firmware for several devices that require firmware that can't be
freely redistributed.
So why is it that we don't offer something similar for codecs? I have
friends that are eager to install openSUSE on their machines -- not even
techies -- because they are sick of all the crap they have to put up
with on Windows when all they really want to do is browse the web, read
their email, listen to some music, laugh at some funny flash animations,
watch youtube or other downloaded videos. The expressions on their faces
when I spend 15 minutes setting up the system to install are pretty
neutral - it's pretty easy. The expressions on their faces when they see
how many ridiculous hoops I need to jump through to configure the
Packman repository and then replace the codecs changes to exasperation
when I tell them the reason I had to do all that was only so that they
could listen to their MP3s or watch some video. Sure, some of them are
interested peripherally in the reasons why I have to do that, but most
people have a nervous laugh wondering if everything they're going to be
doing with the system is going to be this hard.
So -- since we KNOW the the Packman repository contains all the plugins
necessary to make gstreamer work as everyone sane expects, can we please
do something about automating this?
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkzm1eMACgkQLPWxlyuTD7IVsgCbBvlXnk6r2m1rNouflxrORGt+
A7oAniVhbA+zQUXe9pQ4C5UV+S5UuD/o
=RYVK
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
In 11.3 it was unnecessary to suspend pulseaudio for jackd to have
access to sound devices, it's back to the old way now, needing.
"pasuspender -- /usr/bin/jackd"
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
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org
