openSUSE Users July 2016

users@lists.opensuse.org

76 participants
97 discussions

by Carlos F. Lange

Anyone up on the weekend? The page https://software.opensuse.org/search is throwing an error: "Error connecting to http://download.opensuse.org/tumbleweed/repo/oss/suse/setup/descr/appdata-8…: Response was: #<Net::HTTPNotFound:0x00000006efad70> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <html> <head> <title>404 - Not Found</title> <style type="text/css"> body { font-size: 62.5%; } #container { font-size: 62.5%; max-width: 600px; margin: auto; margin-top: 2%; border: 4px solid #efefef; padding: 0px 20px; color: #444; font-family: Verdana,helvetica,sans-serif; font-size: 1.25em; } h1 { color: #6D84B4; font-size: 1.5em; } #footer { text-align: right; margin-top: 25px; } </style> </head> <body> <div id="container"> <h1>Error 404 - Not Found</h1> <p>The requested resource was not found.<br>Make sure you entered the correct URL in your browser.</p> <p id="footer">lighttpd/2 - openSUSE is good for you</p> </div> </body> </html> " -- Carlos F Lange Gaúcho nas Pradarias https://www.google.com/+CarlosFLange -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

[opensuse] Plasma debug symbols?

by Mikhail Ramendik

Hello, I had a sudden Plasma crash yesterday, complete with the monitor getting stuck in SLeep mode for a few minutes. KDE failed to send an automatic bug report because it had no debug symbols and could not install them. How do I install debug symbols, so that if the crash repeats a bug report can be sent? I tried yast and could not find an applicable package. -- Yours, Mikhail Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

[opensuse] K3b (Version 2.9.90+git20160111.2358-11.7-x86_64 - packman) and ISO burning

by ianseeks

HI I've been trying to burn a iso of Windows 7 i downloaded but it just opens the window to say its its preparing and the progress does not go any further than 0%. It has caused some strange performance issues. if i load system monitor, it shows "kuiserver" upto 30%+ cpu and i've also had a systemd_coredump (i think that was what it was called). I've sometimes had to use Ctrl Backspace to kill the session to log out. I was just wondering if anyone else is having this problems with this version from packman. Regards Ian -- Qt: 5.6.1 KDE Frameworks: 5.24.0 kf5-config: 1.0 plasmashell 5.7.1 Kernel: 4.6.3-1-default "openSUSE Tumbleweed (20160710) (x86_64)" -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

[opensuse] cannot open KDE session anymore

by Frédéric Bron

Hi, I cannot open a KDE session anymore. I enter my login+password and then nothing happens, the computer is blocked. With Ctrl+Alt+F1, I can switch to text mode root session and see that the following processes are running for my user account: systemd, (sd-pam), dbus-laun..., dbus-daem..., at-spi-bu..., dbus-daem..., at-spi2-r... What does that mean? The other accounts work well. Regards, Frédéric -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

[opensuse] external speakers OK in 13.1, 13.2, TW; but NOT in 42.1

by Felix Miata

SFF Dell Optiplex 780 has an internal speaker that's supposed to work only if the external speaker jack is not occupied. It works as expected in 13.1, 13.2, TW installed to HD, and in Knoppix 7.6.1 DVD with kernel 4.2.6. 42.1 behaves as though the external speaker jack is not occupied, producing sound from aplay and speaker-test only from the internal speaker, not loud enough to hear unless nothing else in the room is making any sound, and then barely so. This is so with 42.1 kernels 4.1.15, 4.1.21 and 4.1.27, and with TW's 4.6.3 kernel. Content of /etc/modprobe.d/ seems to be identical between TW and 42.1 except that 42.1 has a 50-sound.conf file that TW does not, which if present during boot, causes no such device-type errors trying to use speaker-test and aplay with no parameters, and changes output of /proc/asound/cards to 1 instead of 0. VOODOO - making 50-sound.conf visible, rebooting, testing with -Dplughw:1 made external speakers work. Then removing 50-sound.conf visibility and rebooting again, made sound work one boot with either -Dplughw:0 or no option at all. Then I removed the TW kernel, rebooted, and found it was back to using the internal speaker. Next I tried configuring the sound card with Yast's quick automatic method. It created a new 50-sound.conf file. I rebooted. No change, so I redid it with normal setup method. Sound remains on the internal speaker. Besides creating 50-sound.conf, what did Yast actually do. How does one proceed to find a solution? Is this a case for filing a bug? http://fm.no-ip.com/Tmp/SUSE/421/ contains: 1: alsa-info-gx780-s421.txt is output from alsa-info.sh with output of 'lsmod | grep snd' and a selected short list of installed sound rpms appended 2: http://fm.no-ip.com/Tmp/SUSE/421/snd-gx780-stwk3.txt contains from TW: a.list of files in /etc/modprobe.d b.aplay -l output c.aplay -v /usr/share/sounds/alsa/text.wav 3: http://fm.no-ip.com/Tmp/SUSE/421/snd-gx780-s421tde.txt contains from 42.1: d.list of files in /etc/modprobe.d e.content of /etc/modprobe.d/50-sound.conf f.aplay -l output g.aplay -v /usr/share/sounds/alsa/text.wav -- "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(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

[opensuse] xrdp server questions

by Greg Freemyer

All, I do 80% of my openSUSE work at the command line the last few years, so I have little X/KDE/Gnome experience. What little GUI activity I have is in openSUSE VMs that I use to experiment with and none of it remote. I setup a Leap 42.2 test machine with nice new desktop PC hardware.. I decided to access it via RDP from my windows laptop. After installing the xrdp server and starting the service, it is working great in general. The only surprises so far are: - I can log into the machine with multiple simultaneous logins (3 at once so far). I can login as me at the main console, and from 2 Windows PCs simultaneously. Each login is unique. That is perfectly fine. - Among those 3 concurrent login sessions, I can only launch one instance of Firefox total. If I try to launch it from a second session I get an error: ("Firefox is already running and is not responding ...."). Is that a long-term well known bug? Or is it a bug unique to Leap 42.2? - I keep getting a dialog box asking for the root password. It seems related to a background check for security updates. "Authorization is required to refresh the system sources." The application's vendor is "The PackageKit Project". It provides PIDs too if that is helpful. Is that just because I'm using XRDP, or is there a bug? Thanks Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

[opensuse] Cura and Repetier for SuSE 13.1 ? Other 3D printer software with SuSE 13.1?

by MarkusGMX

I was trying to put Cura ( https://ultimaker.com/en/products/cura-software ) onto my SuSE 13.1 system, found out that there is only a fedora rpm thing, had to install mock from fedora, just to finally realise that it all fails because of missing createrepo_c which is not available for SuSE 13.1 according to https://software.opensuse.org/package/createrepo_c :-( Is there any way to get official packages for Cura and Repetier for SuSE 13.1 ? (I've only seen untrusted versions here: https://software.opensuse.org/package/Cura ) Which other 3D printer software can I use with SuSE 13.1 ? Thx in advance ME -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

Re: [opensuse] cannot open KDE session anymore

by stakanov＠freenet.de

> -----Ursprüngliche Nachricht----- > Von: Frédéric Bron > Gesendet: Sa. 16.07.2016 11:44 > An: oS-en , > Betreff: Re: [opensuse] cannot open KDE session anymore > >> Try to login as that user in text mode. I understand that you logged as >> root ("switch to text mode root session"). Once there, check free space >> on all partitions (df -h). > > Free space: > devtmpfs 7.9 G (/dev) > tmpfs 7.9 G (/dev/shm) > tmpfs 7.9 G (/run) > tmpfs 7.9 G (/sys/fs/cgroup) > /dev/sda2 63 G (/) > /dev/sdb1 228 G (/home) > /dev/sda1 831 M (/boot) > >> Then try to login in graphics mode as that user but with another >> desktop, not KDE. > > Tried IceWM, came back to thé session manager. > Plasma 5 gives the same as the default KDE plasma workspace. > > That's all what I have... > Do you use Leap or 13.2? What is your graphic card? What is your graphic card driver? What is your KDE version (in case it is not the standard version of the distribution). Did you try to start the system in "safe mode" to see whether you can login then? >> >> Also, say what openSUSE version you are using. > > Leap 42.1 > > Cheers, > > Frédéric > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

[opensuse] Building a mid-range desktop PC - lower cost MB/CPU/video solution?

by Greg Freemyer

All, By chance, I've built a couple high-end tower PCs in the last year. $1500-$2500 each Now I want to build one closer to $500, but I want to have as much commonality as makes sense. Definitely the same case for cosmetic reasons. I'm hoping I can save a lot of money in the CPU/video selection, and also I will use a lot less RAM this time. == The $500 desire doesn't include a HDD/SDD. (I've got spare SSDs I can use, and I just ordered a small NVMe SSD to experiment with, so I won't count it in this budget if this is where it ends up permanently.) I don't need screaming speed, etc. and I'm happy with the cheapest graphics solution I can get. These are the core components I bought last time: Termaltake V51 case - $100 (mandatory for this build. I want it to look the same.) AsRock X99 MB - $175 (It would be very nice to use again, but not mandatory.) i7-5820K 3.3GHz - $370 (don't need) Asus Radeon RT 360 - $120 (don't need) === Is there a reasonable cost CPU w/integrated graphics that I can use with the X99? Or is there a different MB/CPU/Video solution I should consider that might be closer to $200 combined? Thanks for input Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

[opensuse] Simple SRs to include docs from the tarball in the RPM

by Greg Freemyer

Adding in opensuse, since this thread drifted on-topic! On Wed, Jul 6, 2016 at 1:21 PM, Carlos E. R. <robin.listas(a)telefonica.net> wrote: > On 2016-07-06 15:52, Greg Freemyer wrote: >> On Wed, Jul 6, 2016 at 8:15 AM, Carlos E. R. > >> === >> Getting dangerously close to on-topic, but take a look at this simple >> SR I did last night: >> >> https://build.opensuse.org/request/show/406894 >> >> I suspect everyone active on this mailinglist has the technical skills >> to create SRs of that type. > > Well, you have to know spec files :-) > When I notice those mistakes, I write a bugzilla instead. 5 years ago the openSUSE devs would ask for bugzilla entries. Now they strongly prefer SRs. And they aren't that hard to do for simple issues. On the -factory mailinglist, the devs often ask for SRs, not bugzilla's. > >> fyi: >> The %doc directive in a tarball is special and a knowlegable user can >> do a package install and leave the docs uninstalled, so as far as I'm >> concerned there really isn't any good reason not to add the docs to >> the rpms. >> >> rpm --excludedocs > > Interesting. Was not aware of it. But disks are large, no problem for > most people installing all docs, just in case. > > Perhaps a switch in YaST or zypper config file to disable docs. > I didn't look. As you say, not something I worry about. RE: large disks - SSDs are becoming the norm and even 125 GB is over $50, so for me space is becoming important again on some of my machines. Also in VMs space can be important. >> For some of the packages I care about, I've written and/or updated >> README.suse files and added them a package via SR. >> >> Here's an example: >> https://build.opensuse.org/request/show/304713 > > Well, thanks. > > I might modify or add to a readme, but a SR is still beyond my abilities. SR => Submit Request To modify a readme you have to do a SR: ===== One time setup === - via web browser login into build.opensuse.org (with your normal bugzilla creds) When you do that that first time your home project is setup. You only have to do that once, but you MUST do it before you can do anything from the command line, etc. - from your openSUSE CLI sudo zypper in osc quilt mkdir ~/obs (Or whatever top level dir you want to use. I like obs for this) osc ls Archiving (answer questions about creds) Archiving is just a relatively small project that is easy to list out, but it won't work until you have your home project and credentials setup. ==== End of one time setup ==== - from your openSUSE CLI cd ~/obs (or whatever you named your top level working dir) osc bco <package> # by default the above: # - determines the devel project for the package # - creates a new sub-project in your home project to hold the branch # - branches a copy of the package from the devel project to the new sub-project # note the name of the sub-project that this command created ls # verify the new directory was created cd <new_project_dir> ls # verify a directory exists for the package you want to work on cd <package> # to edit an existing README.suse (etc.) vi README.suse osc vc (to create a changelog describing your edit) osc diff (to confirm you've made the changes you want) osc commit (commits the changes back to YOUR sub-project on the server) osc sr (send the change to devel project maintainer) Once your SR is accepted, you can delete the sub-project. (I do it via the webui, or you can use osc.) > -- > Cheers / Saludos, > > Carlos E. R. > (from 13.1 x86_64 "Bottle" at Telcontar) Pat yourself on the back for having made a semi-permanent change to a openSUSE package. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 years, 11 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users July 2016