January 2019 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Ready! Set! GO!!!
by Fraser_Bell 15 Jan '19

15 Jan '19

IMPORTANT: DO NOT REPLY ON THIS LIST!!! IMPORTANT: DO NOT REPLY ON THIS LIST!!! Replies or comments should be made on the openSUSE Project Mailing List. ================ *... and they're off!* <url>https://news.opensuse.org/2019/01/15/and-the-race-is-on-2018-2019-opensuse-…</url> <url>https://en.opensuse.org/openSUSE:Board_election#2018-2019_openSUSE_Board_Ca…</url> -- -Gerry Makaro openSUSE Board Elections Committee (election-officials **at** openSUSE.org) openSUSE Member openSUSE Global Moderator openSUSE Contributor YaST Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] TW: xfce4-notes
by ellanios82 14 Jan '19

14 Jan '19

- since recent TW zypper dup , cannot coax 'notes' to get started : trying to start from konsole , this is error message : " ~> /usr/bin/xfce4-notes /usr/share/themes/Breeze/gtk-2.0/widgets/styles:13: error: invalid string constant "toolbuttons", expected valid string constant /usr/share/themes/Breeze/gtk-2.0/widgets/styles:11: error: invalid string constant "scrolled_window", expected valid string constant" - any suggestions what i might try ? thanks ..... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 6

[opensuse] leap 15, Nouveau and kernel 4.12
by Frans de Boer 14 Jan '19

14 Jan '19

Finally changed the default kernel for leap 15. First 4.9.x and now 4.19.15. As expected, I got rid of tearing - mostly the bottom half of the screen - while using KDE zoom functionality. I guessed before that 4.12 had a problem with the Nouveau drivers so I changed to another kernel. Now finally I can use Leap 15 as my production environment. Strange, however, that nobody reported similar behavior before, at least not to my knowledge. Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Anybody find a clean UserChrome.css addition for Rounded Tabs in FF60esr?
by David C. Rankin 14 Jan '19

14 Jan '19

All, Web sites are slowly intentionally breaking compatibility with FF 52.9esr, so I bit the bullet and went to 60.4esr (from the update repo), and I'm trying (valiantly) to make this GTK3 monstrosity look palatable. One of the awkward looking features is the tabs at the top are now just square boxes (that frankly just look ugly, not to mention 40% taller) I have found some rather extensive UserChrome modes on github, e.g. https://github.com/wilfredwee/photon-australis which look pretty good, but seem heavy just to try and make Firefox look somewhat like it did in 52esr (from July) Does anyone have a tweak (or shorter version of the UserChrome additions) that will restore some of the rounded tab features to FF 60esr? Example Comparison of 52 -> 60 (screenshot) http://paste.opensuse.org/view//46109343 -- 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

2 4

[opensuse] Upgrading to OpenSuSE15.0 problems
by Marc Chamberlin 14 Jan '19

14 Jan '19

I am in the process of trying to upgrade one of my computers to OpenSuSE 15.0 and running into a number of problems. I first started with OpenSuSE42.3 x64 with the KDE/Plasma desktop, and I tried to do an in place straight upgrade. I will also mention that my OpenSuSE42.3 system had something broken with the network drivers so I did not have access to the internet directly from it. So I used my laptop to download the OpenSuSE 15.0 iso file and burned it to a DVD. I mention this because I am suspicious that this may be what is causing me some of the problems I am experiencing, though I do not understand why that should be the case. After my first attempt to upgrade my computer to 15.0 it failed to boot. My research lead me to discover that the installer had changed the grub configuration so that it was trying to make calls to linuxefi and initrdefi. I don't use the efi filesystem on this computer and have no desire to do so. (don't get me started on how much troubles I have had with efi. I use it on my laptop only because I am using solid state drives and it seems that I must use efi on it.) My BIOS in the computer I am trying to upgrade has EFI turned off and only uses legacy file management. So I manually edited the grub configuration file and removed the efi suffix of these calls, i.e. made calls to linux and initrd instead, and the boot up succeeded. However, that lead me to another mess, after logging in to my account, I discovered the KDE/Plasma desktop was not working properly. I had a few konsole windows that opened up (ones I had left open when I brought the system down) but the plasma part of the desktop was not there. No background, no kicker bar, no mouse activity or the ability to right click and bring up the pop up menu dialog etc. In other words almost useless, although all the services and background tasks I have configured to run started up fine. (things like Apache, Tomcat, Bind, DHCPD etc.) I don't know how to recover from this mess, I tried reinstalling all the KDE and Plasma packages but no joy, so I decided to try a different approach - My next attempt was to install OpenSuSE 15.0 into a new/separate partition but I cannot get past the partitioner. It appears it is trying to force me into using the EFI boot system. I don't allow the OpenSuSE installer's partitioner to decide for me (it's defaults) how to configure my system as it makes choices that I don't want. Instead I have it import all my mount points that I have defined in what was my OpenSuSE42.3 (now upgraded to a broken 15.0) system. That much works fine and I just move the mount point for / to a new partition so that the new OpenSuSE15.0 system will be mostly installed in a different partition and I can keep my old system for the time being. However when I tell the partitioner to accept all the new changes I get a complaint - "Missing device for /boot/efi with size equal or bigger than 256MiB and filesystem vfat." Why am I being forced into using EFI? My system/BIOS is configured to use the legacy boot loaders and explicitly turns off EFI! I cannot find any means of telling the OpenSuSE installer/partitioner to use the legacy method of boot loading either, so I am stuck. I have one other complaint about the OpenSuSE 15.0 installer/partitioner that I want to pass along as it almost destroyed my entire system, had I not caught it. After I told the partitioner to import all my mount points from my previous system, I fortunately observed that it had marked ALL of my mount point partitions to be formatted!!! That is just plain wrong, the user should NEVER have to opt out of having data destroyed, but have to opt in to having anything formatted. That modus operandi really needs to be reversed, formatting of any partition should never be done by default. I will listen to any arguments to the contrary but I feel pretty strongly that this should be reported as a bug and fixed. (I am willing to do so.) Appreciate any thoughts on how to install OpenSuSE 15.0 using the legacy boot loaders and not use EFI booting? Sorry for the long writeup and please forgive me if I didn't communicate this technically correctly, this is definitely not my area of expertise! ... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 12

[opensuse] rhythmbox apears to fail after 42.3 upgrade all
by don fisher 13 Jan '19

13 Jan '19

I performed an zypper up upgrade to a 42.3 system, and now rhytmhbox fails to load. Any solutions known? don -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] TW: xfce4-notes will not execute
by ellanios82 13 Jan '19

13 Jan '19

TW: my xfce4-notes has ceased to function : getting message: " > /usr/bin/xfce4-notes /usr/share/themes/Breeze/gtk-2.0/widgets/styles:1: error: invalid string constant "default", expected valid string constant /usr/share/themes/Adwaita/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant /usr/share/themes/Breeze/gtk-2.0/widgets/styles:4: error: invalid string constant "entry", expected valid string constant /usr/share/themes/Breeze/gtk-2.0/widgets/styles:4: error: invalid string constant "entry", expected valid string constant /usr/share/themes/Adwaita/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant" .... regards -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] Prometheus woes
by Dave Howorth 12 Jan '19

12 Jan '19

OK, another silly question. Does anybody use prometheus? I just installed it but I'm not having much luck getting started with it. I installed it fromthe Leap 15.0 repositories. It runs and --version tells me: prometheus, version 2.1.0 (branch: non-git, revision: non-git) build user: abuild@lamb69 build date: 20180513-03:46:03 go version: go1.9.4 so at least it runs. I can't find any opensuse docs to tell me about anything specific (no man page in particular) so I'm relying on the 'Starting' section in https://prometheus.io/docs/introduction/first_steps/ which is not brilliant. I first tried running as my own user and failed with lack of permission to create /var/lib/prometheus/metrics so then I tried as root, which seemed to work but seems a bit weird, so then I tried user prometheus and that worked too, so is probably right, but it would be nice if there was opensuse docs to say so, and/or something on the web page to indicate it. Anyway, I then fired up a browser and pointed it at http://localhost:9090/graph and got a display. But it doesn't seem to work like https://prometheus.io/docs/introduction/first_steps/ says it should. I assume it means 'choose the "Console" view alongside the "Graph" tab' as opposed to what it does say. But it just says 'no data'. I assume that 'the expression console' is the text box at the top of the screen but nothing happens when I put the recommended string into it, and if I hit Execute, it says 'No datapoints found' Prometheus appears to log to the console where it was started, but apart from some messages saying it has started, there's nothing to indicate any problems. In /var/lib/prometheus/metrics/wal I have two files, one is 434K and the other is 256M so it's certainly storing something! What it is if not datapoints is beyond me. So anybody know what's going on? Or can point me to some better/more accurate documentation? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] TW: xfce4-notes unstable : keeps closing itself
by ellanios82 11 Jan '19

11 Jan '19

TW: - am experiencing xfce4-notes refuses to remain open : executing from konsole , i see message : ":~> xfce4-notes (xfce4-notes:3974): Unique-DBus-WARNING **: 00:20:16.444: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. /usr/share/themes/Adwaita/gtk-2.0/hacks.rc:28: error: invalid string constant "normal_entry", expected valid string constant" - ideas please what to try first thanks ..... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Recommendations for Markup syntax format
by Sébastien 'sogal' Poher 11 Jan '19

11 Jan '19

Hi all, I have a project that implies writing quite a lot of technical documentation. By "technical", I mean it will include: - list, numbered and unnumbered - a few tables - hypertext links of sources - a lot of footnote - excerpt of code and command lines - images - side comments (i.e. more detailed explanation about a word or notion that can't be included inline, so it won't break reading flow, but rather in side or foot notes) I already use Markdown (common markdown) a lot but I think it will be limited for my goal here. I consider using reStructuredText or AsciiDoc as I have heard that they are pretty efficient and standard format for documentation. I guess that some of you already use one of those. Do you have any advises about which one should I choose, any pros and cons of each ? Thank you in advance. Regards, -- Sébastien Poher -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 5