January 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Cups does not start automatically.
by Carlos E. R. 06 Feb '17

06 Feb '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I try to print something, after booting, the list of printers does not appear in Libre Office or gimp. Telcontar:~ # systemctl status cups.service ● cups.service - CUPS Printing Service Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: inactive (dead) Telcontar:~ # Telcontar:~ # systemctl status cupsd.service ● cups.service - CUPS Printing Service Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: inactive (dead) Telcontar:~ # Telcontar:~ # systemctl status cups.socket ● cups.socket Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) Telcontar:~ # There is no message related to cups in /var/log/messages since the last boot. I thought that starting cups would be automatic, when needed, but in my case it is enabled, should be running fulltime. Apparently it also needs colord Telcontar:~ # systemctl status colord.service ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/usr/lib/systemd/system/colord.service; static; vendor preset: disabled) Active: inactive (dead) Telcontar:~ # systemctl start cups.service Telcontar:~ # systemctl status cups.service ● cups.service - CUPS Printing Service Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2017-01-30 19:37:03 CET; 20s ago Main PID: 8361 (cupsd) Tasks: 1 (limit: 512) CGroup: /system.slice/cups.service └─8361 /usr/sbin/cupsd -f Jan 30 19:37:03 Telcontar systemd[1]: Started CUPS Printing Service. Telcontar:~ # systemctl status colord.service ● colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/usr/lib/systemd/system/colord.service; static; vendor preset: disabled) Active: active (running) since Mon 2017-01-30 19:37:04 CET; 28s ago Main PID: 8366 (colord) Tasks: 3 (limit: 512) CGroup: /system.slice/colord.service └─8366 /usr/lib/colord Jan 30 19:37:04 Telcontar systemd[1]: Starting Manage, Install and Generate Color Profiles... Jan 30 19:37:04 Telcontar systemd[1]: Started Manage, Install and Generate Color Profiles. Jan 30 19:37:05 Telcontar colord[8366]: (colord:8366): Cd-WARNING **: failed to get session [pid 8361]: No such device or address Jan 30 19:37:05 Telcontar colord[8366]: (colord:8366): Cd-WARNING **: failed to get session [pid 8361]: No such device or address Jan 30 19:37:05 Telcontar colord[8366]: (colord:8366): Cd-WARNING **: failed to get session [pid 8361]: No such device or address Telcontar:~ # Log: 3.6> 2017-01-30 19:37:03 Telcontar systemd 1 - - Started CUPS Printing Service. <3.5> 2017-01-30 19:37:04 Telcontar dbus 1440 - - [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' <3.6> 2017-01-30 19:37:04 Telcontar systemd 1 - - Starting Manage, Install and Generate Color Profiles... <3.5> 2017-01-30 19:37:04 Telcontar dbus 1440 - - [system] Successfully activated service 'org.freedesktop.ColorManager' <3.6> 2017-01-30 19:37:04 Telcontar systemd 1 - - Started Manage, Install and Generate Color Profiles. <3.6> 2017-01-30 19:37:05 Telcontar colord 8366 - - (colord:8366): Cd-WARNING **: failed to get session [pid 8361]: No such device or address <3.6> 2017-01-30 19:37:05 Telcontar colord 8366 - - message repeated 2 times: [ (colord:8366): Cd-WARNING **: failed to get session [pid 8361]: No such device or address] <3.6> 2017-01-30 19:37:09 Telcontar systemd 1 - - Time has been changed Then when I try to print a message pops up saying that there is a missing printer, but nevertheless it prints. Now, what must I do so that cups does start on boot? Or a minute later, doesn't matter. I have to start it manually, some times several times till it holds. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAliPiiYACgkQtTMYHG2NR9VYMgCdFqTN7EmcDcIGvAi3z1lZcczr b0oAnAzLBVKdEKe+0rT68u+EyI0zdFlY =CFT1 -----END PGP SIGNATURE-----

3 10

[opensuse] setting up mysql error
by george from the tribe 02 Feb '17

02 Feb '17

Ok, so I used the following procedure https://en.opensuse.org/SDB:LAMP_setup to set up an apache2 web server, then php7, and then the mysql server with mariadb. Following that procedure in the SDB, it ran great, I was able to set up a small database, connect to it and edit it with phpmyadmin, and was pretty happy with it. Of course, there is one problem with that setup, and that is that it installs all the database files in the root partition. The SDB doesn't give any guidelines for how to move the database to my home partition, which is where I want it to be. So, I tried to move things on my own, and I am sure I messed something up. The directory where the database was installed at first was here: /var/lib/mysql And the directory that had the apache2 web server and phpmyadmin was here: /srv/www/htdocs Also, there was a file, /etc/my.cnf, in which you could change the location of the database. So here is what I did - I shutdown thy mysql service with systemctl stop mysql Then I went into /etc/my.cnf and put in this line where it says to in the file: # Remove leading # if you want to store your database elsewhere datadir = /home/george/FaithWiringDB/dbproj/mysql Then I copied the mysql files from /var/lib/mysql over to /home/george/FaithWiringDB/dbproj/mysql at first I changed the permissions to george:users, but that didn't work so I changed them back to root:root Now, when I tried to do systemctl start mysql.service, it won't start. # systemctl start mysql.service Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details. And here is the error I get: # systemctl status -l mysql ● mysql.service - MySQL server Loaded: loaded (/usr/lib/systemd/system/mysql.service; enabled; vendor preset: disabled) Active: activating (start-post) (Result: exit-code) since Tue 2017-01-31 15:45:43 PHT; 26s ago Process: 15402 ExecStart=/usr/lib/mysql/mysql-systemd-helper start (code=exited, status=1/FAILURE) Process: 15388 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper upgrade (code=exited, status=0/SUCCESS) Process: 15375 ExecStartPre=/usr/lib/mysql/mysql-systemd-helper install (code=exited, status=0/SUCCESS) Main PID: 15402 (code=exited, status=1/FAILURE); : 15403 (mysql-systemd-h) Tasks: 2 (limit: 512) CGroup: /system.slice/mysql.service └─control ├─15403 /bin/bash /usr/lib/mysql/mysql-systemd-helper wait └─15488 sleep 1 Jan 31 15:45:43 facofficeeng02 systemd[1]: Starting MySQL server... Jan 31 15:45:44 facofficeeng02 mysql-systemd-helper[15403]: Waiting for MySQL to start Jan 31 15:45:44 facofficeeng02 mysql-systemd-helper[15402]: 170131 15:45:44 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB) starting as process 15402 ... Jan 31 15:45:44 facofficeeng02 systemd[1]: mysql.service: Main process exited, code=exited, status=1/FAILURE I am really new to mysql, so any help would be appreciated. How do I get mysql up and running again? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 18

[opensuse] Settings to have wifi up and running after boot
by Albert, Oszkó 01 Feb '17

01 Feb '17

Hi all, This is a long standing problem for me. Now I have an ASUS K501 UX laptop with Leap 42.2 and KDE. Tha laptop possibly does not matter, since this was the situation with 42.1 on this laptop and 42.1 on a Lenovo and on another kind of ASUS with 42.2. The symptoms: When I boot, wired connection gets initialized, and usable when I plug in the cord. I would expect that if and when the network cable is not plugged, the wifi starts working automatically. This is not the case and rfkill says wireless is hard blocked. I can only get wifi running if I put the system to sleep (with fn+Zz or mains switch), and then wake it up (with Esc or mains switch). Sometimes this should be done twice. There is another twist: boot+put to sleep + waking always works on one condition: the mains (or battery charger) is plugged. In this case closing the lid suspends the system and opening the lid wakes it up. When the charger is not plugged the above sequence sometimes works and sometimes (mostly) not. Closing the lid suspends the laptop, opening the lid either wakes it up or causes reboot. I do not know and understand how and why these phenomena are connected. What the charger plugged in state has to do with wifi start or reboot. It is mysterious why the things sometimes at least partly work and sometimes why not. And the basic question is: why the configured wifi does not start after or during bootup. Any kind of hints or tips are welcome. Regards, Albert

6 21

[opensuse] cannot delete a RAID drive
by george from the tribe 01 Feb '17

01 Feb '17

I am trying to free up a partition on my work desktop. One of the partitions on the extra disk is part of an old RAID-1 configuration, and I am trying to delete the raid drive from the system and re-format that partition. However, whenever I try to use fdisk, it re-activates the RAID even though I have already removed it. Here is my partition table: # fdisk -l /dev/sdb Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x12c2c333 Device Boot Start End Sectors Size Id Type /dev/sdb1 2048 206847 204800 100M 7 HPFS/NTFS/exFAT /dev/sdb2 206848 324458495 324251648 154.6G 7 HPFS/NTFS/exFAT /dev/sdb3 324458496 358275071 33816576 16.1G 82 Linux swap / Solaris /dev/sdb4 * 358275072 1953523711 1595248640 760.7G 5 Extended /dev/sdb5 358277120 419717119 61440000 29.3G 83 Linux /dev/sdb6 419719168 481159167 61440000 29.3G 83 Linux /dev/sdb7 481161216 1953523711 1472362496 702.1G 83 Linux The device in question is /dev/sdb5. Note how if I look at the mdstat file, it shows it is active. So I try to fail the drive, but it won't let me. Then I stop the raid drive and remove it, and it shows it is no longer there. Seems like it should work. facofficeeng02:/home/george # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb5[0] 30703616 blocks super 1.2 [2/1] [U_] md1 : active raid1 sdb7[0] 736050176 blocks super 1.2 [2/1] [U_] bitmap: 6/6 pages [24KB], 65536KB chunk unused devices: <none> facofficeeng02:/home/george # cat /etc/mdadm.conf ARRAY /dev/md/facofficeeng02:1 UUID=a8872a97:eecd6828:f759773c:cb18678e facofficeeng02:/home/george # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb5[0] 30703616 blocks super 1.2 [2/1] [U_] md1 : active raid1 sdb7[0] 736050176 blocks super 1.2 [2/1] [U_] bitmap: 6/6 pages [24KB], 65536KB chunk unused devices: <none> facofficeeng02:/home/george # mdadm --fail /dev/md0 /dev/sdb5 mdadm: set device faulty failed for /dev/sdb5: Device or resource busy facofficeeng02:/home/george # mdadm --stop /dev/md0 mdadm: stopped /dev/md0 facofficeeng02:/home/george # mdadm --remove /dev/md0 facofficeeng02:/home/george # cat /proc/mdstat Personalities : [raid1] md1 : active raid1 sdb7[0] 736050176 blocks super 1.2 [2/1] [U_] bitmap: 6/6 pages [24KB], 65536KB chunk unused devices: <none> However, then when I run fdisk again, just to try and mess with it, the array re-activates itself: acofficeeng02:/home/george # fdisk /dev/sdb Welcome to fdisk (util-linux 2.28). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): q facofficeeng02:/home/george # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 sdb5[0] 30703616 blocks super 1.2 [2/1] [U_] md1 : active raid1 sdb7[0] 736050176 blocks super 1.2 [2/1] [U_] bitmap: 6/6 pages [24KB], 65536KB chunk unused devices: <none> I wanted to use fdisk to try and do something to that partition, but the array is reactivated as soon as I run fdisk. I tried gdisk for experiment (I can't use gdisk because the drive is mbr, not gpt), and it does the same thing. The drive re-activates itself. How do I completely get rid of my system seeing the raid in this partition and reactivating itself? I removed all the information from the /etc/mdadm.conf file for that drive, so it is not getting information from there. I am on a 42.2 system. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 6

[opensuse] Leap 42.2 - why does wicked take 39 seconds to get a dhcp address?
by David C. Rankin 01 Feb '17

01 Feb '17

All, I use this same laptop with both Leap and Arch, wpa/wireless. With Arch/netctl the IP is established in 13 seconds. With Leap/wicked it consistently takes 39 seconds. Is there some way to speed up the network connection? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 24

[opensuse] system-sleep/grub2.sleep fails to find the correct grub target
by Carlos E. R. 31 Jan '17

31 Jan '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I see this in the log while trying to hibernate, and a delay: <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - INFO: Running prepare-grub .. <3.6> 2017-01-30 20:23:20 Telcontar systemd 1 - - Stopping Deferred execution scheduler... <3.6> 2017-01-30 20:23:20 Telcontar systemd 1 - - Stopped Deferred execution scheduler. <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - service: no such service upsd.service <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sda1) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sda1) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sda1) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because it has the noresume option <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sda1) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because it has the noresume option <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb2) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb2) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb2) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb2) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - Skipping grub entry #, because its root= parameter (/dev/sdb7) <3.6> 2017-01-30 20:23:20 Telcontar systemd-sleep 10692 - - does not match the current root device (/dev/sdb8). <3.4> 2017-01-30 20:23:25 Telcontar systemd-sleep 10697 - - /usr/lib/systemd/system-sleep/grub2.sleep failed with error code 2. <3.6> 2017-01-30 20:23:25 Telcontar systemd-sleep 10692 - - Suspending system... <0.6> 2017-01-31 12:04:55 Telcontar kernel - - - [158874.187341] PM: Syncing filesystems ... done. Then, on come back, I see the boot menu of grub waiting for a boot selection. Fortunately it is the default one and boot proceeds after some seconds correctly, and hibernation image is found. It is true that the string "/dev/sdb8" is not found on /boot/grub2/grub.cfg. It is an UUID: linux /vmlinuz-4.4.36-8-default root=UUID=c6a59497-85b9-454c-a5d1-1dcafa6eed3d splash=verbose loglevel=3 console=tty0 vga=0x31a resume=/dev/disk/by-label/Swap_0 splash=verbose showopts cer@Telcontar:~> l /dev/disk/by-uuid/c6a59497-85b9-454c-a5d1-1dcafa6eed3d lrwxrwxrwx 1 root root 10 Jan 27 13:47 /dev/disk/by-uuid/c6a59497-85b9-454c-a5d1-1dcafa6eed3d -> ../../sdb8 cer@Telcontar:~> How come? Bugzilla? Known issue? I might as well remove the system-sleep/grub2.sleep script as useless... - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAliQddcACgkQtTMYHG2NR9WWhgCePioF3GkkypuX/NMvQVceJx/d QhsAn2nQjwqsX3gv/hANJm/5Z9gv2H2b =8nmt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Multiple 6 and 11 coredumps on tumblerd
by Mikhail Kasimov 31 Jan '17

31 Jan '17

Hello! After 42.1 -> 42.2 via 'zypper dup', I have multiple coredumps (6 and 11) on /usr/lib64/tumbler-1/tumblerd. Can some give a hint how to insvestigate and fix these annoying problems? [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1012138 (SEGV 11) [2] https://bugzilla.opensuse.org/show_bug.cgi?id=1022066 (SEGABRT 6) Thanks fot advice! -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] cfdisk - strange bad behavior in openSUSE 13.2
by Istvan Gabor 31 Jan '17

31 Jan '17

Hello: This occurs in openSUSE 13.2. Whenever I run cfdisk (version: cfdisk from util-linux 2.25.1) after exiting the program the given device is "rescanned" and my desktop is populated with "A new medium has been detected" windows (Trinity desktop), as many as the partition numbers on the disk. dmesg also indicates that the device was "rescanned". For example: # cfdisk /dev/sdd I exit cfdisk without modifying anything 11 "new devices window appears on the desktop dmesg shows: [ 940.463099] sdd: sdd1 sdd2 sdd3 sdd4 < sdd5 sdd6 sdd7 sdd8 sdd9 sdd10 sdd11 sdd12 > If I login from a remote computer through ssh and run and exit cfdisk, the windows appear on the current user's desktop. This is an unwanted behavior. I've been using cfdisk for several years but never seen something similar. How can I stop this? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

Re: [opensuse] HP printer Leap 42.2 solved
by michael norman 30 Jan '17

30 Jan '17

On 30/01/17 11:44, michael norman wrote: > I have two pcs both attached to a BT router. pc1 is my main box and > dual boots 42.2 and Linux Mint 18.1. That one is a Shuttle, about 5 > years old but still fully functional. pc2 is an older tower probably > about 12 years old but again functional. I use it as a back up machine > and because its the most convenient place to put the printer. HP > Deskjest 2300 > > On 30/01/17 11:20, Per Jessen wrote: >> michael norman wrote: >> >>> My HP D2300 usb printer has worked for many years. It is attached to >>> one of my two pcs and shared between the two. This worked fine up to >>> 13.2 but I cannot get 42.2 to share the printer. >> >> Share out or share in? >> >>> Sharing fails in Yast whereas it worked up to 13.2, >> >> On my Leap422 test clients, I have to go into Yast->Printers and enable >> the network listening. After that it works - the client then runs a >> cups-browsed daemon. >> >>> Is there a known fix for this ? >> >> I think we'll need some more info about your setup - where is the >> printer attached etc. >> >> >> > I went into Yast Printers and just enabled sharing to all computers on the local network. works now. M -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Leap42x - playing mpeg video ?
by Per Jessen 30 Jan '17

30 Jan '17

The video player defaults to "Dragon Player", which doesn't appear to be able to play an MPEG file. On my 10.3 machine, I would use kaffeine, but I suspect I must have installed something extra there too. Ah, kaffeine still works - installed, ran it, it asked if I wanted to install extra libraries/drivers - et voila!, I can play mpeg video. Looks like kaffeine ought to be the default instead of Dragon Player (which doesn't even alert me to the fact that it can't play). -- Per Jessen, Zürich (-4.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 14