March 2016 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] leap install messed up mint
by Chris Murphy 30 Mar '16

30 Mar '16

On Tue, Mar 29, 2016 at 12:11 AM, Andrei Borzenkov <arvidjaar(a)gmail.com> wrote: > > > Отправлено с iPhone > > 29 марта 2016 г., в 9:02, Chris Murphy <lists(a)colorremedies.com> написал(а): > > > > On Mon, Mar 28, 2016, 11:44 PM Andrei Borzenkov <arvidjaar(a)gmail.com> wrote: >> >> >> >> Отправлено с iPhone >> >> > 29 марта 2016 г., в 7:09, Chris Murphy <lists(a)colorremedies.com> >> > написал(а): >> > >> >> On Mon, Mar 28, 2016 at 9:24 PM, Andrei Borzenkov <arvidjaar(a)gmail.com> >> >> wrote: >> >> 28.03.2016 07:54, Chris Murphy пишет: >> >>> Long version: >> >>> Basically the distros have a bunch of mutually incompatible forks of >> >>> upstream GRUB. >> >> >> >> >> >> How it is relevant in this case at all? >> > >> > It's the superset position, the ultimate cause for all bootloading >> > madness on Linux. It's not the user's fault they're so often confused >> > about something that should be so basic and reliable. The GRUB2 >> > multiboot experience handed to us by distros is basically crap and >> > it's not really possible to overstate that. >> > >> > This is marginally less crap with upstream GRUB. But it's actually >> > nearly pleasant with systemd-boot (gummiboot) and rEFInd. So it's not >> >> So rEFInd or systemd-boot will ignore file signature and allow you to load >> and launch anything you through at them? Otherwise please explain how using >> different boot loader would change anything here. > > > > My recommendation is the same as when I first posted. Use the firmware's > built-in boot manager. It solves all of these problems, the user doesn't > have to get wrapped up in bootloader esoterics and workarounds. > > > > And how it makes your statements about boot loaders more relevant? I've already answered that question. By repeating it, you're proposing it's not relevant in order to diminish my criticism of GRUB having shit UI/Ux when it comes to multiboot. Even when GRUB multiboot works, it's basically shit. And it being shit even compared to the built-in boot manager is pretty appalling because even that isn't great. But at least if you can figure out how to get to the built-in boot manager, it doesn't face plant with incoherent, unhelpful errors, that then require Rube Goldberg levels of hacks to work around. -- First, get a cat. Then get a spoon. Now, we're going to teach the cat how to use the spoon. Yes, we need to do this to get Linux A's bootloader to boot Linux B, but this is because Linux is so much better. Where's your cat? You need a cat. No of course this isn't documented anywhere. -- User pain and questions go down dramatically when they figure out they can do this more reliably with the firmware's boot manager. And it solves essentially all known multiboot problems whether Secure Boot related or not. User pain and questions go up dramatically when asked to hack GRUB to work around its deficiencies (in pretty much all ways but especially when it comes to multiboot). It's good and necessary for some users to know such things, because who else do we turn to when we need to know how to build and sign our own kernels and get them to work with Secure Boot? But in the meantime, as a general purpose solution, I think it's better for people to give up on GRUB when it comes to multibooting because the experience is shit. And it's not their fault. Why would I recommend something that makes users miserable? -- Chris Murphy -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] oSC16 - Organizing Team Meeting 7
by ddemaio 29 Mar '16

29 Mar '16

Hi all, Today, March 22, we will have an organizing meeting for the openSUSE Conference on the opensuse-project channel at 1700 UTC. I will have the agenda ready for the meeting: The topics we will discuss today are: Social events Planning Entertainment Planning Marketing Status Keynote Status Trello Cards Schedule Outreach/Education Status Volunteer Tasks Equipment update Regards, Doug

1 2

RE: [opensuse] Bugzilla - a question
by stakanov＠freenet.de 29 Mar '16

29 Mar '16

> -----Ursprüngliche Nachricht----- > Von: ianseeks > Gesendet: So. 27.03.2016 14:08 > An: opensuse(a)opensuse.org > Betreff: [opensuse] Bugzilla - a question > > Someone mentioned in the KDEPIM list that bugs can sit here "unnoticed" for > years. Is there anyway of looking at a bug in bugzilla to check if any of the > people assigned to look at it have actually read it other than them actually > making a comment on it or changing the bug status? > > Regards > > Ian > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- Well, if you wish I can tell you. I am one of the reporters that got a bug closed after so may years that I received a letter of apologies for not having received any consideration before the change of generation took place. Bugs can stay there for about 3 years or longer. To know if your bug is looked upon, you should see if it has been "assigned" and at least if it has been "confirmed". If it is just confirmed but not assigned you have a "weapon", which is the vote. You can vote for a bug and some of the bugs that where unbelievably annoying to people, where fixed just because people did vote for it. We as a distribution may have noteworthy power if we put our forces together and get some bug fixed by popular vote if we do coordinate our votes. So I would say, if you have something that "stays on your heard" which is easy as with PIM as a central component, I think that KDE does still not understand the paramount importance for daily usage that this component has, and you may try to argue for a bug here, I for sure would be available to vote in a coordinated matter when it comes for PIM bugs. Others (I think of Anton and Basil :-p) may do so, driven by an act of profound altruism. You let me know what you need, and if I have votes to spare you will get my support. I firmly believe that one of the mayor problems of this otherwise very enjoyable desktop is priority setting. PIM and Kmail (filtering, akonadi etc) are part of it. Bear in mind however that (for what I heard) they are working on a complete rewrite of PIM/Akonadi to drive out design errors and bugs. So if the problems you face will be fixed through this, i am afraid, chances are good that this will be "wontfix" if the devs think it will be obsoleted by the new version anyway. (Which, to tell the truth, I hope so, it is time to get this very central component working and shining, if not other to heighten the reputation of the software collection as a whole). --- 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

3 4

RE: Re: [opensuse] Battery Mis-behaving Recently
by stakanov＠freenet.de 29 Mar '16

29 Mar '16

> -----Ursprüngliche Nachricht----- > Von: John Andersen > Gesendet: Di. 29.03.2016 03:10 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Battery Mis-behaving Recently > > On 03/28/2016 03:22 PM, stakanov(a)freenet.de wrote: > > Was your machine warm after 40 minutes of suspend? That would be an indication it had not fully > suspended, and something was drawing way more power than it should have for a sleeping machine. > > > Now that you tell me that..... I would say yes. Handwarm, not hot. I did not mention it. As it is a Lenovo it should have been cold. Where could I see a log? Does journalctl trace it? I was not thinking of the kernel of a culprit but if you use Plasma5 then I would have a suspect. --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

RE: Re: [opensuse] Battery Mis-behaving Recently
by stakanov＠freenet.de 29 Mar '16

29 Mar '16

> -----Ursprüngliche Nachricht----- > Von: John Andersen > Gesendet: Mo. 28.03.2016 22:23 > An: opensuse(a)opensuse.org > Betreff: Re: [opensuse] Battery Mis-behaving Recently > > On 03/28/2016 01:08 PM, stakanov(a)freenet.de wrote: >> Is this the normal kernel? It really seams like my problem. I did close the lid. The machine apparently suspends. Shows the symbol, no ventilator. But when opening after 40 minutes, the battery is from full to 5 minutes left of time. Either the battery is wrongly indicating power or there is something not suspending at all. Normally when suspended I have autonomy for hours. --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] kstars no device menu
by buhorojo 28 Mar '16

28 Mar '16

Hi 42.1 kstars should have a Devices section under the Tools menu, but it hasn't. We have all the possible libindi packages installed. Without devices, we cannot connect. Can anyone help? Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

RE: [opensuse] Battery Mis-behaving Recently
by stakanov＠freenet.de 28 Mar '16

28 Mar '16

> -----Ursprüngliche Nachricht----- > Von: John Andersen > Gesendet: Mo. 28.03.2016 21:52 > An: opensuse(a)opensuse.org > Betreff: [opensuse] Battery Mis-behaving Recently > > Sometime in the last three months something started really messing > up my battery charge state and runtime. > > Prior to that I could get reasonable runtime, graceful low-battery detection, > proper warnings, and suspend to disk before battery exhaustion. > (runtime wasn't great, (never is in linux) but it was on the order of 3-4 hours. > > Now I get down to 67 percent and BAM! Laptop stops, no warning or anything. > Is this 13.2, 13.1 or Leap? I have here a severe problem with shutdown, with suspend, with battery-power. All with Leap. I lost a whole battery capacity within 40 minutes, which induces me to belief it was not charged fully while indicating it is charged fully. This sound very similar to what you have just around that either my battery was not full or my battery "decided to be empty". Laptop is a X201 with a battery that (following BIOS and age should be close to perfect). --- 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

2 1

[opensuse] Battery Mis-behaving Recently
by John Andersen 28 Mar '16

28 Mar '16

Sometime in the last three months something started really messing up my battery charge state and runtime. Prior to that I could get reasonable runtime, graceful low-battery detection, proper warnings, and suspend to disk before battery exhaustion. (runtime wasn't great, (never is in linux) but it was on the order of 3-4 hours. Now I get down to 67 percent and BAM! Laptop stops, no warning or anything. > > 1458954603 100.000 fully-charged GMT: Sat, 26 Mar 2016 01:10:03 GMT (on wall power) > 1459015753 98.000 discharging GMT: Sat, 26 Mar 2016 18:09:13 GMT (On battery) > 1459015873 96.000 discharging > 1459015993 95.000 discharging > 1459016113 94.000 discharging > 1459016233 92.000 discharging > 1459016353 91.000 discharging > 1459016473 89.000 discharging > 1459016593 88.000 discharging > 1459016713 87.000 discharging > 1459016833 85.000 discharging > 1459016953 84.000 discharging > 1459017073 82.000 discharging > 1459017193 81.000 discharging > 1459017313 79.000 discharging > 1459017433 78.000 discharging > 1459017553 76.000 discharging > 1459017672 75.000 discharging > 1459017792 73.000 discharging > 1459017912 72.000 discharging > 1459018032 70.000 discharging > 1459018152 68.000 discharging > 1459018272 67.000 discharging GMT: Sat, 26 Mar 2016 18:51:12 GMT > Boom! > Plug it in, give it a few minutes, and boot it again (9 minutes lapsed) > > 1459018842 0.000 unknown GMT: Sat, 26 Mar 2016 19:00:42 GMT (plugged in) > 1459021227 0.000 unknown > 1459021392 0.000 unknown > 1459021527 1.000 charging > 1459021752 2.000 charging > 1459021872 3.000 charging > 1459021992 5.000 charging > 1459022232 7.000 charging > 1459022352 8.000 charging > 1459022472 9.000 charging > 1459022592 10.000 charging > 1459022712 11.000 charging > 1459022832 12.000 charging > 1459022952 13.000 charging > 1459023072 14.000 charging > 1459023192 15.000 charging > 1459023312 16.000 charging > 1459023432 17.000 charging > 1459023552 18.000 charging > 1459023672 19.000 charging > 1459023792 20.000 charging > 1459023912 21.000 charging > 1459024032 22.000 charging > 1459024152 23.000 charging > 1459024272 24.000 charging > 1459024392 26.000 charging > 1459024512 27.000 charging > 1459024632 28.000 charging > 1459024752 29.000 charging > 1459024872 30.000 charging > 1459025112 31.000 charging > 1459025232 32.000 charging > 1459025352 33.000 charging > 1459025592 34.000 charging > 1459025832 35.000 charging > 1459026192 36.000 charging GMT: Sat, 26 Mar 2016 21:03:12 GMT > 1459026552 37.000 charging GMT: Sat, 26 Mar 2016 21:09:12 GMT > 1459027152 38.000 charging GMT: Sat, 26 Mar 2016 21:19:12 GMT > 1459027668 100.000 fully-charged GMT: Sat, 26 Mar 2016 21:27:48 GMT > So in the last 6 minutes, it went from 38% to 100% !!! It appears to only charge it to about 38-ish percent, then decides it is fully charged and won't charge it any more. And when discharging, it gets down to 67 percent (consuming that same 38-ish percent) and drops off line. When I noticed my old battery would quickly die after less than 45 minutes I ordered a new one. SAME RESULTS. Both Batteries behave this way. Both batteries behave similarly. Battery statistics are kept separately by Opensuse /var/lib/upower Both batteries have gone through two complete charge - discharge cycles. I don't know if I can blame Opensuse, or Linux, because I stopped the boot process on a fully charged battery, went to the bios, and sat on the battery bios page and watched the indicated percentage drop smoothly to about 65% (43 minutes) and the laptop powered down. The batteries has both convinced themselves that they are dead with 65% remaining, and drop into protection mode (cutoff). Any Ideas? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] USB sound card
by Dr.-Ing. Dieter Jurzitza 28 Mar '16

28 Mar '16

Dear listmembers, I have two sound cards connected to my PC, one (inactive) in the graphics card, a second one (active) connected to USB, mainly acting as an externa DAC. Due to hum problems I had to put an optical insulation device into the connection between PC and USB sound card. Unfortunately I observe disconnects (?) between PC and sound card every other time, resulting in no more sound being reproduced. After this, I have to terminate kmix and amarok and start first kmix, then amarok again and everything works again. This is quite boring - it may happen every other hour, probably (but not reproducable) when I access the (USB ...) printer, however, it often simply happens without an apparent reason. Is any kind soul out there knowing about an adjustable timeout one might configure to prolong the delay until a device gets dropped? The strange issue is: the sound card is still working the very moment I restart kmix (and amarok). Even "service" sounds from kde are produced independent of the operation of both kmix or amarok. By the way, I am using leap & kde. Thank you in advance for any hint, take care Dieter Jurzitza -- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) ----------------------------------------------------------- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Location of Detailed report on failed dependencies
by Terry Eck 28 Mar '16

28 Mar '16

Running the Software Update I get the following message: "Dependency resolution failed A package dependency could not be found. More information is available in the detailed report." The software update is not the one listed under YaST where it appears as "Online Update". It is found along the bottom of the screen and looks like a shield with green check mark. Thanks for any help, Terry -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2