Quantcast
Channel: openSUSE Forums
Viewing all 40713 articles
Browse latest View live

LEAP 15.1 https://en.opensuse.org/SDB:BTRFS

$
0
0
My situation seems to be out of sync with that page. Brother-in-law's bad SSD originally used btrfs for 42.2, and eventually reached 15.1 in November. First I used ddrescue to clone from the bad SSD to another disk. Then I connected the other disk to a working 15.1 as sdb.

These are the last steps from there I've taken:
Quote:

btrfs rescue zero-log /dev/sda1

Then try to mount the device normally. If it works, stop going.
What exactly is
Quote:

mount normally
with btrfs?
Code:

# mount /dev/sdb2 /mnt
has apparently mounted / just fine, but /mnt/home is void, empty. It should contain what needs to be rescued. Is /home that lost, or is some further mounting step(s) required?

[security-announce] openSUSE-SU-2020:0180-1: moderate: Security update for upx

$
0
0
openSUSE Security Update: Security update for upx ______________________________________________________________________________ Announcement ID: openSUSE-SU-2020:0180-1 Rating: moderate References: #1094138 #1141777 #1143839 #1159833 #1159920 Cross-Refer...

More...

[security-announce] openSUSE-SU-2020:0179-1: moderate: Security update for ucl

$
0
0
openSUSE Security Update: Security update for ucl ______________________________________________________________________________ Announcement ID: openSUSE-SU-2020:0179-1 Rating: moderate References: #1094138 Cross-References: CVE-2018-11243 Affected Produ...

More...

LEAP 15.1 Just installed Leap 15.1. Has the ability to specify the domain name been removed from YaST?

$
0
0
Hi folks. I went through the installation process for Leap 15.1 and noticed that the box to specify the domain name was missing. I had a bit of a look around other menus just in case I'd misremembered this particular part of the installation process, but I couldn't find it anywhere. I gave up on trying to have all of of the man network settings configured by the time of the first boot, and decided to just set the domain name after installation was complete. When I logged in for the first time, I jumped straight in to YaST to set the domain name, but just like in the installation process, there was only a hostname field spanning the entire length of the screen, when I'd normally expect to see a domain name field next to it on the right. Is this supposed to be this way? I decided to stop trying to get the rest of the box configured just in case I'd somehow managed to foul something up in the installation process. I changed very little during the installation process; all I did was add the CLI tools pattern for installation in case it had something useful in it, and then told the installer not to write bootcode to the MBR. I prefer to just boot from a root partition or not have a bootloader at all, but when I told it not to write to the MBR, the installer warned that the system might not be able to boot, so I changed it back, and now whenever the system boots, I always have to keep whacking the F8 key, so I can bring up a disk selection menu where I can choose which HDD to boot from. If I don't bring up that menu and allow the system to boot as it is configured, then it just sits there on a blank screen with a blinking cursor until I switch it off. All I want to do is let the host know which domain it belongs to, so that any software I install and use will find the correct domain name information? I get the impression the behind the scenes part of the networking settings have been undergoing some gradual change in the past few versions of openSUSE, so how should I go about making sure that I can set the domain name, without having to worry about if I've missed updating any relevant configuration files?

LEAP 15.1 USB not recognised.

$
0
0
Hi,

I decided that it was time for a laptop that doesn't burn my lap. So I got myself Lenovo Ideapad 310-15isk. So far, so excellent. But it doesn't seem to want to recognise any some devices I connect to it. For instance I have Inkbook Prime that I like to put some more books onto, the previous laptop recognised it right away, but the Lenovo doesn't want to connect even though the device itself says that it is connected.

TUMBLEWEED Tumbleweed (and Leap) maintenance best practices

$
0
0
I'd like to know how veteran openSUSErs maintain their systems. Are there utilities that you run regularly, directories that you regularly trim?

The reason I ask:

If I hadn't stumbled across this recent thread:

http://lists.opensuse.org/opensuse-f.../msg00025.html

I might never have heard of .rpmnew files, or been motivated to investigate the related utilities rpmconfigcheck.
(I just found one mention of rcrpmconfigcheck at: https://en.opensuse.org/SDB:Offline_upgrade , but can't remember seeing it mentioned elsewhere in openSUSE documentation.)

Imagine my surprise when I finally ran rpmconfigcheck a few days ago! I had over twenty .rpmnew and .rpmsave files accumulated since I adopted Tumbleweed more than two years ago. I'll be sure to run it from now on, but would like to know if there are other maintenance steps I should be taking that I'm not taking now.

I always use zypper dup with Tumbleweed, never zypper up.

I installed tmpwatch, run it regularly, and also prune logs with journalctl --vacuum-time.

For me, that's about it.

LEAP 15.1 convert multiple jpg to pdf issue

$
0
0
Hi, I have a problem ImageMgick. I'ld like to convert a lot of jpeg files to one pdf file but when I run convert *.jpg output.pdf I get a blank pdf file with white pages but pdf file size is 35MB.
When I import this pdf file to Gimp I can see correct pdf pages but Okular or Adobe Acrobat can not show pages only blakn white pages...

I used ImageMagick under 42.3 and it worked perfectly. What maybe wrong? Can someone help me?

Thanks for help.

TUMBLEWEED Need help with this rsyslog.conf line

$
0
0
info: rsyslogd: version 8.39.0

:msg, contains_i, "qt" -/var/log/qt.log

The contains_i causes an error but if i switch it to just contains it is ok.
Isnt contains_i supported? or is my formatting wrong somehow?

Tumbleweed + modem USB 3G Huawei K3772 ← nie działa pod Gnome.

$
0
0
Witam,

mam stary modem USB 3G Huawei K3772.

Testowałem na nim kilkanaście najpopularniejszych dystrybucji Linuksa i nigdy nie miałem żadnych problemów ani ze sterownikiem do tego modelu, ani z jego konfiguracją i połączeniem z Siecią.

Pobrałem najnowszą openSUSE Tumbleweed i w środowisku KDE Plasma nie mam żadnych problemów z moim modemem, natomiast środowisko Gnome go „nie widzi” – a chcę właśnie używać openSUSE z Gnome. :-(
–––

Objawy są takie →

1. Po uruchomieniu systemu wkładam modem do gniazda USB i czekam chwilę, aż modem zostanie wykryty przez system – tak jak we wszystkich testowanych przeze mnie Linuksach.

2. Klikam opcję: Ustawienia sieci komórkowej. W oknie: Sieć jest wyświetlony numer IMEI mojego modemu.

3. Przełączam suwak na opcję połączenia komórkowego, po czym na belce: Sieć – wybieram: Dodaj nowe połączenie, ale połączenia skonfigurować nie sposób, bo w kolejnych oknach nie ma żadnych opcji dla mojego modemu, kreator go „nie widzi”.

Czy ma ktoś pomysł jak mogę się połączyć z Siecią przy pomocy mojego modemu?

Dziękuję za pomoc!
Wolf

Highlights of YaST Development Sprint 93

$
0
0
Lately, the YaST team has been quite busy fixing bugs and finishing some features for the upcoming (open)SUSE releases. Although we did quite some things, in this report we will have a closer look at just a few topics: A feature to search for packages across all SLE modules has arrived to YaST. Improved support […]

More...

LEAP 15.1 Very slow booting then none

$
0
0
As soon as the problems started I checked my HD connectors and memory card connectors. That made no difference. I ran Spinrite on my HD and it reported no problems.I rebooted. When "Started Local Service" appeared on the screen it turned black. After a long wait a prompt returned and told me that there was a problem on /dev/sda5 which is my /home partition and suggested I log in as root to view journalctl -xb. It showed errors on that parttition and suggested I should fsck it which I did, allowing all the corrections. I can reboot now, but all my favorite applications are missing from my panel and a number of mystery files have appeared in my home directory. Their names are...

asyncio...concurrent.futures...socket...threading...time...urllib.parse...webrowser

I can replace the missing items on my panle, but I am concerned that something else needs to be looked at. Any suggestions would be appreciated

LEAP 15.1 SAMSUNG S4 data transfer

$
0
0
I'm trying to get some files off an old Samsung S4 phone

I connect the USB cable,

a Device Notifier popup says, 3 actions for this device,

I select Open with file manager

When I try to open a directory, I get the following error

Code:

  Could not enter folder /SCH-i545/phone/DCIM/Camera
Why does this happen?

Is there a more robust directory on the phone for file transfers?

Thank you

LEAP 15.1 PHP not read cookies

$
0
0
Hello,
I installed web server LAMP using pattern. But I have got problem: although cookies are set, php can not read it (After "Cookie is " is emptiness). What else I have to do to fix it. This is program code:

Code:

echo('<html>
<head>
<script>
document.cookie = "username=John Doe; expires=Thu, 18 Dec 2013 12:00:00 UTC";');
echo('</script>
</head>');
<body>
$a1=$_COOKIE["username"];
$a=122;
ECHO('Cookie is: '. $a1);

LEAP 15.1 Can't enable opengl on the qemu machine

$
0
0
In a windows 10 guest managed by virt-manager (qemu), a program requires opengl to run.

I however can't get over this error:


Some google results shows I need to change the option from
Code:

--graphics spice,port=20001,listen=127.0.0.1
to
Code:

--graphics spice,listen=127.0.0.1
Wonder how I should do it with the GUI? I switched the "port", "tls" on and off in the GUI but they just give me different errors.

LEAP 15.1 Installer cannot see “missing” physical volumes

$
0
0
My current setup successfully underwent each upgrade from Leap 42.1 to Leap 15.0, but is suddenly rejected by Leap 15.1 installer:

Quote:

The volume group /dev/vgSamLnx is incomplete because some physical volumes are missing.
Incomplete volume groups are not visible in the Partitioner and will be deleted at the
final step, when all the changes are performed in the system.
The strange thing is that those volumes not only appear as fully operational in Leap 15.0, but also seem to be fine when checked manually from within Leap 15.1 installation environment. When googling by the error message text, the only result returned is the installer source code, so I suppose I may have hit some corner case. But my disk configuration is pretty simple:

  1. a pair of identical HDDs,
  2. several identical partitions on both HDDs, with GPT partition table and protective MBR,
  3. several RAID 1 arrays on top of some partitions, implemented by Linux MDRAID,
  4. single LVM volume group on top of those RAID arrays acting as physical volumes,
  5. several LVM logical volumes inside that LVM volume group.

(There is also another HDD in the system containing Windows and an older openSUSE installation on top of its own LVM group, which is not related to the current setup.)

I made several attempts running the offline installer and booting back to the online system, and so on, but could not get the difference in their view of disk devices. The only error I could spot in the installer logs is that GPT backup partition table was missing somehow, but fixing that had no effect on the installer. That else can be done to debug the issue?

This is what I see in the installer environment:
Code:

# cat /proc/mdstat

Personalities : [raid1]
md126 : active raid1 sdc4[1] sdb4[0]
      310383424 blocks super 1.0 [2/2] [UU]
      bitmap: 0/3 pages [0KB], 65536KB chunk

md127 : active raid1 sdc2[1] sdb2[0]
      486536000 blocks super 1.0 [2/2] [UU]
      bitmap: 0/4 pages [0KB], 65536KB chunk

unused devices: <none>

Code:

# lsblk

NAME                              MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
loop0                                7:0    0  70.5M  1 loop  /parts/mp_0000
loop1                                7:1    0  13.8M  1 loop  /parts/mp_0001
loop2                                7:2    0  49.4M  1 loop  /mounts/mp_0000
loop3                                7:3    0  76.3M  1 loop  /mounts/mp_0001
loop4                                7:4    0  4.1M  1 loop  /mounts/mp_0002
loop5                                7:5    0  1.8M  1 loop  /mounts/mp_0003
loop6                                7:6    0    64K  1 loop  /mounts/mp_0004
sda                                  8:0    0 465.8G  0 disk 
├─sda1                              8:1    0  39.2M  0 part 
├─sda2                              8:2    0  752M  0 part 
├─sda3                              8:3    0  240G  0 part 
├─sda4                              8:4    0    1K  0 part 
├─sda5                              8:5    0  510M  0 part 
├─sda6                              8:6    0    4G  0 part 
└─sda7                              8:7    0  216G  0 part 
  ├─vgMain-lvHome                  253:20  0    32G  0 lvm 
  ├─vgMain-lvRoot                  253:21  0    32G  0 lvm 
  ├─vgMain-lvTestDebian7          253:22  0    16G  0 lvm 
  ├─vgMain-lvTestSuse12            253:23  0    16G  0 lvm 
  ├─vgMain-lvTestCentOS6          253:24  0    16G  0 lvm 
  ├─vgMain-lvTestFedora19g        253:25  0    16G  0 lvm 
  ├─vgMain-lvTestFedora19x        253:26  0    16G  0 lvm 
  ├─vgMain-lvTestFreeBSD9          253:27  0    16G  0 lvm 
  ├─vgMain-lvTestWindows51        253:28  0    4G  0 lvm 
  ├─vgMain-lvTestSuse12text        253:29  0    4G  0 lvm 
  ├─vgMain-lvTestFreeBSD10        253:30  0    8G  0 lvm 
  ├─vgMain-lvTestNetBSD6          253:31  0    8G  0 lvm 
  └─vgMain-lvTestNetBSD7sparc      253:32  0    4G  0 lvm 
sdb                                  8:16  0  1.8T  0 disk 
├─sdb1                              8:17  0  1003M  0 part 
├─sdb2                              8:18  0  464G  0 part 
│ └─md127                            9:127  0  464G  0 raid1
│  ├─vgSamLnx-lvSysRoot          253:0    0    64G  0 lvm 
│  ├─vgSamLnx-lvSysSwap          253:1    0    8G  0 lvm 
│  ├─vgSamLnx-lvSysTemp          253:2    0    32G  0 lvm 
│  ├─vgSamLnx-lvSysWork          253:3    0    32G  0 lvm 
│  ├─vgSamLnx-lvUsrHome          253:4    0  320G  0 lvm 
│  ├─vgSamLnx-lvSysHost          253:5    0    4G  0 lvm 
│  ├─vgSamLnx-lvDevUbuntu        253:6    0    16G  0 lvm 
│  ├─vgSamLnx-lvTmpBench          253:7    0    2G  0 lvm 
│  ├─vgSamLnx-lvDevMCBC          253:8    0    8G  0 lvm 
│  ├─vgSamLnx-lvDevMCBCv3007sparc 253:9    0    8G  0 lvm 
│  ├─vgSamLnx-lvDevMCBCv3002sparc 253:10  0    76G  0 lvm 
│  ├─vgSamLnx-lvDevMCBCv5007x64  253:11  0    16G  0 lvm 
│  ├─vgSamLnx-lvDevAstraSpecial  253:12  0    16G  0 lvm 
│  └─vgSamLnx-lvDevAstraSEv14    253:13  0    8G  0 lvm 
├─sdb3                              8:19  0    2G  0 part 
└─sdb4                              8:20  0  296G  0 part 
  └─md126                            9:126  0  296G  0 raid1
    ├─vgSamLnx-lvUsrHome          253:4    0  320G  0 lvm 
    ├─vgSamLnx-lvDevScientific64  253:14  0    16G  0 lvm 
    ├─vgSamLnx-lvDevFreeBSD        253:15  0    16G  0 lvm 
    ├─vgSamLnx-lvTestWindows51    253:16  0    4G  0 lvm 
    ├─vgSamLnx-lvTestSambaFS      253:17  0    16G  0 lvm 
    ├─vgSamLnx-lvTestCentOS43      253:18  0    16G  0 lvm 
    └─vgSamLnx-lvTestCentOS49      253:19  0    16G  0 lvm 
sdc                                  8:32  0  1.8T  0 disk 
├─sdc1                              8:33  0  1003M  0 part 
├─sdc2                              8:34  0  464G  0 part 
│ └─md127                            9:127  0  464G  0 raid1
│  ├─vgSamLnx-lvSysRoot          253:0    0    64G  0 lvm 
│  ├─vgSamLnx-lvSysSwap          253:1    0    8G  0 lvm 
│  ├─vgSamLnx-lvSysTemp          253:2    0    32G  0 lvm 
│  ├─vgSamLnx-lvSysWork          253:3    0    32G  0 lvm 
│  ├─vgSamLnx-lvUsrHome          253:4    0  320G  0 lvm 
│  ├─vgSamLnx-lvSysHost          253:5    0    4G  0 lvm 
│  ├─vgSamLnx-lvDevUbuntu        253:6    0    16G  0 lvm 
│  ├─vgSamLnx-lvTmpBench          253:7    0    2G  0 lvm 
│  ├─vgSamLnx-lvDevMCBC          253:8    0    8G  0 lvm 
│  ├─vgSamLnx-lvDevMCBCv3007sparc 253:9    0    8G  0 lvm 
│  ├─vgSamLnx-lvDevMCBCv3002sparc 253:10  0    76G  0 lvm 
│  ├─vgSamLnx-lvDevMCBCv5007x64  253:11  0    16G  0 lvm 
│  ├─vgSamLnx-lvDevAstraSpecial  253:12  0    16G  0 lvm 
│  └─vgSamLnx-lvDevAstraSEv14    253:13  0    8G  0 lvm 
├─sdc3                              8:35  0    2G  0 part 
└─sdc4                              8:36  0  296G  0 part 
  └─md126                            9:126  0  296G  0 raid1
    ├─vgSamLnx-lvUsrHome          253:4    0  320G  0 lvm 
    ├─vgSamLnx-lvDevScientific64  253:14  0    16G  0 lvm 
    ├─vgSamLnx-lvDevFreeBSD        253:15  0    16G  0 lvm 
    ├─vgSamLnx-lvTestWindows51    253:16  0    4G  0 lvm 
    ├─vgSamLnx-lvTestSambaFS      253:17  0    16G  0 lvm 
    ├─vgSamLnx-lvTestCentOS43      253:18  0    16G  0 lvm 
    └─vgSamLnx-lvTestCentOS49      253:19  0    16G  0 lvm 
sdd                                  8:48  1  28.9G  0 disk 
├─sdd1                              8:49  1  3.8M  0 part 
├─sdd2                              8:50  1  3.8G  0 part 
└─sdd3                              8:51  1    16G  0 part  /mnt
sr0                                11:0    1  1024M  0 rom

Code:

# pvs

  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  PV        VG      Fmt  Attr PSize  PFree
  /dev/md126 vgSamLnx lvm2 a--  463.99g    0
  /dev/md127 vgSamLnx lvm2 a--  296.00g 65.99g
  /dev/sda7  vgMain  lvm2 a--  216.00g 28.00g

# pvscan

  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  PV /dev/md126  VG vgSamLnx        lvm2 [463.99 GiB / 0    free]
  PV /dev/md127  VG vgSamLnx        lvm2 [296.00 GiB / 65.99 GiB free]
  PV /dev/sda7    VG vgMain          lvm2 [216.00 GiB / 28.00 GiB free]
  Total: 3 [975.99 GiB] / in use: 3 [975.99 GiB] / in no VG: 0 [0  ]

# pvdisplay

  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  --- Physical volume ---
  PV Name              /dev/md126
  VG Name              vgSamLnx
  PV Size              464.00 GiB / not usable 4.81 MiB
  Allocatable          yes (but full)
  PE Size              4.00 MiB
  Total PE              118782
  Free PE              0
  Allocated PE          118782
  PV UUID              L592qS-LLAM-T2cX-fhp6-t0FN-whnr-a9OkWW
 
  --- Physical volume ---
  PV Name              /dev/md127
  VG Name              vgSamLnx
  PV Size              296.00 GiB / not usable 4.81 MiB
  Allocatable          yes
  PE Size              4.00 MiB
  Total PE              75776
  Free PE              16894
  Allocated PE          58882
  PV UUID              8E55fv-0Vh6-ealr-6GVR-8k3m-YmUk-zBM8T1
 
  --- Physical volume ---
  PV Name              /dev/sda7
  VG Name              vgMain
  PV Size              216.00 GiB / not usable 4.00 MiB
  Allocatable          yes
  PE Size              4.00 MiB
  Total PE              55295
  Free PE              7168
  Allocated PE          48127
  PV UUID              KhNxP6-HBOg-eICK-rmlj-pNWH-r6Gr-3a3xuQ

See also:
  • libstorage-ng device graph (XML)
  • other logs archived:
    • /var/log contents (except irrelevant)
    • libstorage-ng log and device graph excerpts from /var/log/YaST2/y2log
    • lvm logs (pvs, pvscan, pvdisplay, vgs, vgscan, vgdisplay, lvs, lvscan, lvdisplay, vgchange, lvchange)
    • blkid, dmesg, mount

PS. After reading recent discussions here on the forum I became aware that the system could be upgraded online. Although I had never tried such method, I would definitely prefer that. However I am afraid that under current circumstances I may end up with non-functioning system if Leap 15.1 treats the disks in the same way as its offline installer does.

LEAP 15.2 NM not scanning known hidden WiFi networks anymore?

$
0
0
Testing Leap 15.2 alpha with Gnome. My WiFi router has a hidden SSID, I need to go to WiFi settings, "Connect to hidden network", select (known, configured) SSID, <root password>, then connection is established.
With Leap 15.1 all that is automatic at boot ("connect automatically" and "available to all users" are checked), but apparently 15.2 doesn't scan for known hidden networks.
Configs are the same apparently, unless I missed something (checked with nmtui).
Has something important changed in that area? Any hints to check configs I possibly missed?
Can the kernel driver (ath9k) have a role or is the 5.3 kernel doing something odd in that area?

TUMBLEWEED Firmware pruning.

$
0
0
I'm looking to trim out the unnecessary kernel firmware on my Tumbleweed install, but the YaST package manager throws an error that doing so will break the kernel-firmware-all package. Would it be safer to break the kernel-firmware-all package, or remove it?

LEAP 15.2 Installer kernel panic

$
0
0
I have one of these https://www.dell.com/en-uk/shop/lapt...15-9570-laptop and I've never been able to get 15.0 to run properly or 15.1 to even install, but with support for 42.3 being a distant memory I decided to give the alpha of 15.2 a try.

I had to add acpi=off as a kernel parameter or else the installer would simply shut down, with this parameter I now get the following error message:



I have a working 42.3 setup and am more than happy to run whatever diagnostics, I'd even be willing to apply patches to patch and compile the kernel if any of the devs have some idea of what might fix this. I've dabbled in minor kernel fixed in the past but unfortunately other commitments mean I don't have time to fix this myself.

LEAP 15.1 Blackscreen after boot with a horizontal line

[security-announce] openSUSE-SU-2020:0187-1: moderate: Security update for ceph

$
0
0
openSUSE Security Update: Security update for ceph ______________________________________________________________________________ Announcement ID: openSUSE-SU-2020:0187-1 Rating: moderate References: #1161074 #1161312 Cross-References: CVE-2020-1699 CVE-2...

More...
Viewing all 40713 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>