May 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] USB Devices just stop working!
by Ritchie Fraser 03 May '14

03 May '14

Hi all, I have taken the plunge and performed a fresh install 13.1 on my HP Compaq Presario CQ60 (replacing a 11.2 installation). I seem to have an issue with usb. I boot the machine and all is well for a while. Then my USB mouse and external USB HDD stop responding. The mouse is getting power from the USB socket as the red led underneath lights up. After they have stopped responding, if I watch /var/log/messages and unplug / plug in the devices nothing appears in the message log. Is there a way to restart the USB subsystem like I can restart the network? Regards Ritchie -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] How to start apache+ssl with encrypted server key?
by Josef Wolf 03 May '14

03 May '14

Hello, I am currently upgrading to opensuse-13.1 and experience a problem starting apache with an encrypted SSL server key. In older opensuse releases, I increased APACHE_START_TIMEOUT in /etc/sysconfig/apache2, and started the server manually by calling /etc/init.d/apache2 startssl But this don't seem to work anymore in 13.1. No matter how big I set the timeout, it always times out after about 90 seconds. Before the upgrade, I had to wait about 5 minutes until the passphrase prompt appeared. Here is a transcript: raven:/root # date; /etc/init.d/apache2 start; date Sat May 3 00:15:25 CEST 2014 redirecting to systemctl start apache2.service Job for apache2.service failed. See 'systemctl status apache2.service' and 'journalctl -xn' for details. Sat May 3 00:16:55 CEST 2014 It times out after 90 seconds, although I have set APACHE_START_TIMEOUT=400. With older opensuse releases, I would get a passphrase prompt after several minutes. raven:/root # journalctl -xn -- Logs begin at Fri 2014-05-02 15:48:46 CEST, end at Sat 2014-05-03 00:17:21 CEST. -- May 03 00:16:55 raven systemd[1]: apache2.service operation timed out. Terminating. May 03 00:16:55 raven systemd[1]: Failed to start The Apache Webserver. -- Subject: Unit apache2.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba4… -- -- Unit apache2.service has failed. -- -- The result is failed. May 03 00:16:55 raven systemd[1]: Unit apache2.service entered failed state. raven:/root # systemctl status apache2.service apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; disabled) Active: failed (Result: timeout) since Sat 2014-05-03 00:16:55 CEST; 43s ago Main PID: 21229 May 03 00:15:25 raven start_apache2[21229]: [Sat May 03 00:15:25.469059 2014] [so:warn] [pid 21229] AH01574: module ssl_module is already loaded, skipping May 03 00:16:55 raven systemd[1]: apache2.service operation timed out. Terminating. May 03 00:16:55 raven systemd[1]: Failed to start The Apache Webserver. May 03 00:16:55 raven systemd[1]: Unit apache2.service entered failed state. raven:/root # The files in /var/log/apache2/ are created, but are eempty. Any ideas how to track this down? -- Josef Wolf jw(a)raven.inka.de -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] two nearly failed 13.1 installs and virtual machine problem
by jdd 03 May '14

03 May '14

Hello, I post this for infos. I just installed 13.1 on two old laptops (lifebook and HP compaq), with only 512Mb ram the two of them failed at first, that is on the very end yast freezed. On the HP I could reboot the flash card I used, go to update and finish the install (I had to choose "show all partitions"). no user was installed, but root was and I could so finish installing and updating the system. on the lifebook, even the update failed, but I discovered by chance than grub was working and the distro booting, but no user was available, not even root. so I had to boot a rescue disk, mount --bind proc, sys and dev, chroot and set the root passwd after that all could run and I'm updating right now. so, you see, one don't have to give up too fast :-) a second remark. I had last week to install 13.1 on a virtual machine hosted by my own server online, 12.3 for the host. Very powerful machine, host with i7 and 24Gb ram, virtual by virtualbox 2 proc and 8Gb ram. The installs screen of yast2 (graphical, ssh -X, virtualbox graph interface) was *deadly slow* - nearly unusable, specially for language selection. I noticed this because I had the same day to reinstall a 12.1 on this very same machine, and it was pretty fluid on the exact same circumstances. why is 13.1 install so slow, I don't know, I didn't experience such things on my old laptops. jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] KDE 4.13 is FAST!
by Anton Aylward 02 May '14

02 May '14

I'm very very impressed by the speed of KDE 4.13 Not only is the startup part that steps though the icons on the splash screen about 4-5 times as fast as in .11, but so is that application start up. Previously the KDE components, dolphin and the terminal window, each with many tabs, came up PDQ, but the Mozilla components, Firefox and Thunderbird, might take as much as 8 or ten seconds. Now all of them come up almost instantly. While I only need to bring up KDE once or twice a week (this week has been exceptional, a few times every day as parts of .13 get released to the respositories) I get the similar snappy response in other areas, starting other applications from the CLI in the terminal window and via F2. Speed & response is always something to be grateful for. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] apache2 index.html and DocumentRoot questions
by doiggl＠velocitynet.com.au 02 May '14

02 May '14

Hello, On http://127.0.0.1/ the shows error[1] Question: How do I get the browser to show the index.html content ? What needs changing ? and how is the display location set ? Thanks Glenn - I have these rpms installed # rpm -qa |grep -i apache2 |sort apache2-2.4.7-3.2.x86_64 apache2-doc-2.4.6-6.19.2.noarch apache2-example-pages-2.4.6-6.19.2.x86_64 apache2-mod_php5-5.4.20-4.1.x86_64 apache2-prefork-2.4.7-3.2.x86_64 apache2-utils-2.4.6-6.19.2.x86_64 /srv/www/htdocs/index.html shows: # cat /srv/www/htdocs/index.html <html><body><h1>It works!</h1></body></html> # httpd2 -S VirtualHost configuration: *:80 127.0.0.1 (/etc/apache2/vhosts.d/cacti.conf:1) ServerRoot: "/srv/www" Main DocumentRoot: "/srv/www/htdocs" Main ErrorLog: "/var/log/apache2/error_log" Mutex ssl-cache: using_defaults Mutex default: dir="/run/" mechanism=default Mutex mpm-accept: using_defaults Mutex ssl-stapling: using_defaults PidFile: "/run/httpd.pid" Define: DUMP_VHOSTS Define: DUMP_RUN_CFG User: name="wwwrun" id=30 Group: name="www" id=8 [1] http://127.0.0.1/ Access forbidden! You don't have permission to access the requested directory. There is either no index document or the directory is read-protected. If you think this is a server error, please contact the webmaster. Error 403 127.0.0.1 Apache/2.4.7 (Linux/SUSE) -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] Chromium and Flash
by C 02 May '14

02 May '14

Since updating to Chromuim 33 and now 34, some webpages with Flash content embedded no longer work. For example: https://www.youtube.com/watch?v=A3JC24p0YsA (Which I'm guessing has no HTML5 equiv content) Pepper-flash is installed and shows up as enabled in chrome://plugins ------------ Adobe Flash Player (2 files) - Version: 13.0.0.206 Shockwave Flash 13.0 r0 ------------ If I roll back to Chromium 31, everything works as expected. Any tips on what I can do to sort this out other than use Firefox (which works fine) or roll back to Chromium 31? C. -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Machine failing to hibernate if a certain java application is running.
by Carlos E. R. 02 May '14

02 May '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, When a certain java application (see later) is running, I have a machine that fails to hibernate. I see this in the pm-suspend.log (trimmed for simplicity): +++····························· Initial commandline parameters: Mon Apr 28 12:56:11 CEST 2014: Running hooks for hibernate. Running hook /usr/lib/pm-utils/sleep.d/00logging hibernate hibernate: hibernate initiated: Mon Apr 28 12:56:11 CEST 2014 ... ... hibernate: success everywhere till ... /usr/lib/pm-utils/sleep.d/99info hibernate hibernate: success. Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate: /usr/lib/pm-utils/sleep.d/99video hibernate hibernate: success. Mon Apr 28 12:56:13 CEST 2014: performing hibernate INFO: using built-in quirks database from HAL. INFO: S2RAM_OPTS from HAL quirks: ' '. Mon Apr 28 12:56:19 CEST 2014: Awake. Mon Apr 28 12:56:20 CEST 2014: Running hooks for thaw Running hook /usr/lib/pm-utils/sleep.d/99video thaw hibernate: /usr/lib/pm-utils/sleep.d/99video thaw hibernate: success. Running hook /usr/lib/pm-utils/sleep.d/99info thaw hibernate: ·····························++- It is thawing immediately, no error given. Let's see the messages log: +++····························· 2014-04-28T12:56:11.880848+02:00 AmonLanc pm-utils: Hibernating (01)... 2014-04-28T12:56:12.353763+02:00 AmonLanc kernel: [137474.737127] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 2014-04-28T12:56:12.510594+02:00 AmonLanc systemd[1]: network(a)eth0.service: main process exited, code=killed, status=9/KILL 2014-04-28T12:56:12.518248+02:00 AmonLanc network[23906]: redirecting to "systemctl --signal=9 kill network.service" 2014-04-28T12:56:12.564912+02:00 AmonLanc pm-utils: Hibernating (95)... 2014-04-28T12:56:13.981750+02:00 AmonLanc kernel: [137476.366469] PM: Marking nosave pages: [mem 0x0009f000-0x000fffff] 2014-04-28T12:56:13.981778+02:00 AmonLanc kernel: [137476.366477] PM: Basic memory bitmaps created 2014-04-28T12:56:16.040658+02:00 AmonLanc kernel: [137477.194160] Syncing filesystems ... done. 2014-04-28T12:56:16.051944+02:00 AmonLanc kernel: [137477.258892] Freezing user space processes ... (elapsed 0.002 seconds) done. 2014-04-28T12:56:16.051953+02:00 AmonLanc kernel: [137477.261594] PM: Preallocating image memory... 2014-04-28T12:56:16.051956+02:00 AmonLanc kernel: [137478.096784] Restarting tasks ... done. 2014-04-28T12:56:16.051959+02:00 AmonLanc kernel: [137478.104366] PM: Basic memory bitmaps freed 2014-04-28T12:56:31.561440+02:00 AmonLanc dbus[1490]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) 2014-04-28T12:56:32.060387+02:00 AmonLanc pm-utils: Thawing (95)... 2014-04-28T12:56:32.060867+02:00 AmonLanc dbus[1490]: [system] Activated service 'org.freedesktop.PackageKit' failed: Cannot launch daemon, file not found or permissions invalid 2014-04-28T12:56:32.061501+02:00 AmonLanc network[24081]: redirecting to "systemctl restart network.service" 2014-04-28T12:56:32.062659+02:00 AmonLanc systemd[1]: Stopping ifup managed network interface eth0... 2014-04-28T12:56:32.098013+02:00 AmonLanc systemd[1]: Stopping LSB: Configure network interfaces and set up routing... 2014-04-28T12:56:32.098846+02:00 AmonLanc systemd[1]: Starting LSB: Configure network interfaces and set up routing... ·····························++- dmesg doesn't say different: +++····························· [137476.366469] PM: Marking nosave pages: [mem 0x0009f000-0x000fffff] [137476.366477] PM: Basic memory bitmaps created [137477.194160] Syncing filesystems ... done. [137477.258892] Freezing user space processes ... (elapsed 0.002 seconds) done. [137477.261594] PM: Preallocating image memory... [137478.096784] Restarting tasks ... done. [137478.104366] PM: Basic memory bitmaps freed ·····························++- So no messages at about why it aborts. Now a normal pm-suspend.log, with the suspect java application stopped: +++····························· Initial commandline parameters: Mon Apr 28 12:49:48 CEST 2014: Running hooks for hibernate. Running hook /usr/lib/pm-utils/sleep.d/00logging hibernate hibernate: hibernate initiated: Mon Apr 28 12:49:48 CEST 2014 ... ... /usr/lib/pm-utils/sleep.d/99info hibernate hibernate: success. Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate: /usr/lib/pm-utils/sleep.d/99video hibernate hibernate: success. Mon Apr 28 12:49:49 CEST 2014: performing hibernate INFO: using built-in quirks database from HAL. INFO: S2RAM_OPTS from HAL quirks: ' '. Mon Apr 28 12:51:57 CEST 2014: Awake. Mon Apr 28 12:51:57 CEST 2014: Running hooks for thaw Running hook /usr/lib/pm-utils/sleep.d/99video thaw hibernate: /usr/lib/pm-utils/sleep.d/99video thaw hibernate: success. Running hook /usr/lib/pm-utils/sleep.d/99info thaw hibernate: ·····························++- The log is the same, but the machine actually powered off. The timestamps get written to file after the fact, I guess. And lets see /var/log/messages - - this time it is different, the machine did go to hibernation and it shows: +++····························· 2014-04-28T12:49:48.268310+02:00 AmonLanc pm-utils: Hibernating (01)... 2014-04-28T12:49:48.488613+02:00 AmonLanc kernel: [137215.095786] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0 2014-04-28T12:49:48.570074+02:00 AmonLanc systemd[1]: network(a)eth0.service: main process exited, code=killed, status=9/KILL 2014-04-28T12:49:48.577795+02:00 AmonLanc network[21730]: redirecting to "systemctl --signal=9 kill network.service" 2014-04-28T12:49:48.622385+02:00 AmonLanc pm-utils: Hibernating (95)... 2014-04-28T12:49:49.744408+02:00 AmonLanc kernel: [137216.351823] PM: Marking nosave pages: [mem 0x0009f000-0x000fffff] 2014-04-28T12:49:49.744439+02:00 AmonLanc kernel: [137216.351831] PM: Basic memory bitmaps created 2014-04-28T12:51:57.342868+02:00 AmonLanc kernel: [137217.131446] Syncing filesystems ... done. 2014-04-28T12:51:57.120800+02:00 AmonLanc systemd[6024]: Time has been changed 2014-04-28T12:51:57.121541+02:00 AmonLanc systemd[1]: Time has been changed 2014-04-28T12:51:57.122260+02:00 AmonLanc systemd[30852]: Time has been changed 2014-04-28T12:51:58.354793+02:00 AmonLanc kernel: [137217.155722] Freezing user space processes ... (elapsed 0.004 seconds) done. 2014-04-28T12:51:58.354815+02:00 AmonLanc kernel: [137217.160555] PM: Preallocating image memory... done (allocated 71061 pages) 2014-04-28T12:51:58.354817+02:00 AmonLanc kernel: [137217.303618] PM: Allocated 284244 kbytes in 0.14 seconds (2030.31 MB/s) 2014-04-28T12:51:58.354821+02:00 AmonLanc kernel: [137217.303624] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 2014-04-28T12:51:58.354824+02:00 AmonLanc kernel: [137217.305344] Suspending console(s) (use no_console_suspend to debug) 2014-04-28T12:51:58.354826+02:00 AmonLanc kernel: [137217.305664] parport_pc 00:08: disabled 2014-04-28T12:51:58.354829+02:00 AmonLanc kernel: [137217.305677] i8042 aux 00:07: System wakeup disabled by ACPI 2014-04-28T12:51:58.354831+02:00 AmonLanc kernel: [137217.305685] i8042 kbd 00:06: System wakeup enabled by ACPI 2014-04-28T12:51:58.354834+02:00 AmonLanc kernel: [137217.385024] PM: freeze of devices complete after 79.668 msecs 2014-04-28T12:51:58.354837+02:00 AmonLanc kernel: [137217.385196] PM: late freeze of devices complete after 0.169 msecs 2014-04-28T12:51:58.354840+02:00 AmonLanc kernel: [137217.385506] PM: noirq freeze of devices complete after 0.306 msecs 2014-04-28T12:51:58.354848+02:00 AmonLanc kernel: [137217.385616] ACPI: Preparing to enter system sleep state S4 2014-04-28T12:51:58.354851+02:00 AmonLanc kernel: [137217.386034] PM: Saving platform NVS memory 2014-04-28T12:51:58.354854+02:00 AmonLanc kernel: [137217.386287] Disabling non-boot CPUs ... 2014-04-28T12:51:58.354856+02:00 AmonLanc kernel: [137217.386386] PM: Creating hibernation image: 2014-04-28T12:51:58.354858+02:00 AmonLanc kernel: [137217.388002] PM: Need to copy 56036 pages 2014-04-28T12:51:58.354861+02:00 AmonLanc kernel: [137217.388002] PM: Normal pages needed: 56036 + 1024, available pages: 72826 2014-04-28T12:51:58.354863+02:00 AmonLanc kernel: [137217.388002] PM: Restoring platform NVS memory 2014-04-28T12:51:58.354866+02:00 AmonLanc kernel: [137217.388002] microcode: CPU0 sig=0xf29, pf=0x4, revision=0x2e 2014-04-28T12:51:58.354868+02:00 AmonLanc kernel: [137217.388002] ACPI: Waking up from system sleep state S4 2014-04-28T12:51:58.354874+02:00 AmonLanc kernel: [137217.404087] yenta_cardbus 0000:01:03.0: O2: enabling read prefetch/write burst. If you experience problems or performance issues, use the yenta_socket parameter 'o2_speedup=off' 2014-04-28T12:51:58.354877+02:00 AmonLanc kernel: [137217.420544] PM: noirq restore of devices complete after 30.077 msecs 2014-04-28T12:51:58.354880+02:00 AmonLanc kernel: [137217.420664] PM: early restore of devices complete after 0.083 msecs 2014-04-28T12:51:58.354882+02:00 AmonLanc kernel: [137217.439541] i915 0000:00:02.0: setting latency timer to 64 2014-04-28T12:51:58.354885+02:00 AmonLanc kernel: [137217.456333] uhci_hcd 0000:00:1d.0: setting latency timer to 64 2014-04-28T12:51:58.354887+02:00 AmonLanc kernel: [137217.456355] usb usb2: root hub lost power or was reset 2014-04-28T12:51:58.354889+02:00 AmonLanc kernel: [137217.456367] uhci_hcd 0000:00:1d.1: setting latency timer to 64 2014-04-28T12:51:58.354892+02:00 AmonLanc kernel: [137217.456384] usb usb3: root hub lost power or was reset 2014-04-28T12:51:58.399884+02:00 AmonLanc kernel: [137217.456394] uhci_hcd 0000:00:1d.2: setting latency timer to 64 2014-04-28T12:51:58.399899+02:00 AmonLanc kernel: [137217.456412] usb usb4: root hub lost power or was reset 2014-04-28T12:51:58.399902+02:00 AmonLanc kernel: [137217.456423] ehci-pci 0000:00:1d.7: setting latency timer to 64 2014-04-28T12:51:58.399904+02:00 AmonLanc kernel: [137217.456435] usb usb1: root hub lost power or was reset 2014-04-28T12:51:58.399907+02:00 AmonLanc kernel: [137217.460310] ehci-pci 0000:00:1d.7: cache line size of 64 is not supported 2014-04-28T12:51:58.399909+02:00 AmonLanc kernel: [137217.460329] pci 0000:00:1e.0: setting latency timer to 64 2014-04-28T12:51:58.399911+02:00 AmonLanc kernel: [137217.460441] ata_piix 0000:00:1f.1: setting latency timer to 64 2014-04-28T12:51:58.399914+02:00 AmonLanc kernel: [137217.460502] snd_intel8x0 0000:00:1f.5: setting latency timer to 64 2014-04-28T12:51:58.399916+02:00 AmonLanc kernel: [137217.460581] snd_intel8x0m 0000:00:1f.6: setting latency timer to 64 2014-04-28T12:51:58.399922+02:00 AmonLanc kernel: [137217.460739] eth0: DSPCFG accepted after 0 usec. 2014-04-28T12:51:58.399926+02:00 AmonLanc kernel: [137217.460746] eth0: Setting full-duplex based on negotiated link capability. 2014-04-28T12:51:58.399929+02:00 AmonLanc kernel: [137217.488156] i8042 kbd 00:06: System wakeup disabled by ACPI 2014-04-28T12:51:58.399931+02:00 AmonLanc kernel: [137217.488820] parport_pc 00:08: activated 2014-04-28T12:51:58.399934+02:00 AmonLanc kernel: [137217.624329] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out 2014-04-28T12:51:58.399936+02:00 AmonLanc kernel: [137217.624332] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out 2014-04-28T12:51:58.399939+02:00 AmonLanc kernel: [137217.624543] ata1.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded 2014-04-28T12:51:58.399941+02:00 AmonLanc kernel: [137217.648375] ata1.00: configured for UDMA/100 2014-04-28T12:51:58.399943+02:00 AmonLanc kernel: [137217.648467] sd 0:0:0:0: [sda] Starting disk 2014-04-28T12:51:58.399949+02:00 AmonLanc kernel: [137217.912028] usb 1-4: reset high-speed USB device number 2 using ehci-pci 2014-04-28T12:51:58.399953+02:00 AmonLanc kernel: [137218.032044] firewire_core 0000:01:0a.0: rediscovered device fw0 2014-04-28T12:51:58.399955+02:00 AmonLanc kernel: [137218.156017] usb 4-2: reset full-speed USB device number 2 using uhci_hcd 2014-04-28T12:51:58.399957+02:00 AmonLanc kernel: [137218.473541] PM: restore of devices complete after 1034.498 msecs 2014-04-28T12:51:58.399960+02:00 AmonLanc kernel: [137218.862203] Restarting kernel threads ... done. 2014-04-28T12:51:58.399962+02:00 AmonLanc kernel: [137218.865089] Restarting tasks ... done. 2014-04-28T12:51:58.399965+02:00 AmonLanc kernel: [137218.871900] PM: Basic memory bitmaps freed 2014-04-28T12:52:01.173911+02:00 AmonLanc dbus[1490]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) 2014-04-28T12:52:01.700733+02:00 AmonLanc pm-utils: Thawing (95)... 2014-04-28T12:52:01.928066+02:00 AmonLanc dbus[1490]: [system] Activated service 'org.freedesktop.PackageKit' failed: Cannot launch daemon, file not found or permissions invalid 2014-04-28T12:52:02.426069+02:00 AmonLanc network[21963]: redirecting to "systemctl restart network.service" 2014-04-28T12:52:02.433872+02:00 AmonLanc systemd[1]: Stopping ifup managed network interface eth0... 2014-04-28T12:52:02.436145+02:00 AmonLanc systemd[1]: Stopping LSB: Configure network interfaces and set up routing... 2014-04-28T12:52:02.565994+02:00 AmonLanc systemd[1]: Starting LSB: Configure network interfaces and set up routing... 2014-04-28T12:52:03.105363+02:00 AmonLanc ifdown[21980]: eth0 device: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller 2014-04-28T12:52:03.112182+02:00 AmonLanc ifdown[21980]: eth0 device: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller 2014-04-28T12:52:03.368314+02:00 AmonLanc network[21991]: Setting up network interfaces: 2014-04-28T12:52:03.905985+02:00 AmonLanc network[21991]: lo ·····························++- Now, about the application itself. It is using java. Actually, the problem started about two days ago, when I installed oracle java to see if it solved a different issue. Before it was using java-1_7_0-openjdk-1.7.0.6-24.13.5.i586, which as far as I remember doesn't have this particular problem. The application itself is jdownloader (jdupdate.jar), an application to download things on its own (http://jdownloader.org) When it is running it impedes hibernation, probably intentionally, because it would abort a long download which would then have to be restarted (these sites often do not allow retaking partials downloads). But that is of no consequence to me, as I time the hibernation to happen after the download completed while I sleep (via 'at'). My guess is then that the functionality to impede hibernation fails with java-1_7_0-openjdk-1.7.0.6-24.13.5.i586, but not with jre-1.7.0_55-fcs.i586. But I'm surprised that there is no entry at all in the logs about why the hibernation was aborted. BUG somewhere? So, my problem now is to force hibernation to happen, perhaps by suspending the application itself or directly killing it. I know about "fg". But "bg" doesn't seem to be for "suspending" a process, just sends a process to background. Or I can revert to openjdk. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlNeRCsACgkQtTMYHG2NR9UIMgCfY+FJkGzJd0gHMvMSAaBRo5TN mKoAoJBUe+XZsEJvUYD9eRNG7N/rqcQ1 =Zx5P -----END PGP SIGNATURE-----

3 3

Fwd: [opensuse] Re: X Server for display crash after upgrading to KDE4.13
by John Connor 01 May '14

01 May '14

---------- Forwarded message ---------- From: John Connor <jaconnor44(a)gmail.com> Date: 1 May 2014 19:36 Subject: Re: [opensuse] Re: X Server for display crash after upgrading to KDE4.13 To: Open Suse Mailing List <opensuse(a)opensuse.org> I use Yast2 in text/curses all the time (for remote access via SSH). It doesn't need the bandwidth that X-forwarding would need, and I find it reasonably usable. Not as pretty, of course, and you spend a lot of time hitting the arrow keys, but it is useable. John On 1 May 2014 16:45, Anton Aylward <opensuse(a)antonaylward.com> wrote: > > On 05/01/2014 08:19 AM, Basil Chupin wrote: > > On 01/05/14 21:44, Anton Aylward wrote: > >> On 05/01/2014 02:36 AM, Basil Chupin wrote: > >>> [...] > >> "Yast2 in keyboard mode" ?? > >> > >> Do you mean 'zypper'? > > > > Nope, YaST2. > > > > You mean that you have never had the pleasure of using YaST2 in keyboard > > mode?! > > > > What you have been missing! :-) > > > > Login as root at level 3 and then on the command line, "Yast2". Take it > > from here - and enjoy! :-) . > > Oh you mean > > CURSES! > > Once. > Never again! > > -- > The saying often quoted from Lord Kelvin… that 'where you cannot measure > your knowledge is meagre and unsatisfactory,' as applied in mental and > social science, is misleading and pernicious. This is another way of > saying that these sciences are not science in the sense of physical > science and cannot attempt to be such without forfeiting their proper > nature and function. Insistence on a concretely quantitative economics > means the use of statistics of physical magnitudes, whose economic > meaning and significance is uncertain and dubious. (Even wheat is > approximately homogeneous only if measured in economic terms.) And a > similar statement would even apply more to other social sciences. In > this field, the Kelvin dictum very largely means in practice, 'if you > cannot measure, measure anyhow!' > — Frank Hyneman Knight > 'What is Truth' in Economics? (1956), 166 > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] X Server for display crash after upgrading to KDE4.13
by C 01 May '14

01 May '14

Seems like I've got a repeatable problem after updating to KDE4.13 (update from KDE 4.12 to 4.13 with a downgrade on the branding). I can trigger the crash by launching Chromium (any version from 31 through 33 - I tried 31, 32 and 33, wiping ~/.config/chromium each time to force a clean start). As soon as I launch Chromium, the X server dies and leaves this line in /var/log/messages: 2014-04-25T19:10:33.176822+02:00 linux-w1b9 kdm[600]: X server for display :0 terminated unexpectedly No other error is showing up in messages, Xorg.0.log and so on (at least not that I can see). Firefox 29.0 works fine.. Chromium is the only app so far that I've found to trigger the X Server crash after upgrading. Any tips on finding a way to nail this one down? C -- openSUSE 13.1 x86_64, KDE 4.13 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 24

[opensuse] Updating to KDE SC 4.13 from KDE:Current
by Raymond Wooninck 01 May '14

01 May '14

In the next hours KDE:Current will publish KDE 4.13 SC. As that this release comes with a big change (Nepomuk -> Baloo), we would like some simple steps in order to perform the right upgrade. Before the upgrade In order to migrate data automatically from the Nepomuk store to the new format (used by Baloo), you will need Nepomuk up and running, and just for the time needed for the migration. Ensure that Nepomuk is running before the update (in System Settings > Desktop Search). This is only necessary in case Nepomuk is in use on the system. The upgrade itself * If you are already using KDE:Current then the upgrade should be a simple "zypper up" or upgrade packages through YaST Software Management. * If you are not yet using KDE:Current, then please follow the instructions on https://en.opensuse.org/KDE_repositories#Current_KDE_SC_release on how to add the necessary repositories. After adding them, a zypper dup is required to ensure that all the KDE packages are coming from KDE:Current. Please do not remove nepomuk, as that otherwise the migration to baloo will fail !! Also after the upgrade please make sure that the following package is installed "baloo-file". After this check, log off and back on. The migrator will then run and move all the data that can be migrated to the new system. It will also turn off Nepomuk at the end of the migration. At this moment it would be safe to remove the nepomuk related packages like nepomuk-core, libnepomukwidgets, soprano*, strigi, virtuoso and shared- desktop-ontologies. There are only a few packages left that are still requiring the nepomuk-framework (like bangarang, kweshtunotes, etc). Using Baloo Unlike the 'include folders to be indexed', Baloo prefers to index everything and exclude unwanted folders explicitly. With the standard setup, Baloo will index all files and directories below the home-directory. All other filesystems are indicated as omitted. This can be changed by deleting the respective entries. Unfortunately it is not possible to switch baloo off through systemsettings. If baloo is not wanted on the system, then the package "baloo-file" needs to be removed to prevent files being indexed. The package "baloo-pim" (only present when kdepim is installed) can be removed if no search capabilities are required for kmail. The only search client currently available for baloo, is the package called milou. Milou can be placed in the panel for easy access and the usage is quite simple. The search term is indicated and search results are shown for files, emails, etc. In the Milou settings, the categories from which results are shown can be selected. Milou can NOT be placed in the systray, as that this would cause the plasma desktop to crash upon login. Tags on files are no longer stored inside the database, but stored in the extended file attributes (xattr), which are stored in separate files on the filesystem. Known issues with KDE 4.13 - The initial indexing can be heavy on I/O especially if there are large text files: either one waits till the indexing is complete (this step is done only once), or the folder containing such files is excluded using System Settings. - Some data will be lost during the migration: in particular, emails will have to be re-indexed, and file<->activity associations, if used, will not be preserved. - Milou causes the Plasma-desktop to crash if it is placed in the systray !! Regards openSUSE KDE Community Team -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

16 51