October 2013 - openSUSE Users - openSUSE Mailing Lists

Re: [opensuse] System Up-gradation: How to eradicate extra files & unusable files
by AP 08 Oct '13

08 Oct '13

And even while using "zypper up" I get a warning: ================== Retrieving repository 'Packman Repository' metadata ----------------------------------------------------------------------[|] File 'repomd.xml' from repository 'Packman Repository' is unsigned, continue? [yes/no] (no): ================== Should I continue with yes or no due to security issue(s), if any exist(s). Thanks. -- Life and death. At some point we're gonna leave this world. Do I know when? Absolutely not. --- Terrell Owens Just I dislike pain, so all other beings dislike pain. Live and let live. --- Mahavir Bhagwan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] System Up-gradation: How to eradicate extra files & unusable files
by AP 08 Oct '13

08 Oct '13

On Tue, Oct 8, 2013 at 1:51 AM, David Haller <dnh(a)opensuse.org> wrote: > I'm missing a "zypper clean" here. Oh thanks. And even now I run this command to get the output: "All repositories have been cleaned up." -- Life and death. At some point we're gonna leave this world. Do I know when? Absolutely not. --- Terrell Owens Just I dislike pain, so all other beings dislike pain. Live and let live. --- Mahavir Bhagwan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] System Up-gradation: How to eradicate extra files & unusable files
by AP 07 Oct '13

07 Oct '13

Hi, I had openSUSE 12.2 with KDE paltform. I upgraded from "zypper dup". The exact process I followed was from the root login and was as follows: zypper repos --uri zypper refresh zypper update zypper lr sed -i 's/12\.2/12\.3/g' /etc/zypp/repos.d/* zypper ref zypper dup in order from the first. It worked and now over. Then I run: zypper patch zypper up Now, I have 12.3 KDE openSUSE. But Totem player was working. So, for that, I just searched for "gstreamer-plugins" in the YAST and installed all the files containing this name. Since it was a GNOME application, I was installing in KDE. Apart from it, there could possibly be many files which were installed and not used in the Totem player (because of the installation method used). So how can those be all recognized and eradicated, simply because they won't be used any more any time! Apart from it, after having 12.3 desktop, how should I know that there are no more old files or conflicting files, though I have removed the Orphaned Packages from Yast. Thanks. The totem player was working fine in 12.2 but after up-gradation is not gstreamer-plugins -- Life and death. At some point we're gonna leave this world. Do I know when? Absolutely not. --- Terrell Owens Just I dislike pain, so all other beings dislike pain. Live and let live. --- Mahavir Bhagwan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] Drive, space and usage
by Duaine Hechler 07 Oct '13

07 Oct '13

I am upgrading from 500GB to 1TB drives. The 500GB drives are 99% full. After I do the initial upgrade, how is the data spread across the drive ? Contiguous from front to back like Windows FS ? Or evenly spread (but contiguously) across the drive ? Ultimately, I'm trying to figure out - is the front of the drive going to get the brunt of the work or is the data going to be scattered across the drive. General layout: root (/) swap /home (rest of drive) TIA, Duaine -- Duaine Hechler Piano, Player Piano, Pump Organ - Tuning, Servicing & Rebuilding (314) 838-5587 / dahechler(a)att.net / www.hechlerpianoandorgan.com Home & Business user of Linux - 13 years -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 65

Re: [opensuse] System Up-gradation: How to eradicate extra files & unusable files
by AP 07 Oct '13

07 Oct '13

On Mon, Oct 7, 2013 at 11:30 PM, John Andersen <jsamyth(a)gmail.com> wrote: > Trying to root out any un-used configuration files is also probably not worth > the effort. Many times the update process will put new configuration files in > with an additional extension (.rpmnew) but leave your existing one in place and > in use. I suppose you could purge these, but they don't harm you and might be > useful in the future. > So short answer: Don't bother. Okay, so ultimately its okay! -- Life and death. At some point we're gonna leave this world. Do I know when? Absolutely not. --- Terrell Owens Just I dislike pain, so all other beings dislike pain. Live and let live. --- Mahavir Bhagwan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] network (wifi) occasionally dropping out
by Peter 07 Oct '13

07 Oct '13

Until recently I was using the same laptop at the same address I've been at the last few years, and I never had any problems with the wifi connection to the router. The wireless interface is the ipw2200. Then I got another secondhand laptop with the iwl4965 interface. I've noticed in KNetworkManagement the signal strength never appears as high as on the other laptop, but most of the time I have no problems. Every now and then, however, maybe every couple of days or so, connectivity goes haywire. Sometimes if I switch the hardware wireless switch off and back on again, I'm back to normal. Sometimes I try that, I restart, I go mad tearing my hair out and have rebooted the router and the problem can persist for a couple of hours or so. At first I was running both machines side-by-side and I thought one might be 'stealing' the signal from the other because things seemed worse when they were both on, and less comprehensively I've now had the odd similar problem on the old machine when the new one isn't running. I tried changing the wireless in YaST to traditional setup using Qinternet. There I can do a soft hang-up and restart, which also sometimes works, but not always. Trying to browse to the router homepage at 192.168.1.1 often doesn't succeed at these times. I know nothing about pinging generally so maybe I'm doing something stupid here, but the peculiar thing is that when trying to ping 192.168.1.1 I consistently get results like these: PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=2.97 ms 64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=2.87 ms 64 bytes from 192.168.1.1: icmp_seq=30 ttl=64 time=4.57 ms 64 bytes from 192.168.1.1: icmp_seq=36 ttl=64 time=2.90 ms 64 bytes from 192.168.1.1: icmp_seq=39 ttl=64 time=6.68 ms ^C --- 192.168.1.1 ping statistics --- 39 packets transmitted, 5 received, 87% packet loss, time 38004ms rtt min/avg/max/mdev = 2.872/4.003/6.687/1.489 ms whilst if I ping one of my websites housed on a server in another country (UK) in quick succession I get this: PING username.me.uk (212.159.8.91) 56(84) bytes of data. 64 bytes from homepages.plus.net (212.159.8.91): icmp_seq=1 ttl=239 time=75.0 ms 64 bytes from homepages.plus.net (212.159.8.91): icmp_seq=2 ttl=239 time=68.2 ms 64 bytes from homepages.plus.net (212.159.8.91): icmp_seq=3 ttl=239 time=70.7 ms 64 bytes from homepages.plus.net (212.159.8.91): icmp_seq=4 ttl=239 time=74.5 ms ^C --- username.me.uk ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7184ms rtt min/avg/max/mdev = 68.280/72.144/75.034/2.791 ms (At the time of typing this both are behaving now with 0% packet loss). I would have expected these results to be the other way around. What's going on? Is it just a flaky wireless card that sometimes drops out, poor drivers, the network card going to sleep or some power management mode, interference from another neighbour's network, or something else that could be responsible? (openSUSE 12.3) Cheers, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 9

[opensuse] intel Haswell graphics (HD Graphics 4600) in openSUSE 12.3
by Roger Oberholtzer 07 Oct '13

07 Oct '13

A couple of months ago I wrote about trying to install oS 12.3 on a PC with intel Haswell graphics. I could not get it to work. X kept wanting to use fbdev instead. I never did sort that out and added an NVidia card instead. I have another of these computers and would really like to see if I can get this to work. I have more than a couple of hours, as was the case last time. The hardware as described by lspci: 00:02.0 VGA compatible controller: Intel Corporation Haswell Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device 2010 Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f7400000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features I have the following installed: kernel-desktop-3.7.10-1.1.1.i686 xorg-x11-7.6_1-178.1.noarch xf86-video-intel-2.99.902-85.2.i586 The X log shows that the intel driver is loaded. But it then immediately uses the fbdev driver: [ 6.456] (==) Matched intel as autoconfigured driver 0 [ 6.456] (==) Matched modesetting as autoconfigured driver 1 [ 6.456] (==) Matched fbdev as autoconfigured driver 2 [ 6.456] (==) Matched vesa as autoconfigured driver 3 [ 6.456] (==) Assigned the driver to the xf86ConfigLayout [ 6.456] (II) LoadModule: "intel" [ 6.456] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 6.477] (II) Module intel: vendor="X.Org Foundation" [ 6.477] compiled for 1.14.3, module version = 2.99.902 [ 6.477] Module class: X.Org Video Driver [ 6.477] ABI class: X.Org Video Driver, version 14.1 [ 6.477] (II) LoadModule: "modesetting" [ 6.477] (WW) Warning, couldn't open module modesetting [ 6.477] (II) UnloadModule: "modesetting" [ 6.477] (II) Unloading modesetting [ 6.477] (EE) Failed to load module "modesetting" (module does not exist, 0) [ 6.477] (II) LoadModule: "fbdev" [ 6.477] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 6.477] (II) Module fbdev: vendor="X.Org Foundation" [ 6.477] compiled for 1.14.2, module version = 0.4.3 [ 6.477] Module class: X.Org Video Driver [ 6.477] ABI class: X.Org Video Driver, version 14.1 [ 6.477] (II) LoadModule: "vesa" [ 6.477] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 6.477] (II) Module vesa: vendor="X.Org Foundation" [ 6.477] compiled for 1.14.2, module version = 2.3.2 [ 6.477] Module class: X.Org Video Driver [ 6.477] ABI class: X.Org Video Driver, version 14.1 [ 6.477] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics, HD Graphics 2000, HD Graphics 3000, HD Graphics 2500, HD Graphics 4000, HD Graphics P4000, HD Graphics 4600, HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100, HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200 [ 6.478] (II) FBDEV: driver for framebuffer: fbdev [ 6.478] (II) VESA: driver for VESA chipsets: vesa [ 6.478] (++) using VT number 7 [ 6.479] (II) Loading sub module "fbdevhw" [ 6.479] (II) LoadModule: "fbdevhw" [ 6.479] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 6.479] (II) Module fbdevhw: vendor="X.Org Foundation" [ 6.479] compiled for 1.14.2, module version = 0.0.2 [ 6.479] ABI class: X.Org Video Driver, version 14.1 [ 6.479] (**) FBDEV(0): claimed PCI slot 0@0:2:0 [ 6.479] (II) FBDEV(0): using default device [ 6.479] (WW) Falling back to old probe method for vesa [ 6.480] (II) FBDEV(0): Creating default Display subsection in Screen section "Default Screen Section" for depth/fbbpp 16/16 It cotninues to configure the FBDEV driver. The hardware is http://ark.intel.com/products/75122/, which states that it is HD Graphics 4600, which the driver lists as being supported. I looked at https://01.org/linuxgraphics/downloads to see if there was something newer. Nope. Seems the version in X11:XOrg is the latest. I wonder about the modeset module error. Which RPM should that have come from? I am guessing this is why the intel driver fails to load... -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 14

Re: [opensuse] A novice's perspective: .deb and .rpm
by AP 06 Oct '13

06 Oct '13

On Sun, Oct 6, 2013 at 6:35 PM, Carlos E. R. <robin.listas(a)telefonica.net> wrote: > Because as I said, YOU does the equivalent of "zypper patch", not "zypper > up". If you had tried "zypper patch" you would have it did not list those > 128 MB you saw with "zypper up". Yes, I get it. Thanks. -- Life and death. At some point we're gonna leave this world. Do I know when? Absolutely not. --- Terrell Owens Just I dislike pain, so all other beings dislike pain. Live and let live. --- Mahavir Bhagwan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] A novice's perspective: .deb and .rpm
by AP 06 Oct '13

06 Oct '13

On Sat, Oct 5, 2013 at 7:30 PM, Carlos E. R. <robin.listas(a)telefonica.net> wrote: >>> YOU shows only patches, while "zypper up" shows also newer RPM versions >>> in configured repositories. >> On Sat, Oct 5, 2013 at 6:20 PM, Carlos E. R. <> wrote: >>> YOU does the equivalent of "zypper patch". To do the equivalent of >>> "zypper >>> up" in YaST package manager (qt version) you right-click on the list of >>> packages, and select all tin this list update if newer. But that list was not coming in the YOU when I clicked 'online update' and as soon as I finished that, I run 'zypper up' which updates (~126 MBs)! >> YOU probably means Yast. > YOU is acronym for YaST Online Update. Oh I see. -- Life and death. At some point we're gonna leave this world. Do I know when? Absolutely not. --- Terrell Owens Just I dislike pain, so all other beings dislike pain. Live and let live. --- Mahavir Bhagwan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

Re: [opensuse] A novice's perspective: .deb and .rpm
by AP 06 Oct '13

06 Oct '13

On Sat, Oct 5, 2013 at 11:29 PM, Greg Freemyer <greg.freemyer(a)gmail.com> wrote: > OpenSUSE releases security patches for the supported life of the > distribution. > There is a formal security team that looks for the need for these patches > and reviews them once a package maintainer submits a proposed patch. The > security team will deny any proposed updates that do not have an associated > bugzilla entry they are resolving or a publicly known security > vulnerability. > These patches are only available to end-users from the openSUSE updates > repository. > The zypper command "zypper patch" looks for those security patches and only > those security patches. YOU does the same. > Normal RPM updates are also extremely common in the various openSUSE > repositories other than the updates repository. They are often just version > updates and may have nothing to do with security issues or bug fixes. > "zypper up" will look through all of the configured repositories for any > available RPM updates regardless. > I am not sure if zypper up also gets all patches or not. I use "zypper > patch" when I want to ensure I have all security updates / bug fixes > installed on a box. > I use "zypper up" much more sparingly and almost always to update specific > packages only. ie. "zypper up sleuthkit" will install the latest version > of sleuthkit from the currently active repository for sleuthkit. "zypper > dup --from security" will look only in the security repo to see if there is > a newer version of any of my installed packages available. If there is, it > will install it regardless of what the current repository for the package > is. > Thus there are at least 4 variations of zypper I use to update packages in > the course of a year. > zypper patch (hopefully every couple weeks) > zypper up <package> (to install a new version of a specific <package> if > in my already configured repo) > zypper dup -- from <repository> (to get the latest version of all packages > in that repository) > zypper dup (done rarely, but needed to move from one full release to the > next. ie. once every 8 months) > You will note, I rarely if ever invoke "zypper up". If I do invoke it, I am > looking to get the list of what updates are available overall for my system. > I typically then cancel out of the update and update the specific packages I > want updated via one of the above methods. Thanks for a clear & explicit reply. In fact, whatever, be the case, I would use both now 'zypper up' as well as 'zypper patch' or from yast. But I knew this which I wanted to know. Regards. -- Life and death. At some point we're gonna leave this world. Do I know when? Absolutely not. --- Terrell Owens Just I dislike pain, so all other beings dislike pain. Live and let live. --- Mahavir Bhagwan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0