openSUSE Users June 2015

users@lists.opensuse.org

92 participants
110 discussions

by Michael Fischer

Hi all. Upgraded the laptop to 13.2 from 12.3. Alsamixer and Yast2 both show master and PCM at 100%, but apps seem to have much lower volumes during playback. Now, it _could_ be the vlc version in part.. that's where I notice the volume difference the most. Previous installation was i | vlc | package | 2.0.6-127.2 | x86_64 | (System Packages) Currently installed is: i | vlc | package | 2.2.0-146.1 | x86_64 | (System Packages) Any notions what knobs I could try twisting? I _did_ notice the prior thread and tried changing /etc/pulse/daemon.conf ; flat-volumes = yes to flat-volumes = no With no appreciable result after restarting pulseaudio and checking with `pulseaudio --dump-conf`. TIA, Michael -- Michael Fischer michael(a)visv.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 years

[opensuse] Re: OFF LIST Problems with GRUB/GRUB2

by Felix Miata

Anton Aylward composed on 2015-06-25 08:53 (UTC-0400): > Felix Miata wrote: >> Anton Aylward composed on 2015-06-24 22:00 (UTC-0400): >>> Feeling paranoid about it ... >>> See if this works! >> I don't understand if you are asking a question or telling me something I >> don't get. Ping! >> https://bugzilla.opensuse.org/show_bug.cgi?id=839081 tells me you should not >> try more than one checkbox at a time in YaST2 Bootloader. As I have neither >> Grub2 nor LVM, it's nothing I could check. > Part of the reason, I think, that Windows and OSX "just works" is that > users aren't allowed to make decisions like this. > "Where should I put the MBR?" > And answer like "Well, everywhere, just to make sure!" > is perfectly reasonable, sn't it? > Isn't it? Of course! So did you try again selecting one choice only? Maybe a comment in the bug that it seems not to have gotten fixed is in order? Devs spend too much time making stuff "better" and fixing others' "improvements", kicking sleeping dogs, than ensuring "improvements" aren't breaking stuff. Did you set reply-to to opensuse list in your message an hour before this one on purpose? -- "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

7 years

[opensuse] I appear to have lost my thunderbird settings ?

by Per Jessen

After a crash yesterday, thunderbird came up and suggested I set up a new email account - I have 3 accounts defined, but they were gone. I checked the .thunderbird directory, also checked the backup, all looks good. There must be something, somewhere that tells TB which profile to use? -- Per Jessen, Zürich (15.9°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 years

Re: [opensuse] Problems with GRUB/GRUB2 (was: OFF LIST...until reply-to-list was set)

by Felix Miata

Anton Aylward composed on 2015-06-25 07:57 (UTC-0400): I don't get why OFF LIST emails are going out set to reply-to-list. > Felix Miata wrote: >> Anton Aylward composed on 2015-06-24 21:54 (UTC-0400): >>> Felix Miata wrote: >>>>>> no, I don't have dracut for 13.1 >>> If I'm reading things right, the problem isn't going to be solved by >>> drakut. As far as I can tell, drakut is a replacement for mkinitrd. >> Technically quite correct. As a practical matter, I'm not so sure. On 13.1 I >> use either stock kernels, or these: >> http://download.opensuse.org/repositories/home:/mkubecek:/evergreen-13.1/op… > Has 13.1 gone evergreen already? Wiki might still say so. I didn't check lately. Answer is no. That's supposed to happen after current TW morphs into a post-13.2 GA release. > As noted, I use Kernel_stable. >>> As far as I can tell, mkinitrd is working OK. >> Hopefully. > Once we start doubting the fundamentals we're on a downward spiral. That happened with 12.1, aka systemd. > All I can say is that the various initrds work. So you're running now on 4.0.5, just bootloader config is broken? >>> As far as I can tell its >>> is rebuilding /boot/grub2/grub.cfg correctly >> IIRC, mkinitrd/dracut on kernel installation/upgrade only trigger bootloader >> updates, not do them. I think it's perl-Bootloader that calls on the >> grub/bootloader scripts. > To be honest, I'm not sure that a kernel upgrade SHOULD cause a > bootloader update. The thing in the MBR, the stage1/stage2 code of > "0.97" or the .mod files of "2' have no reason to change, on the config > files that define the menus. I agree in general. If you aren't booted from rescue media, what's already in MBR and EBR apparently works, sleeping dogs that do not need disturbing. "Bootloader update" can be either or both of two things: 1-binary "installation" or "setup" 2-configuration (boot menuing) Of course, the latter needs changing with every kernel change, unless relying exclusively on symlinks, which most distros including openSUSE do not by default, if ever, attempt to do. On my own installations, normal booting is always via symlinks. >>> The problem is that grub2 is not doing what I think it should. >> I think that's due to bug I gave in previous email. >>> I've tried doing what *I* think is reinstall grub2 and in the MBR, I think you somehow failed. What else, other than a bug you and I know nothing about, explains the GRUB halt? >>> that you YAST, that you command line. >> I do not understand your grammar here. >>> I've described what happens. >>> I think this is a MBR or whatever problem >> Maybe it's both initrd and bootloader. Clearly bootloader is at least part of >> problem to be dumping you at GRUB. >>> not a specific mkinitrd/drakut problem. >> Were you using kernel-stable before, or were you using 3.11 or 3.12 >> previously? > I've been using kernel_stable for all of this year. > I'm well into the 4.0 series now > # ls -1 /boot/vmlinux* > /boot/vmlinux-3.19.3-1.gf10e7fc-default.gz > /boot/vmlinux-3.19.3-1.gf10e7fc-desktop.gz > /boot/vmlinux-4.0.5-3.gb5e86cc-default.gz > /boot/vmlinux-4.0.5-3.gb5e86cc-desktop.gz > /boot/vmlinux-4.0.5-4.g56152db-default.gz > /boot/vmlinux-4.0.5-4.g56152db-desktop.gz > /boot/vmlinux-4.0.5-5.g80f6bcd-default.gz > /boot/vmlinux-4.0.5-5.g80f6bcd-desktop.gz > /boot/vmlinux-4.1.0-1.gfcf8349-default.gz > /boot/vmlinux-4.1.0-1.gfcf8349-desktop.gz > There's a purge_kernels pending. You actually enabled purge-kernels.service? System installation (YaST/PBL) doesn't do it. > I have > multiversion.kernels = oldest,latest,latest-1,latest-2,running 2 more than default. >> Have you looked for mention of mkinitrd or dracut in the >> kernel-stable changelog or man page? > The changelog has a lot that is irrelevant to me: atuff to do with ARM, > modules I don't use like crypto, XEN. The stuff that is relevant is all > BtrFS stuff. IMO, BTRFS is good rationale to upgrade the whole OS, not just kernel, unless you know about and also upgrade everything that touches BTRFS. All I know about BTRFS is it's too new for me to want to touch. It's only been about a year since I started using EXT4 instead of EXT3 on new installations, and then only on 64 bit installations, the far less-used arch here. > mkinitrd is 2.8.1-9.1 and the last changelog entry is Mon 06 Oct 2014 > 08:00:00 AM EDT. > The grub2 changelogs are 2013/2014. >> I suspect kernel-stable sees little >> service or testing on 13.1. Also, kernel builders are probably all using a >> much more evolved systemd than that in 13.1, plus newer compiler. > Evidence? Keyword: suspect. Actual evidence escapes my recollection. It's more about what I don't see than what I do. I keep irc://freenode/#opensuse-factory open, but visit it only at random. There is probably a lot on opensuse-factory mailing list I miss because of skipping many threads based purely on $SUBJECT. I miss even more for that reason and others on kernel, project, yast-devel and packaging lists. > So you are saying 'upgrade to 13.2 cos that's where the real action is'. I wasn't, though I can understand such an interpretation. IMO, the real action isn't even in TW, but in TW as a foundation, plus widely varying portions of OBS. >> Maybe along >> the way something prudent is, after restoring bootloader menu functionality, >> booting prior kernel to get latest dracut installed and trying it via cmdline >> on kernel-stable. > I see no logic in that. Seeing no logic makes sense, as long as you're fully confident your trouble is exclusively with bootloader. > * I see no reason to start using dracut with 13.1 other than to 'learn > about it' Maybe this is a problem that you and I don't know about. > * I see no reason to worry about 'prior kernels'. +1 if that's how you've booted since the s*** hit your fan yesterday. > The problem is getting the boot loader to work at all. It *is* working "at all" now, no? You're getting a grub> prompt and getting kernel and initrd to successfully boot your 13.1 installation, no? If true, this seems to me like the above-referenced bug has caused Grub Legacy to be installed (aka setup) on MBR (and/or PBR???) without any corresponding menu configuration. It needs /boot/grub/menu.lst, not /boot/grub2/grub.cfg. I think you'll find you have both Grub Legacy and Grub2 rpms installed, as is normal even in TW. Here's something else to think about: Anton Aylward composed on 2015-06-24 19:56 (UTC-0400): > This was a 'new' 1T that I partitioned as root & swap are real > partitions and a LVM > # Start End Size Type Name > 1 34 3906250 1.9G BIOS boot parti primary > 2 3907584 15624191 5.6G Microsoft basic primary > 3 15624192 1953523711 924.1G Linux LVM primary How did you manage to have such a small (34 sector) boot "track"? Are those 4k sectors being used as 4k sectors? Can your new (from updating) Grub2 core.img with LVM and BTRFS support fit in such a space if what are logically used are 512 bytes? Has its tail managed to roll into your swap partition? Why isn't your swap partition labeled as swap by fdisk, or is it actually an M$ partition? Was GRUB happening because Grub Legacy's MBR sector was installed (due to bug) but does not support 4k? -- "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

7 years

[opensuse] Lists seem down :-?

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No email since yesterday at 21:05 UTC. Strange... - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlWKmPwACgkQtTMYHG2NR9UZswCfV6ndDcVP+vDqhp+oiQjkKII7 sOQAn2Rb0HUFXCiYfhRrO0qJaIGNcgIP =s9Bi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 years

[opensuse] Re: OFF LIST Problems with GRUB/GRUB2

by Felix Miata

Anton Aylward composed on 2015-06-24 17:07 (UTC-0400): > Felix Miata wrote: >> Maybe this is a question for the factory list. Default in 13.1 is mkinitrd. >> Newer kernels are expected to be used with dracut. Somebody could have >> forgotten about that in doing some reconfig for gcc5 or something like that. >> Or, "unsupported" translates to simply requiring dracut rather than mkinitrd. > maybe I should bite the bullet and upgrade to 13.2 > no, I don't have dracut for 13.1 I think you can get it from OBS if not from standard repos. IIRC there is a required newer version for the OBS kernels like you installed. -- "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

7 years

[opensuse] Dual Administrative Access?

by Lew Wolfgang

Hi Folks, I'm stumped on this one. I've been asked to configure an area in a filesystem that enforces the concept of requiring two users to agree to remove files from that area. Someone suggested using SeLinux, a system I know very little about. Does anyone know how to require the permission of two logged-in users to remove a file or directory? How would one prevent root from removing the files? Thanks, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 years

[opensuse] Install troubles on E-machine EL1352 with Compaq FP745A monitor

by andredo＠wxs.nl

All my trials to install the last four snapshots or 13.2 ended after the restart in a green screen with a rectangle with two maps; 'home' and 'thrash'. I could than create some other rectangles but no progress. What is going wrong? Suggestions please André den Oudsten -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 years

[opensuse] How to network with a VM?

by Olav Reinert

Hi, I'm running GNOME on openSUSE 13.2 with all updates. Using yast, I have set up a KVM hypervisor, and installed opensuse 13.2 in a VM. Using virt-manager I can run the VM and interact with its GUI. I can open a browser in the guest and surf the net. So far so good. Now I want to SSH into the VM, and I can't figure out how to do it. sshd is running in the guest, its firewall is disabled, and its IP-address is 10.0.2.15. Yet, trying to ssh to connect to that address doesn't work. What do I need to do to be able to contact a server process in the VM from the host? Regards, Olav -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 years

[opensuse] BTRFS mailing list

by Moby

Is the BTRFS mailing list at linux-btrfs(a)vger.kernel.org active? I have sent subscribe messages to it with no response ... -- --Moby -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 years

← Newer
1
2
3
4
5
6
7
...
11
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 June 2015