December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 932162] New: Context menu "Paste" does not work in Thunar
by bugzilla_noreply＠novell.com 12 Nov '17

12 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=932162 Bug ID: 932162 Summary: Context menu "Paste" does not work in Thunar Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: whoknows2012(a)myopera.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Paste option in Thunar file manager is greyed out & does not work. I can not press it. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 958880] New: Two service files still missing - question on the reason for this ...
by bugzilla_noreply＠novell.com 07 Nov '17

07 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=958880 Bug ID: 958880 Summary: Two service files still missing - question on the reason for this ... Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dieter.jurzitza(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In /var/log/messages I find two error messages that IMHO should not exist. This refers to: Dec 13 10:00:01 djunix systemd[1]: Cannot add dependency job for unit xdm.service, ignoring: Unit xdm.service failed to load: No such file or directory. Dec 13 10:00:01 djunix systemd[1]: Cannot add dependency job for unit syslog.service, ignoring: Unit syslog.service failed to load: No such file or directory. IMHO I think that the reference to xdm - service ought to refer to display-manager.service, because within the latter there is a statement saying: Alias=xdm.service The second one is found within several files, klogd.service is referring to this, and in the syslog.socket file it shows that there should exist a link from /etc/systemd/system/syslog.service to /usr/lib/systemd/system/syslog-ng.service So, should I setup bug reports for both syslog-ng and xdm? Thank you for looking into this, take care Dieter Jurzitza -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 929117] New: VUL-0: accountsservice: Possible memory leak
by bugzilla_noreply＠novell.com 07 Nov '17

07 Nov '17

http://bugzilla.suse.com/show_bug.cgi?id=929117 Bug ID: 929117 Summary: VUL-0: accountsservice: Possible memory leak Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: vpereira(a)novell.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Compiling the the package with Address Sanitizer, we get the following error: 250s] ==5294==ERROR: LeakSanitizer: detected memory leaks [ 250s] [ 250s] Direct leak of 40 byte(s) in 3 object(s) allocated from: [ 250s] #0 0x7fec26e10c4a in malloc (/usr/lib64/libasan.so.2+0x96c4a) [ 250s] #1 0x7fec26046480 in g_malloc (/usr/lib64/libglib-2.0.so.0+0x51480) [ 250s] [ 250s] Direct leak of 32 byte(s) in 2 object(s) allocated from: [ 250s] #0 0x7fec26e10f6a in realloc (/usr/lib64/libasan.so.2+0x96f6a) [ 250s] #1 0x7fec2604651e in g_realloc (/usr/lib64/libglib-2.0.so.0+0x5151e) [ 250s] [ 250s] Indirect leak of 213 byte(s) in 2 object(s) allocated from: [ 250s] #0 0x7fec26e10c4a in malloc (/usr/lib64/libasan.so.2+0x96c4a) [ 250s] #1 0x7fec26046480 in g_malloc (/usr/lib64/libglib-2.0.so.0+0x51480) [ 250s] [ 250s] SUMMARY: AddressSanitizer: 285 byte(s) leaked in 7 allocation(s). -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 875373] New: systemd-tmpfiles-setup.service runs before all filesystems are mounted
by bugzilla_noreply＠novell.com 06 Nov '17

06 Nov '17

https://bugzilla.novell.com/show_bug.cgi?id=875373 https://bugzilla.novell.com/show_bug.cgi?id=875373#c0 Summary: systemd-tmpfiles-setup.service runs before all filesystems are mounted Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: Other OS/Version: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: systemd-maintainers(a)suse.de ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- - Factory, last updated yesterday - last known-working version: Factory from 2014-04-13 systemd-tmpfiles-setup.service runs before all filesystems are mounted. (Probably) since the change that makes /var/run a symlink to /run, the tmpdirs below /var/run can't be created on my system. Note: I have an encrypted /home partition, and /var is a symlink to /home/sys-var. This means /var becomes available after /home has been mounted. systemd-tmpfiles-setup.service should wait until _all_ filesystems are mounted. # systemctl status systemd-tmpfiles-setup.service systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-setup.service; static) Active: active (exited) since So 2014-04-27 11:44:45 CEST; 29min ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 1491 ExecStart=/usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=0/SUCCESS) Main PID: 1491 (code=exited, status=0/SUCCESS) CGroup: /system.slice/systemd-tmpfiles-setup.service Apr 27 11:44:45 geeko systemd-tmpfiles[1491]: Failed to create directory /var/run/samba: No such file or directory Apr 27 11:44:45 geeko systemd-tmpfiles[1491]: Failed to create directory /var/run/svnserve: No such file or directory [... and some more /var/run/* directories with similar error message ...] Apr 27 11:44:45 geeko systemd[1]: Started Create Volatile Files and Directories. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 12

[Bug 946356] New: Package 1-Click-Installer doesn't work anymore
by bugzilla_noreply＠novell.com 03 Nov '17

03 Nov '17

http://bugzilla.opensuse.org/show_bug.cgi?id=946356 Bug ID: 946356 Summary: Package 1-Click-Installer doesn't work anymore Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Software Portal Assignee: benji(a)opensuse.org Reporter: mschnitzer(a)suse.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 647829 --> http://bugzilla.opensuse.org/attachment.cgi?id=647829&action=edit Bug Hi, I tried to do a 1-Click-Installation: https://software.opensuse.org/ymp/systemsmanagement:machinery/openSUSE_13.2… As you can see, there is an issue with the API. Please have also a look into my attachment. Regards, Manu -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 954147] New: mozilla-kde4-integration should be ported to KF5
by bugzilla_noreply＠novell.com 30 Oct '17

30 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=954147 Bug ID: 954147 Summary: mozilla-kde4-integration should be ported to KF5 Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: pastas4(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Now that Plasma 5 is the default desktop, it would be good to remove dependencies on kdebase4-runtime. One of the last items on the list preventing that from happening is the fact that Firefox still uses KDE4 for desktop integration. So kmozillahelper needs to be ported to KF5. There is already a port of it done for Arch, as seen here: https://github.com/cruiseliu/kmozillahelper-frameworks But it might be a bit stale at this point. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 927831] New: ping gives wrong warning: kernel is not very fresh, upgrade is recommended
by bugzilla_noreply＠novell.com 30 Oct '17

30 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=927831 Bug ID: 927831 Summary: ping gives wrong warning: kernel is not very fresh, upgrade is recommended Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: armv7 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: Network Assignee: ms(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: hare(a)suse.com, tiwai(a)suse.com Found By: Development Blocker: --- Created attachment 631630 --> http://bugzilla.opensuse.org/attachment.cgi?id=631630&action=edit tcpdump On a recent armv7 Factory with linux-4.0.0, I found this random warning: rcwicked restart ; ping -n 192.168.12.1 PING 192.168.12.1 (192.168.12.1) 56(84) bytes of data. WARNING: kernel is not very fresh, upgrade is recommended. >From 192.168.12.2: icmp_seq=2 Destination Host Unreachable >From 192.168.12.2: icmp_seq=3 Destination Host Unreachable 64 bytes from 192.168.12.1: icmp_seq=4 ttl=64 time=1051 ms 64 bytes from 192.168.12.1: icmp_seq=5 ttl=64 time=45.9 ms 64 bytes from 192.168.12.1: icmp_seq=6 ttl=64 time=63.1 ms 64 bytes from 192.168.12.1: icmp_seq=7 ttl=64 time=87.7 ms 64 bytes from 192.168.12.1: icmp_seq=8 ttl=64 time=519 ms 64 bytes from 192.168.12.1: icmp_seq=9 ttl=64 time=34.0 ms According to http://nslug.ns.ca/pipermail/nslug/2014-January/026056.html the warning seems to be about a problem with kernels <2.4.9 So either the warning should just be dropped, rephrased, or we find out why it is occurring randomly even today. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 938387] New: pt_BR keyboard not set correctly in nwe installs
by bugzilla_noreply＠novell.com 26 Oct '17

26 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=938387 Bug ID: 938387 Summary: pt_BR keyboard not set correctly in nwe installs Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: elchevive68(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hi, After installing Tumbleweed my keyboard is not set right. If I go to YaST -> Select the system keyboard, the keyoard selected is the right one "Portugues (Brazil) but the result is not the correct. If I click in another, then select Portugues (Brazil) again, it starts working correctly. Unfortunately this change only remains for this session, if I do a reboot, the wrong keyboard layout is used Which addition info you need to debug this problem? Regard, Luiz -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 927677] New: some usb sticks require root password to mount
by bugzilla_noreply＠novell.com 26 Oct '17

26 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=927677 Bug ID: 927677 Summary: some usb sticks require root password to mount 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: F.Schuette(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 631497 --> http://bugzilla.opensuse.org/attachment.cgi?id=631497&action=edit system with problematic usb stick (sdb, id-scsi) I tried two similar usb sticks, one of them mounted as usual, the other one required me to input root password to mount. I attached udisksctl output to the report. -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 900376] New: Upgrading OpenSuse 13.1 using zipper or yast2 triggers network failures
by bugzilla_noreply＠novell.com 22 Oct '17

22 Oct '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900376 Bug ID: 900376 Summary: Upgrading OpenSuse 13.1 using zipper or yast2 triggers network failures Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: foolishewe(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 609401 --> http://bugzilla.opensuse.org/attachment.cgi?id=609401&action=edit Tar bundle of command output and log files from the initial bug report I have a Toshiba P855-S200 laptop that ran OpenSuse 12.1 (or was it 12.2) without incident. I recently brought it back on line and updated the to OpenSuse 13.1 from installation media (DVD) which went very smoothly. However when I do the post install upgrade of packages, the networking fails (both wireless and wired). The wireless adapter sees routers and connects using Network Manager (on KDE). It appears that DNS is working (e.g. nslookup cnn.com has the expected results), however actually retrieving data fails (e.g. wget cnn.com fails). This causes the online update to fail to download packages about 2/3 of the way through (always at the same point). Rebooting does not fix this. I am able to reproduce this, since I can use the install media to "Update" which actually reverts the updated packages. I've tried this several times and it appears to fail at the same point. What information is needed to track this down? How can I successfully upgrade my packages so that I get bug fixes and (more importantly) security updates? Please find attached a file name failedupgrade.tgz, which contains the following information tar tzvf ./failedupgrade.tgz drwxr-xr-x dummy/users 0 2014-10-08 21:25 ./failedupgradeinfo/ -rw-r--r-- dummy/users 524 2014-10-08 07:51 ./failedupgradeinfo/iwconfig.log -rw-r--r-- dummy/users 995 2014-10-08 21:23 ./failedupgradeinfo/wget.log -rw-r--r-- dummy/users 1367 2014-10-08 08:01 ./failedupgradeinfo/resolv.conf -rw-r--r-- dummy/users 126 2014-10-08 07:52 ./failedupgradeinfo/uname.log -rw-r--r-- dummy/users 61382 2014-10-08 08:07 ./failedupgradeinfo/dmesg.log -rw-r--r-- dummy/users 143734 2014-10-08 08:00 ./failedupgradeinfo/rpmqa.log -rw-r--r-- dummy/users 930961 2014-10-08 08:22 ./failedupgradeinfo/wpa_supplicant.log iwconfig.log - the output of iwconfig wget.log - the output of nslookup cnn.com and wget cnn.com after the failed on-line update resolv.conf - the actual resolv.conf file (I changed it to use faster dns servers). uname.log - the output of uname -a after the failed on-line update demesg.log - the output of dmesg after the failed on-line update rpmqa.log - the output of rpm -q -a after the failed on-line update wpa_supplicant.log - the wpa_supplicant.log file zypperlr.log - the output of zypper lr after the failed on-line upgrade attempt. Steps to reproduce: 1) Install 13.1 from media and upgrade the existing installation. 2) If necessary, remove the apper package, it interferes with zypper and yast2's software management. 3) Do Yast on-line update. Observe loss of network connectivity. -- You are receiving this mail because: You are on the CC list for the bug.

1 3