[opensuse] 13.1 boot time/shutdown
Hi, let me first cite from another mail on the opensuse lists.
On the flipside, I own a machine that boots so fast, every time I change the branding package for Plymouth, I need to build a second version with enforced delays to purposefully slow the boot process down in order to test whether or not the changes I've made are working, because normally plymouth is finished and X is launching before my LCD has changed it's resolution from Grub2 to Plymouth.. so in my case, Plymouth is actually adding needless seconds to my boot process and causing more flickers than if it wasn't there
But as wolfgangs reply shows, my situation is not universal.
If someone steps up and maintains it, great
Wolfgang - have you installed systemd-analyze and run "systemd-analyze blame" and "systemd-analyze plot > output.svg" to get a picture of what is taking so long on your boot?
So now I completely replaced my hardware with a very powerful completely new one. Latest Intel core i5 Haswell + SSD. No software raid anymore. Just a very simple setup with one disk. And I'm still really wondering how you can boot that fast. My boot time is regularly still 45 seconds (almost exactly the same as with my old hardware). Hygiea:~ # systemd-analyze blame 30.883s systemd-udev-settle.service 5.825s network.service 5.427s network@enp0s25.service 3.034s cifs.service 1.000s systemd-vconsole-setup.service ... What is this systemd-udev-settle.service doing? Nobody could tell me so far. Could it be related to USB devices? I have some of them connected which have card readers attached. The network service also is a bit strange given that it is a static configuration. In the log file the big pause looks like this: 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.514367] sd 7:0:0:1: Attached scsi generic sg5 type 0 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.606936] sd 7:0:0:0: [sdd] Attached SCSI removable disk 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.618720] sd 7:0:0:1: [sde] Attached SCSI removable disk 2014-02-13T07:13:01.986839+01:00 Hygiea kernel: [ 33.722749] usblp0: removed 2014-02-13T07:13:01.986840+01:00 Hygiea kernel: [ 33.875790] usb 3-3: reset high-speed USB device number 3 using xhci_hcd The other issue I still (or more again) have: shutdown does not work at all. It just stays on when it reached the final shutdown according to systemd's output and this is also after around 2 minutes. All that is really new since 13.1 and it got only worse with completely new hardware. This is really annoying. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 13.02.2014 07:49, schrieb Wolfgang Rosenauer:
blame" and "systemd-analyze plot > output.svg" to get a picture of what is taking so long on your boot? So now I completely replaced my hardware with a very powerful completely new one. Latest Intel core i5 Haswell + SSD. No software raid anymore. Just a very simple setup with one disk. And I'm still really wondering how you can boot that fast. My boot time is regularly still 45 seconds (almost exactly the same as with my old hardware).
Hygiea:~ # systemd-analyze blame 30.883s systemd-udev-settle.service 5.825s network.service 5.427s network@enp0s25.service 3.034s cifs.service 1.000s systemd-vconsole-setup.service ...
What is this systemd-udev-settle.service doing? Nobody could tell me so far. Could it be related to USB devices? I have some of them connected which have card readers attached. The network service also is a bit strange given that it is a static configuration.
In the log file the big pause looks like this: 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.514367] sd 7:0:0:1: Attached scsi generic sg5 type 0 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.606936] sd 7:0:0:0: [sdd] Attached SCSI removable disk 2014-02-13T07:13:01.986838+01:00 Hygiea kernel: [ 3.618720] sd 7:0:0:1: [sde] Attached SCSI removable disk 2014-02-13T07:13:01.986839+01:00 Hygiea kernel: [ 33.722749] usblp0: removed 2014-02-13T07:13:01.986840+01:00 Hygiea kernel: [ 33.875790] usb 3-3: reset high-speed USB device number 3 using xhci_hcd
Hi, I wonder since I installed 13.1 why the boot process takes so long. Thanks to your message I learned about "systemd-analyze blame". In my situation also network and systemd-udev-settle.service take long to do their jobs, but the other way round: systemd-analyze blame 26.459s network.service 24.541s network@enp2s5.service 5.947s systemd-udev-settle.service 2.903s plymouth-start.service How I can I figure out in detail why it hangs? And how do I change this? Thanks Karl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Karl Sinn
Am 13.02.2014 07:49, schrieb Wolfgang Rosenauer:
blame" and "systemd-analyze plot > output.svg" to get a picture of what is taking so long on your boot? So now I completely replaced my hardware with a very powerful completely new one. Latest Intel core i5 Haswell + SSD. No software raid anymore. Just a very simple setup with one disk. And I'm still really wondering how you can boot that fast. My boot time is regularly still 45 seconds (almost exactly the same as with my old hardware).
Hygiea:~ # systemd-analyze blame 30.883s systemd-udev-settle.service 5.825s network.service 5.427s network@enp0s25.service 3.034s cifs.service 1.000s systemd-vconsole-setup.service ...
What is this systemd-udev-settle.service doing? Nobody could tell me so far. Could it be related to USB devices? I have some of them connected which have card readers attached. The network service also is a bit strange given that it is a static configuration.
[...]
I wonder since I installed 13.1 why the boot process takes so long. Thanks to your message I learned about "systemd-analyze blame". In my situation also network and systemd-udev-settle.service take long to do their jobs, but the other way round:
systemd-analyze blame 26.459s network.service 24.541s network@enp2s5.service 5.947s systemd-udev-settle.service 2.903s plymouth-start.service
How I can I figure out in detail why it hangs? And how do I change this?
I am in the same: My older server box w/no ssd: 15.737s mysql.service 15.254s apache2.service 8.421s smb.service 7.694s SuSEfirewall2.service 6.419s plymouth-start.service 6.271s systemd-udev-settle.service 6.259s network.service 5.240s network@eth0.service My desktop work station w/ssd for system: 21.945s network.service 20.906s network@eth0.service 3.126s ntp.service 2.047s systemd-udev-settle.service 1.338s spamd.service 1.181s SuSEfirewall2.service 1.020s privoxy.service -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-13 13:55, Patrick Shanahan wrote:
My desktop work station w/ssd for system:
21.945s network.service 20.906s network@eth0.service 3.126s ntp.service 2.047s systemd-udev-settle.service 1.338s spamd.service 1.181s SuSEfirewall2.se
This laptop, no ssd: 7.082s spamd.service 5.671s systemd-fsck@dev-disk-by\x2dlabel-Boot.service 5.613s systemd-fsck@dev-disk-by\x2dlabel-Other.service 4.970s systemd-fsck@dev-disk-by\x2dlabel-Home.service 4.159s lvm2-activation.service 3.412s windows-C.mount 3.315s xdm.service 2.503s lvm2-activation-early.service 2.185s NetworkManager.service Funny about the lvm, as I have no lvm here. You can try instead "systemd-analyze critical-chain". Mine: The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @26.468s └─helloworld.service @26.073s +394ms └─multi-user.target @26.071s └─spamd.service @18.988s +7.082s └─basic.target @18.929s └─timers.target @18.922s └─systemd-tmpfiles-clean.timer @18.922s └─sysinit.target @18.913s └─apparmor.service @18.535s +377ms └─systemd-tmpfiles-setup.service @18.027s +503ms └─local-fs.target @17.629s └─other.mount @16.395s +1.232s └─systemd-fsck@dev-disk-by\x2dlabel-Other.service @10.730s +5.613s └─dev-disk-by\x2dlabel-Other.device @10.726s minas-tirith:~ # - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL8wsAACgkQja8UbcUWM1we4gD/QtVle0OLlecgO2tIVvsbFDA2 qtWaf9q58GH5/uhMGacA/2n6S8Z+ag/zyah3nOXo+/kIp5Jm6TYhqRfOl/sjh2px =i62F -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Feb 13, 2014 at 5:04 PM, Carlos E. R.
Funny about the lvm, as I have no lvm here.
It cannot know whether you have volume groups or not. Hopefully second attempt to switch to event-based activation will be more successful. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-13 14:15, Andrey Borzenkov wrote:
On Thu, Feb 13, 2014 at 5:04 PM, Carlos E. R.
wrote: Funny about the lvm, as I have no lvm here.
It cannot know whether you have volume groups or not.
I know that, but it takes 4 seconds to find out.
Hopefully second attempt to switch to event-based activation will be more successful.
Maybe :-) - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL8yGgACgkQja8UbcUWM1xMMAD/QNi0WF27HvQvPRLRuhbceOFI 3mRkNcdh1TAhLdoClycA/3Pva6eFEvYa0+rcjX05BvqNd2MvDr4dif8Ckz2sYXN5 =m0Fb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 13/02/2014 14:28, Carlos E. R. a écrit :
I know that, but it takes 4 seconds to find out.
most of the tasks are in //, obviously jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu 13 Feb 2014 02:28:08 PM CST, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-02-13 14:15, Andrey Borzenkov wrote:
On Thu, Feb 13, 2014 at 5:04 PM, Carlos E. R.
wrote: Funny about the lvm, as I have no lvm here.
It cannot know whether you have volume groups or not.
I know that, but it takes 4 seconds to find out.
Hi But is it in the critical chain? HP 4430s, B840 Dual Core cpu @1.9GHz, 8GB RAM, Vertex4 128GB SSD I use gummiboot and no plymouth. systemd-analyze Startup finished in 4.868s (firmware) + 26ms (loader) + 3.236s (kernel) + 2.315s (userspace) = 10.446s systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @2.307s └─xdm.service @1.692s +614ms └─ntp.service @1.584s +107ms └─nss-lookup.target @1.581s └─network.target @1.576s └─NetworkManager.service @1.508s +67ms └─SuSEfirewall2_init.service @1.409s +96ms └─basic.target @1.380s └─sockets.target @1.380s └─dbus.socket @1.380s └─sysinit.target @1.374s └─apparmor.service @1.110s +264ms └─systemd-tmpfiles-setup.service @1.070s +39ms └─local-fs.target @1.065s └─var-lib-ntp-proc.mount @1.673s └─local-fs-pre.target @393ms └─systemd-remount-fs.service @382ms +11ms └─systemd-readahead-replay.service @312ms +59ms -- Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890) openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop up 1 day 8:48, 3 users, load average: 0.03, 0.06, 0.05 CPU Intel® B840@1.9GHz | GPU Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-13 14:55, Malcolm wrote:
On Thu 13 Feb 2014 02:28:08 PM CST, Carlos E. R. wrote:
It cannot know whether you have volume groups or not.
I know that, but it takes 4 seconds to find out.
Hi But is it in the critical chain?
Hum. You got a point there. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL84KQACgkQja8UbcUWM1wCFgD/TPTMvLkfqni52b89P99ptLPS XtGS54m/JZcrXnSpcKMA/2AlvKwqs9XXqbCMH1i3aUPrfBKDut784/LwiX/7MaJl =TXai -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
mine, with ssd: # systemd-analyze Startup finished in 5.041s (kernel) + 22.884s (userspace) = 27.925s on this old (3 year) computer, the (new) ssd did really makes things faster jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Feb 13, 2014 at 2:29 PM, jdd
mine, with ssd:
# systemd-analyze Startup finished in 5.041s (kernel) + 22.884s (userspace) = 27.925s
on this old (3 year) computer, the (new) ssd did really makes things faster
I don't know if this helps the discussion much.. Here's mine from an updated 13.1 (install is about 2 weeks old). # systemd-analyze Startup finished in 2.421s (kernel) + 1.955s (userspace) = 4.376s # systemd-analyze blame 785ms vmware.service 716ms systemd-udev-settle.service 532ms plymouth-start.service 186ms nfs.service 179ms dkms_autoinstaller.service 172ms apparmor.service 134ms mnt-windows.mount 98ms plymouth-read-write.service .... (truncated)
From Grub to desktop is barely measurable/noticeable... as in it's stinking fast. That's with VMWare, NFS mounts etc. in there.
C. -- openSUSE 13.1 x86_64, KDE 4.12 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 13/02/2014 17:47, C a écrit :
# systemd-analyze Startup finished in 2.421s (kernel) + 1.955s (userspace) = 4.376s
specially fast :-!
# systemd-analyze blame
finally systemd have smart analyse tools :-) mine: # systemd-analyze blame 21.270s network.service 20.752s network@enp2s0.service 448ms windows-HD\x2dC.mount 248ms apparmor.service 202ms systemd-fsck@dev-disk-by\x2did-ata\x2dWDC_WD1001FAES\x2d60Z2A0_WD\x2dWCATR1443583\x2dpart9.service 190ms postfix.service 155ms SuSEfirewall2.service 127ms systemd-vconsole-setup.service 123ms systemd-remount-fs.service 121ms windows-ssd\x2dc.mount (...) I have a specially long NTFS (windows) mount that could be avoided at boot (with noauto) thanks, I like learning :-) jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 13.02.2014 14:04, schrieb Carlos E. R.:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 2014-02-13 13:55, Patrick Shanahan wrote:
My desktop work station w/ssd for system:
21.945s network.service 20.906s network@eth0.service 3.126s ntp.service 2.047s systemd-udev-settle.service 1.338s spamd.service 1.181s SuSEfirewall2.se This laptop, no ssd:
7.082s spamd.service 5.671s systemd-fsck@dev-disk-by\x2dlabel-Boot.service 5.613s systemd-fsck@dev-disk-by\x2dlabel-Other.service 4.970s systemd-fsck@dev-disk-by\x2dlabel-Home.service 4.159s lvm2-activation.service 3.412s windows-C.mount 3.315s xdm.service 2.503s lvm2-activation-early.service 2.185s NetworkManager.service
Funny about the lvm, as I have no lvm here.
You can try instead "systemd-analyze critical-chain". Mine:
The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character.
graphical.target @26.468s └─helloworld.service @26.073s +394ms └─multi-user.target @26.071s └─spamd.service @18.988s +7.082s └─basic.target @18.929s └─timers.target @18.922s └─systemd-tmpfiles-clean.timer @18.922s └─sysinit.target @18.913s └─apparmor.service @18.535s +377ms └─systemd-tmpfiles-setup.service @18.027s +503ms └─local-fs.target @17.629s └─other.mount @16.395s +1.232s
└─systemd-fsck@dev-disk-by\x2dlabel-Other.service @10.730s +5.613s └─dev-disk-by\x2dlabel-Other.device @10.726s minas-tirith:~ #
here it looks like this: graphical.target @3w 6d 2h 26min 52.163s └─multi-user.target @41.153s └─cron.service @41.147s └─postfix.service @39.919s +1.225s └─time-sync.target @39.912s └─ntp.service @39.638s +248ms └─nss-lookup.target @39.610s └─network.target @39.601s └─network.service @13.141s +26.459s └─SuSEfirewall2_init.service @11.144s +1.995s └─basic.target @11.116s It's hanging at network.service. How can I find out what's the problem, and how to fix it? thanks Karl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 13/02/14 13:55, Karl Sinn wrote:
It's hanging at network.service.
How can I find out what's the problem, and how to fix it?
How long does it take for the DHCP server to respond? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 13.02.2014 15:10, schrieb Dylan:
On 13/02/14 13:55, Karl Sinn wrote:
It's hanging at network.service.
How can I find out what's the problem, and how to fix it?
How long does it take for the DHCP server to respond?
it's my local router: ping 192.168.2.1 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=0.459 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=0.417 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=0.469 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=0.482 ms Karl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-13 15:13, Karl Sinn wrote:
How long does it take for the DHCP server to respond?
it's my local router: ping 192.168.2.1
No, that's not it. DHCP, for reasons I don't clearly know, is often very slow to respond. I guess the method tries something which fails, but has to wait for the timeouts before trying another way. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL84YEACgkQja8UbcUWM1wYNQD/QMOpnJEbUQJEt//wVdrlGPiT 2i95JrwDl43/jPtELVYBAIaoGFL9zLC5ISMYAVQCwyyVyZg0lELmToMKc8JAYzlm =PF+q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
No, that's not it. DHCP, for reasons I don't clearly know, is often very slow to respond. I guess the method tries something which fails, but has to wait for the timeouts before trying another way.
How do I check that? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-13 17:32, Karl Sinn wrote:
No, that's not it. DHCP, for reasons I don't clearly know, is often very slow to respond. I guess the method tries something which fails, but has to wait for the timeouts before trying another way.
How do I check that?
As I said, i don't know. You could, perhaps, start wireshark, and then tell the dhcp client to get an IP. Then analyze what happens... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL8/9oACgkQja8UbcUWM1wDwQEAjJSo/jHBCIi+E6rSq9NPHfqY r9iOtHid4vmL1putJoAA+QFcSZo9bcYTffwHbnnJwHxNCupPFDKMpTw4V1vdDecT =5mlX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Head of systemctl-analyze blame on 32 bit 13.2, 2.8GHz P4, LVM-free, RAID-free, single HD host gx280: 10.658s lvm2-activation.service 9.697s systemd-fsck@dev-disk-by\x2dlabel-15pub.service 8.876s systemd-fsck@dev-disk-by\x2dlabel-12suse123.service 6.850s systemd-fsck@dev-disk-by\x2dlabel-14usrlcl.service 6.700s systemd-fsck@dev-disk-by\x2dlabel-17cooker.service 5.773s systemd-fsck@dev-disk-by\x2dlabel-os131p19.service 5.226s systemd-fsck@dev-disk-by\x2dlabel-03boot.service 4.199s systemd-fsck@dev-disk-by\x2dlabel-13home.service 4.038s lvm2-activation-early.service 3.777s wicked.service Total boot time roughly 90 seconds. Last time shown before last times scrolled offscreen was 79 or so. 13.1 on same machine only takes about 40 seconds: 9.493s systemd-udev-settle.service 8.946s systemd-fsck@dev-disk-by\x2dlabel-15pub.service 6.925s systemd-fsck@dev-disk-by\x2dlabel-os132p20.service 6.253s systemd-fsck@dev-disk-by\x2dlabel-13home.service 6.187s network.service 5.874s systemd-fsck@dev-disk-by\x2dlabel-14usrlcl.service 2.657s nmb.service 1.808s systemd-vconsole-setup.service 1.792s nfsserver.service 1.723s lvm2-activation-early.service -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Andrey Borzenkov
-
C
-
Carlos E. R.
-
Dylan
-
Felix Miata
-
jdd
-
Karl Sinn
-
Malcolm
-
Patrick Shanahan
-
Wolfgang Rosenauer