August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 900092] New: PackageKit/zypp has trouble with multiple versions in a repo (libzypp can handle it)
by bugzilla_noreply＠novell.com 18 Jan '17

18 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900092 Bug ID: 900092 Summary: PackageKit/zypp has trouble with multiple versions in a repo (libzypp can handle it) Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The VideoLAN repository (and likely also packman) certainly have a strange setup for that, nevertheless it's existing in the real world. there is a package * vlc-2.1.5-2.1 (whith subpackages built, I only focus on one of them:) * libvlc5-2.1.5-2-1 (version 100% in sync to vlc) and there is * vlc-beta-3.0.0-2.1 * libvlc5-3.0.0-2.1 (it is supposed to be ABI compatible, but we prefer not to gamble) vlc has a Requires: libvlc5 = %{version-%{release} and so does vlc-beta vlc and vlc beta have a Conflicts: against each other. while the user has vlc-2.1.5-1.1 installed, a zypper up happily upgrades vlc inside the 'stable branch', and keeps libvlc5 in line to what it should be if the user has vlc-beta installe, the same works using zypper Using PackageKit though (pkcon for one): if the user has vlc installed, pkcon update fails with Fatal error: vlc-noX-2.1.5-111.1.x86_64 requires libvlc5 = 2.1.5-111.1, but this requirement cannot be provided which is quite annoying: if the user happens to have this constellation (and probably others!) then pkcon update simply aborts -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 913178] New: radiotray does not start
by bugzilla_noreply＠novell.com 18 Jan '17

18 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=913178 Bug ID: 913178 Summary: radiotray does not start Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mpapis(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 619615 --> http://bugzilla.opensuse.org/attachment.cgi?id=619615&action=edit zypper lr -u -U I can not find the fix for https://bugzilla.opensuse.org/show_bug.cgi?id=904322 in my 13.2 installation ```bash # sudo zypper if radiotray ... Version: 0.7.3-6.1.5 ... # sudo zypper up radiotray ... No update candidate for 'radiotray-0.7.3-6.1.5.noarch'. The highest available version is already installed. Resolving package dependencies... Nothing to do. ``` `zypper lr -u -U` attached -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 920671] New: MATE: keyboard shortcuts missing in mate-keybinding-properties
by bugzilla_noreply＠novell.com 18 Jan '17

18 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=920671 Bug ID: 920671 Summary: MATE: keyboard shortcuts missing in mate-keybinding-properties Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: ulrich.hobelmann+suse(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- In the MATE keyboard shortcuts dialog, there are only a few entries for the music bindings and for general applications, no Window Manager actions, nothing else. So it seems like something is very broken. In addition, shortcuts involving META key (windows key) don't work. I tried setting Win-E to caja, but nothing happens. Not sure if this is just a related problem. (also see maybe related bug 792682 - X11:MATE: Terminal keyboard shortcut doesn't work) -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 926865] New: zypper never removes packages that it says it is going to remove
by bugzilla_noreply＠novell.com 18 Jan '17

18 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=926865 Bug ID: 926865 Summary: zypper never removes packages that it says it is going to remove 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: illumilore(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0 Build Identifier: When I run sudo zypper -v ref;sudo zypper -v dup to upgrade my system, zypper says it is going to remove packages: The following 2 applications are going to be REMOVED: digiKam Showfoto but, they are never removed: zypper se digi S | Name | Summary | Type --+----------------------------+------------------------------------------------+------------ i | digikam | A KDE Photo Manager | package | engauge-digitizer | Ditigize old graphs into numbers again | package | rmedigicontrol | GUI control tool for RME Digi32 and RME Digi-> | package | PlotDigitizer | Ditigize scanned plots of functional data | package i | digikam-doc | Documentation of Digikam | package | digikam-lang | Languages for package digikam | package | engauge-digitizer-doc | Documentation for Engauge Digitizer | package | perl-Algorithm-CheckDigits | Perl extension to generate and test check di-> | package | texlive-digiconfigs | Writing "configurations" | package | texlive-digiconfigs-doc | Documentation for texlive-digiconfigs | package i | digiKam | | application Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 899510] New: Fix support using multiple base URLs for a reop
by bugzilla_noreply＠novell.com 16 Jan '17

16 Jan '17

http://bugzilla.suse.com/show_bug.cgi?id=899510 Bug ID: 899510 Summary: Fix support using multiple base URLs for a reop Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: ma(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- [http://lists.opensuse.org/zypp-devel/2014-10/msg00000.html] - Support defining multiple base URLs directly within a .reop file. - This is currently possible by using a 'mirrorlist=' instead of 'baseurl', but unfortunately using a local file as mirrorlist is broken (code strips 'path' component from URL which is illegal for 'file:' schema) - Fix zypper to non-interactively switch baseurls upon error. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 906005] New: Forward Email Template Error
by bugzilla_noreply＠novell.com 14 Jan '17

14 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=906005 Bug ID: 906005 Summary: Forward Email Template Error Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: guoyunhebrave(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is the default head of forward mail in KMail: -------------------------------------------------- Subject: XXXXX Date: Tuesday 18 November 2014 From: 10:24:08 To: A <someonea(a)example.com> To: B <someoneb(a)example.com> ---------------------------------------------------- I checked the template of forward email, the head part is: ------------------------------------------------------- Subject: %OFULLSUBJECT Date: %ODATE From: %OTIMELONG To: %OFROMADDR %OADDRESSEESADDR ------------------------------------------------------- I think this is a template error. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 916741] New: Too many "disable" links on the top of Chinese wiki
by bugzilla_noreply＠novell.com 14 Jan '17

14 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=916741 Bug ID: 916741 Summary: Too many "disable" links on the top of Chinese wiki Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Wiki Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: guoyunhebrave(a)gmail.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- See this picture: http://imgur.com/0VubKU5 These links are language variants. The first "disable" should be Chinese, the second "Simple Chinese", the third "Traditional Chinese"... It is better to show exact names of these tabs. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 904300] New: Weird question marks on bootsplash
by bugzilla_noreply＠novell.com 10 Jan '17

10 Jan '17

http://bugzilla.novell.com/show_bug.cgi?id=904300 Bug ID: 904300 Summary: Weird question marks on bootsplash 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: tonyj(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 612712 --> http://bugzilla.novell.com/attachment.cgi?id=612712&action=edit screenshot I'm not sure what catagory to file this under. Updated main workstation from 13.1 to 13.2 using zypper dup. Now on bootsplash I see 3 green question marks before X starts. Screenshot attached, $ cat /proc/cmdline root=/dev/disk/by-id/ata-ST31000528AS_6VP43XF3-part2 resume=/dev/disk/by-id/ata-ST31000528AS_6VP43XF3-part1 splash=silent quiet -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 924346] New: Plasma5 install to openSUSE Tw, Hung during installation of kpackage
by bugzilla_noreply＠novell.com 10 Jan '17

10 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=924346 Bug ID: 924346 Summary: Plasma5 install to openSUSE Tw, Hung during installation of kpackage Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pat(a)indy.rr.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- attempting to install plasma5 to my openSUSE Tw system hung during install of kpackage. Was not recoverable. After an extended period, reformatted and reinstalled Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 935956] New: BTRFS balance failure.
by bugzilla_noreply＠novell.com 10 Jan '17

10 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=935956 Bug ID: 935956 Summary: BTRFS balance failure. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: moby(a)pcsn.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- BTRFS / (one big file system but that is irrelevant) running on top of md raid 5 consisting of 4 SATA disks. Balance was performed after doing massive I/O (almost filling up the filesystem etc and then doing some deletions etc). Balance keeps on failing while reporting some insanities described below. All snapshots were deleted so snapshots should not have anything to do with the issue at hand. Below was seen on kernel 3.16.7-21-default. The machine is now at kernel 4.0.5-5.g80f6bcd-default and btrfs-progs v4.1+20150622. These two items were upgraded to see if the issue could be resolved. Everything else on the machine (including creating/deleting files) on the machine works fine, only btrfs balance is acting insane. btrfs balance keeps failing with messages like below in the log (below is a grep 'btrfs' from journalctl -b so the messages are not necessarily contiguous): [44950.935025] BTRFS info (device md1): relocating block group 3706217037824 flags 1 [44954.665729] BTRFS info (device md1): relocating block group 3705143296000 flags 1 [44966.689827] BTRFS info (device md1): found 156 extents [44985.223754] BTRFS: bdev /dev/md1 errs: wr 9911, rd 0, flush 0, corrupt 0, gen 0 [44985.224033] BTRFS: bdev /dev/md1 errs: wr 9912, rd 0, flush 0, corrupt 0, gen 0 [44985.224285] BTRFS: bdev /dev/md1 errs: wr 9913, rd 0, flush 0, corrupt 0, gen 0 Running a btrfs scrub / showed no errors or issues at all. Then I started doing btrfs balance start -dusage=X and noticed that it would succeed up to X = 73 and fail after that. Then I started deleting subsets of data. I did btrfs balance start -dusage=X after each delete and noticed that as more and more data was deleted, X kept increasing before the balance would error out. Deleting more data allowed value of X to go upto 98 before btrfs balance would error out. Also, today, I started a btrfs balance -dusage=95. At the same time I was running btrfs balance status -v to watch the status. The percentage left started at 100% and kept decreasing ... it eventually went below zero and still kept on decreasing. It was at -111% when I canceled the balance. Output of the balance is below: Wed Jun 24 12:29:12 CDT 2015 Balance on '/' is running 306 out of about 145 chunks balanced (312 considered), -111% left Dumping filters: flags 0x1, state 0x1, force is off DATA (flags 0x2): balancing, usage=95 -- You are receiving this mail because: You are on the CC list for the bug.

1 3