February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1026658] New: The go package shouldn't set $GOBIN to $HOME/go/bin
by bugzilla_noreply＠novell.com 25 Mar '19

25 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1026658 Bug ID: 1026658 Summary: The go package shouldn't set $GOBIN to $HOME/go/bin Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kgronlund(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the go package, the file /etc/profile.d/go.sh is installed. In that file is the following: export GOROOT=/usr/$libdir/go export GOBIN=/usr/bin export GOPATH=/usr/share/go/contrib if [ `id -u` != 0 ]; then export GOPATH=$HOME/go:/usr/share/go/contrib export GOBIN=$HOME/go/bin fi Setting GOBIN to $HOME/go/bin is extremely confusing. I would set GOPATH to point to my go directory, and then expect binaries to be installed to $GOPATH/bin. Instead, the binaries end up in another, arbitrary location. Regarding GOBIN, the upstream documenation says as following: "This should only be set if you really know what you're doing... The default should be fine." The correct thing here ought to be to set GOPATH, but to unset GOBIN so it isn't set at all, thereby defaulting to GOPATH/bin. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1017291] New: multiple users, last user not preselected if you start/restart your pc
by bugzilla_noreply＠novell.com 14 Mar '19

14 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1017291 Bug ID: 1017291 Summary: multiple users, last user not preselected if you start/restart your pc Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- it is the first in alphabetical order which is selected and not the last connected user sddm.conf contents: [Theme] Current=breeze-openSUSE CursorTheme=breeze_cursors [XDisplay] ServerPath=/usr/bin/X SessionCommand=/etc/X11/xdm/Xsession DisplayCommand=/etc/X11/xdm/Xsetup MinimumVT=7 state.conf contents: [Last] # Name of the last logged-in user. This username will be preselected/shown when the login screen shows up User=<my name> -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 903889] New: incorrect routing with bridge interface
by bugzilla_noreply＠novell.com 11 Mar '19

11 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=903889 Bug ID: 903889 Summary: incorrect routing with bridge interface Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: PC OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: comes(a)naic.edu QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have done a fresh installation of 13.2. I use static network parameters (no dhcp) and I selected the KVM Host Server pattern. This makes the installer to automatically select the network configuration: bridged configuration using wicked (which by the way I cannot override anymore during the setup after the first reboot because the "improved" installer decided I don't need to). The problem with this configuration (bridged network and no dhcp) is that the gateway get associated with the ethernet device and not the bridge device. It exists the file /etc/sysconfig/network/ifroute-eth0 which contains default <gateway ip> - eth0 but that's wrong. I can use yast to correct the routing and after that the routing configuration file is: /etc/sysconfig/network/ifroute-br0 containing: default <gateway ip> - br0 If during the installation I select dhcp the bridge has the proper routing. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 925873] New: resume fails after hibernate from Cinnamon, succeeds after hibernate from command line
by bugzilla_noreply＠novell.com 11 Mar '19

11 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=925873 Bug ID: 925873 Summary: resume fails after hibernate from Cinnamon, succeeds after hibernate from command line Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: schuetzm(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 629922 --> http://bugzilla.suse.com/attachment.cgi?id=629922&action=edit screenshot After installing systemd 210-25.16.1 via update, resume after hibernate from the Cinnamon shutdown dialog hangs, while everything works flawlessly when I use "echo -n disk > /sys/power/state". (Previously I had used systemd 210-879.1 from tsaupe repo IIRC, because of another bug which has since been resolved.) In my setup, I have encrypted /home and swap partitions. It correctly asks me for the password (in Plymouth), but then everything stops; there's only the Plymouth splash screen, which doesn't react to <Esc>, <Ctrl+Fn> or <Ctrl+Alt+Del>. I managed to circumvent the splash screen by pressing escape early; see the attached screen shot. The last thing printed is "Starting dracut pre-mount hook...", after that, even the cursor disappears. -- You are receiving this mail because: You are on the CC list for the bug.

1 78

[Bug 900099] New: smartmontools: generate_smartd_opts refers to init script
by bugzilla_noreply＠novell.com 08 Mar '19

08 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=900099 Bug ID: 900099 Summary: smartmontools: generate_smartd_opts refers to init script Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: sbrabec(a)suse.com Reporter: lnussel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- - /usr/lib/smartmontools/generate_smartd_opts refers to an init script that no longer exists - /usr/lib/smartmontools/generate_smartd_opts is never called AFAICS unless one uses YaST to edit /etc/sysconfig/smartmontools. Maybe the service file should call it before launching smartd? - /var/lib/smartmontools/smartd_opts should probably be moved to /run - rcsmartd symlink is missing -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 951749] New: gcin does not installed if selected Traditional Chinese while installation
by bugzilla_noreply＠novell.com 28 Feb '19

28 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=951749 Bug ID: 951749 Summary: gcin does not installed if selected Traditional Chinese while installation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 RC1 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: yast2-maintainers(a)suse.de Reporter: mlin(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- gcin is default input method for Traditional Chinese[1], however selected Traditional Chinese as default in installer but gcin does not installed after installation. I've check the iso, unfortunately gcin is not exists. [1] https://build.opensuse.org/package/view_file/openSUSE:Leap:42.1/gcin/gcin.s… -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 951707] New: zypper search hangs due to text formatting
by bugzilla_noreply＠novell.com 28 Feb '19

28 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=951707 Bug ID: 951707 Summary: zypper search hangs due to text formatting Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ronisbr(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi. I am having a problem with zypper search function in some cases. If I execute, for example: $ zypper search nautilus in a terminal (like mate-terminal) in which 60px <= width <= 86px, then it loops printing empty characters: $ zypper search nautilus Carregando os dados do repositório... Lendo os pacotes instalados... S | Nome | Resumo | Tipo --+--------------------------------------+--------------------------+----------- | Nautilus-Actions Configuration Tool | Configure items to be -> | aplicativo i | brasero-nautilus | Brasero CD/DVD burning-> | pacote | folder-color-nautilus | Change a directory col-> | pacote | gnome-shell-search-provider-nautilus | File Manager for the G-> | pacote i | libnautilus-extension1 | File Manager for the G-> | pacote | libnautilus-extension1-32bit | File Manager for the G-> | pacote i | nautilus | File Manager for the G-> | pacote | nautilus-actions | Nautilus extension to -> | pacote | nautilus-actions-devel | Nautilus extension to -> | pacote | nautilus-actions-lang | Languages for package -> | pacote i | nautilus-deja-dup | Déjà Dup Plugin for Na .... (eternal loop) I can see the same behavior using LANG=C: $ LANG=C zypper search nautilus Loading repository data... Reading installed packages... S | Name | Summary | Type --+--------------------------------------+-------------------------+------------ | Nautilus-Actions Configuration Tool | Configure items to be-> | application i | brasero-nautilus | Brasero CD/DVD burnin-> | package | folder-color-nautilus | Change a directory co-> | package | gnome-shell-search-provider-nautilus | File Manager for the -> | package i | libnautilus-extension1 | File Manager for the -> | package | libnautilus-extension1-32bit | File Manager for the -> | package i | nautilus | File Manager for the -> | package | nautilus-actions | Nautilus extension to-> | package | nautilus-actions-devel | Nautilus extension to-> | package | nautilus-actions-lang | Languages for package-> | package i | nautilus-deja-dup | Déjà Dup Plugin for N .... (eternal loop) However, for LANG=C the width interval in which the problem can be seen is different. Notice that if I resize the terminal such that the width is outside the aforementioned interval, then everything works. Thus, I think it is related with a text formatting function or something. Below, I am appending additional information about my system. ➜ ~ cat /etc/os-release NAME=openSUSE VERSION="Tumbleweed" VERSION_ID="20151017" PRETTY_NAME="openSUSE Tumbleweed (20151017) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:20151017" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" ➜ ~ zypper --version zypper 1.12.16 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 975966] New: hang in FITRIM ioctl()
by bugzilla_noreply＠novell.com 26 Feb '19

26 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=975966 Bug ID: 975966 Summary: hang in FITRIM ioctl() Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: sbrabec(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While installing util-linux-systemd by online update tool, rpm hangs. Linux oct 4.5.0-3-default #1 SMP PREEMPT Mon Mar 28 07:27:57 UTC 2016 (8cf0ce6) x86_64 x86_64 x86_64 GNU/Linux Analyzing the problem, I found that the hang is caused by: ├─packagekitd─┬─btrfs-defrag-pl │ ├─rpm───sh───sh───systemctl The hanging systemctl is: /usr/bin/systemctl try-restart fstrim.service fstrim.timer And the hanging command is: ps axl shows: 4 0 5777 1 20 0 22252 2556 blkdev Ds ? 0:11 /usr/sbin/fstrim -a # ls -al /proc/5777/fd/ total 0 dr-x------ 2 root root 0 Apr 18 14:40 . dr-xr-xr-x 9 root root 0 Apr 18 13:59 .. lr-x------ 1 root root 64 Apr 18 14:40 0 -> /dev/null lrwx------ 1 root root 64 Apr 18 14:40 1 -> socket:[101297] lrwx------ 1 root root 64 Apr 18 14:40 2 -> socket:[101297] lr-x------ 1 root root 64 Apr 18 14:40 3 -> /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdb lr-x------ 1 root root 64 Apr 18 14:40 4 -> /boot/grub2/i386-pc /dev/sdb is this device: [ 2.274041] scsi 2:0:0:0: Direct-Access ATA KINGSTON SV300S3 BBF0 PQ: 0 ANSI: 5 [ 2.275099] sd 0:0:0:0: [sda] Attached SCSI disk [ 2.304981] sd 2:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB) [ 2.305504] sd 2:0:0:0: [sdb] Write Protect is off [ 2.305511] sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 2.305806] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 2.306629] sdb: sdb1 sdb2 [ 2.307319] sd 2:0:0:0: [sdb] Attached SCSI disk There are no error or timeout messages in dmesg, only this one: [ 1110.897517] perf interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 oct:~ # cat /proc/5777/stack [<ffffffff8136f950>] blkdev_issue_discard+0x1e0/0x230 [<ffffffffa03d7161>] btrfs_issue_discard+0xe1/0x180 [btrfs] [<ffffffffa03ddc4c>] btrfs_discard_extent+0x9c/0x100 [btrfs] [<ffffffffa043dfc4>] do_trimming+0xa4/0x170 [btrfs] [<ffffffffa043fbac>] btrfs_trim_block_group+0x4bc/0x540 [btrfs] [<ffffffffa03e8e6a>] btrfs_trim_fs+0x10a/0x3f0 [btrfs] [<ffffffffa042b41e>] btrfs_ioctl_fitrim+0x11e/0x170 [btrfs] [<ffffffffa0431d0f>] btrfs_ioctl+0x4cf/0x1e30 [btrfs] [<ffffffff8121dd02>] do_vfs_ioctl+0x92/0x580 [<ffffffff8121e269>] SyS_ioctl+0x79/0x90 [<ffffffff816cc072>] entry_SYSCALL_64_fastpath+0x16/0x71 [<ffffffffffffffff>] 0xffffffffffffffff gdb disassemble (with a debuginfo from release 3.1) indicates that it waits in wait_for_completion_io(). 0xffffffff8136f93f <+463>: lock decl 0x20(%rsp) 0xffffffff8136f944 <+468>: je 0xffffffff8136f950 <blkdev_issue_discard+480> 0xffffffff8136f946 <+470>: lea 0x30(%rsp),%rdi 0xffffffff8136f94b <+475>: callq 0xffffffff816c8630 <wait_for_completion_io> -> 0xffffffff8136f950 <+480>: mov 0x24(%rsp),%eax 0xffffffff8136f954 <+484>: test %eax,%eax 0xffffffff8136f956 <+486>: cmove %ebx,%eax 0xffffffff8136f959 <+489>: lea -0x28(%rbp),%rsp Strace hangs for long minutes, then it does few commands and hangs again: strace: Process 5777 attached close(4) = 0 stat("/boot/grub2/x86_64-efi", {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 stat("/boot/grub2", {st_mode=S_IFDIR|0755, st_size=168, ...}) = 0 stat("/dev/sdb1", {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 17), ...}) = 0 open("/sys/dev/block/8:17", O_RDONLY|O_CLOEXEC) = 4 newfstatat(4, "partition", {st_mode=S_IFREG|0444, st_size=4096, ...}, 0) = 0 readlink("/sys/dev/block/8:17", "../../devices/pci0000:00/0000:00"..., 4095) = 83 open("/sys/block/sdb/dev", O_RDONLY|O_CLOEXEC) = 5 fstat(5, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f8fc2425000 read(5, "8:16\n", 4096) = 5 close(5) = 0 munmap(0x7f8fc2425000, 4096) = 0 close(4) = 0 open("/sys/dev/block/8:17", O_RDONLY|O_CLOEXEC) = 4 openat(4, "queue/discard_granularity", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) openat(3, "queue/discard_granularity", O_RDONLY|O_CLOEXEC) = 5 fcntl(5, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE) fstat(5, {st_mode=S_IFREG|0444, st_size=4096, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f8fc2425000 read(5, "512\n", 4096) = 4 close(5) = 0 munmap(0x7f8fc2425000, 4096) = 0 close(4) = 0 open("/boot/grub2/x86_64-efi", O_RDONLY) = 4 fstat(4, {st_mode=S_IFDIR|0755, st_size=0, ...}) = 0 ioctl(4, FITRIM, {start=0, len=0xffffffffffffffff, minlen=0} -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 936768] New: Language packages obey the wrong option for Recommended packages
by bugzilla_noreply＠novell.com 25 Feb '19

25 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=936768 Bug ID: 936768 Summary: Language packages obey the wrong option for Recommended packages Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: mvidner(a)suse.com QA Contact: qa-bugs(a)suse.de CC: gs(a)suse.com Found By: --- Blocker: --- I have a system where only the English Language is installed (/var/lib/zypp/RequestedLocales has en_US). If I run the YaST package manager (qt or ncurses), enable Ignore Recommended Packages for Already Installed Packages (which will be the default, see https://bugzilla.opensuse.org/show_bug.cgi?id=902394 ) and add another language (eg Czech), no additional packages are selected. This is contrary to my expectation, since I consider Czech to be a new "package" so its recommended dependencies such as desktop-translations and bundle-lang-common-cs should be selected for installation. It works if I disable the Ignore...Already option. I wondered why the solver would behave so and I noticed that most language dependencies were expressed as conjunctions, eg bundle-lang-common-cs: Supplements: bash & namespace:language(cs) (it also has this, and I wonder why) Provides: locale (bash:cs) so in one way I see that bash is "already installed" so there's a pretext for not installing the bundle. OTOH the language is new, so the user expectation is IMHO clear. desktop-translations is even more interesting, since there is no conjunction, OTOH there is a disjunction. (Why not simply list a Supplements for each?) Supplements: namespace:language(af) | ... | namespace:language(cs) | ... I noticed all this when converting the Ignore...Already option to a one-time command similar to `zypper inr`. Gabi then argued that it was necessary for it to remain an option so that language rpms can be installed. I think that they should obey the onlyRequires option, which is newly exposed in the UIs as "Install Recommended Packages" (boo#900853). Overall, I consider this a part of a bigger cleanup of Recommends, https://fate.suse.com/318099 -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1012781] New: pam-kwallet,fails to unlock kwallet by login process
by bugzilla_noreply＠novell.com 22 Feb '19

22 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1012781 Bug ID: 1012781 Summary: pam-kwallet,fails to unlock kwallet by login process Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- i install pam-kwallet packet then i restart opensuse then i open a kde session then kwallet asks for me the password to open kwallet! i open /ect/pam.d/sddm file contents are: #%PAM-1.0 auth include common-auth account include common-account password include common-password session required pam_loginuid.so session include common-session it must be: #%PAM-1.0 auth include common-auth -auth optional pam_kwallet5.so account include common-account password include common-password session required pam_loginuid.so session include common-session -session optional pam_kwallet5.so auto_start after adding the statements -auth optional pam_kwallet5.so -session optional pam_kwallet5.so auto_start there is no more pb note: you can't use this feature if you choose to use gpg key to crypt wallet file you can only use this feature if: - you choose "blowfish" method when creating wallet file - the name of the wallet must be kwallet i use this tuto https://wiki.archlinux.org/index.php/KDE_Wallet -- You are receiving this mail because: You are on the CC list for the bug.

1 13