August 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1051647] New: Cinnamon Desktop
by bugzilla_noreply＠novell.com 17 Jul '19

17 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1051647 Bug ID: 1051647 Summary: Cinnamon Desktop Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: lnussel(a)suse.com Reporter: thstclair(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I installed cinnamon DE. Everything seems to work EXCEPT even though I have window backgrounds and wallpapers installed and available, the system cannot use them. This same box has Plasma 5 and GNOME installed and both have no issues. In Cinnamon icons, applications, resolution work perfectly...only on a light gray desktop. I removed Cinnamon and then replaced it hoping that something would be replaced that might have gotten "buggared", but the same thing continued. When Cinnamon opens and closes, I can see a GNOME wallpaper for a very brief split second. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1008493] New: YaST2 tftp-server configuration shows error for reading the log
by bugzilla_noreply＠novell.com 17 Jul '19

17 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1008493 Bug ID: 1008493 Summary: YaST2 tftp-server configuration shows error for reading the log Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: zluo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 700651 --> http://bugzilla.suse.com/attachment.cgi?id=700651&action=edit yast logs (tftp server) run test case yas2_tftp. I got error for error occurred while reading the log. compare with sles 12 sp2 gmc (SLE-12-SP2-Server-DVD-ppc64le-Build2192) there is no error message pops up even at stage of initial configuration before any logs created. Please check logs and screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1031133] New: update-alternatives: spurious warnings with --remove
by bugzilla_noreply＠novell.com 16 Jul '19

16 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1031133 Bug ID: 1031133 Summary: update-alternatives: spurious warnings with --remove Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: tchvatal(a)suse.com Reporter: jmatejek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- when using update-alternatives in %postun, the following warnings are emitted: update-alternatives: warning: alternative /usr/bin/virtualenv-3.6 (part of link group virtualenv) doesn't exist; removing from list of alternatives update-alternatives: warning: /etc/alternatives/virtualenv is dangling; it will be updated with best choice update-alternatives: using /usr/bin/virtualenv-2.7 to provide /usr/bin/virtualenv (virtualenv) in auto mode This is because update-alternatives first checks if it must modify the auto-selection, and discovers that key files are missing so it auto-corrects the alternative choice. ...which is what I was telling it to do in the first place. Unfortunately, using "--quiet" also silences the one non-warning, "using <something> to provide <something> in auto mode" which seems like a thing we should keep. update-alternative should not warn about broken files when instructed to remove them. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1009432] New: openSUSE:Tools/osc-plugin-install: Bug
by bugzilla_noreply＠novell.com 16 Jul '19

16 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1009432 Bug ID: 1009432 Summary: openSUSE:Tools/osc-plugin-install: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: ro(a)suse.com Reporter: a.malik.michael(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Hi, every time i try to use "osc in" i get the following error Traceback (most recent call last): File "/usr/bin/osc", line 41, in <module> r = babysitter.run(osccli) File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 343, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 366, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 500, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1230, in _dispatch_cmd return handler(argv[0], opts, *args) File "/var/lib/osc-plugins/osc-install.py", line 305, in do_install arch_words = self._read_system_name(etc_S_r, opts) File "/var/lib/osc-plugins/osc-install.py", line 559, in _read_system_name text = open(file).read() IOError: [Errno 2] No such file or directory: '/etc/SuSE-release' when i checked /etc/, i could not find SUSE-release. I am not sure if this would help but, i could fine os-release which contained the following NAME="openSUSE Tumbleweed" # VERSION="20161108" ID=opensuse ID_LIKE="suse" VERSION_ID="20161108" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20161108" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1056745] New: Please move /usr/share/OpenCV/OpenCVModules*.cmake to opencv-devel
by bugzilla_noreply＠novell.com 14 Jul '19

14 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1056745 Bug ID: 1056745 Summary: Please move /usr/share/OpenCV/OpenCVModules*.cmake to opencv-devel Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: cfeck(a)kde.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please move development files "/usr/share/OpenCV/OpenCVModules*.cmake" from package "opencv" to package "opencv-devel". -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1050856] New: Selecting by full lines in konsole 17.04.2 (KDE 5.32.0, Qt 5.6.2) "forgets" the last end-of-line
by bugzilla_noreply＠novell.com 12 Jul '19

12 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1050856 Bug ID: 1050856 Summary: Selecting by full lines in konsole 17.04.2 (KDE 5.32.0, Qt 5.6.2) "forgets" the last end-of-line Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This happens in openSUSE 42.3, it used not to happen in 42.2. Case 1: 1. Triple-click a line in a konsole tab. 2. Middle-click in another tab at a bash prompt Expected result (42.2 and earlier): The line is pasted including the end-of-line, and starts executing. Actual result (42.3): The line is pasted but the cursor hangs at the end of it and the user must hit Enter to start execution. Case 2: 1. Select several full lines in a konsole tab by dragging the mouse vertically along the left margin. 2. Middle-click in another tab at a bash prompt Expected result (42.2 and earlier): All lines are executed in sequence. Actual result (42.3): All lines except the last one execute in sequence. Then the cursor hangs at the end of the last line and the user has to hit Enter to complete the operation. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 954556] New: After upgrading from 13.2 to Leap 42.1, Mercurial chokes on files locally deleted and ignored, but changed on the remote
by bugzilla_noreply＠novell.com 12 Jul '19

12 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=954556 Bug ID: 954556 Summary: After upgrading from 13.2 to Leap 42.1, Mercurial chokes on files locally deleted and ignored, but changed on the remote Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 URL: http://users.skynet.be/antoine.mechelynck/vim/vim-tony mec.bundle.bz2 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm not sure if this bug is in the correct Component. It concerns a difference between the Mercurial versions for openSUSE 13.2 and openSUSE Leap 42.1. I'll describe below the problems I had (in a Mercurial repository with local changes) after upgrading to Leap 42.1, and how I solved them (probably not ideally), in the hope that something can be found to make life easier to anyone else running into the same (or a sufficiently similar) problem. FWIW I've uploaded at http://users.skynet.be/antoine.mechelynck/vim/vim-tonymec.bundle.bz2 a full bundle of my local Vim repository, including a clone of the Mercurial mirror at https://bitbucket.org/vim-mirror/vim with local changes. The bundle is 8.8 MiB for a repository occupying about 151 MiB so I didn't attach it to this bug. The tip before I upgraded to Leap 42.1 was the merge commit about 30 changesets from the present tip. The earlier changesets (0 to 7225) are probably not as interesting but I didn't know how else to let you look at it from my point of view. It might be possible to inspect the bundle without unpacking it, by declaring it as a "repository" by means of the -R argument to Mercurial. This past weekend I upgraded to Leap 42.1 and a few hours ago "hg in" displayed 27 new changesets. I tried to "fetch" them but instead of saying "remote changed runtime/doc/tags which local deleted" and asking me if I wanted to download the changes or keep deleted, Mercurial errored out with the new changesets applied, the "old" merge still current, no new merge done, and a message saying that it could not proceed because of a locally ignored file changed on the remote (the deleted file in question). I goofed around some, updated (not easily) to 0 and back to tip, including a couple of manual merges for which Mercurial invoked vimdiff as my preferred merge tool, and finally added one monstrous changeset by hg addremove followed by hg commit. Those "added" files are IIUC files ignored by my locally modified .hgignore on the other unnamed branch. After that I could finally merge my local changes with the monstrous changeset I had just added on top of Bram's official tip. After that I notice that "hg diff" on the locally deleted file does not give the same output as it used to before the upgrade to Leap. Previously it showed a diff between the remote version of the file and /dev/null, which was longish and looked messy, but, well, I used to think that was the way of things, at least with that version of Mercurial. Now it just says: diff --git a/runtime/doc/tags b/runtime/doc/tags deleted file mode 100644 which I find much neater even if it is not visually reversible. I am practically certain that what I did was not the "ideal" thing to do, but it is the best I could find to work around this change of behaviour and still get a working directory tree with which I could compile Bram's version with my local changes (which consist of one feature added and one disabled in src/feature.h, plus .hgignore lines for runtime/doc/tags which is regenerated by "make install" anyway, and for some directories and files not present on the remote, e.g. "shadow" directories allowing me to compile a Huge and a Tiny build in parallel from the same source with different config settings passed as environment variables). I hope Mercurial won't choke again the next time new changesets are added at the remote and I try to apply them. -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1055516] New: images in desktop previes on mpuse-over are too small
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1055516 Bug ID: 1055516 Summary: images in desktop previes on mpuse-over are too small Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Minor Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: linux(a)daniel-bauer.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 738198 --> http://bugzilla.opensuse.org/attachment.cgi?id=738198&action=edit hovering an image-icon shows a preview with only a very small preview Until 13.2 when hovering over an icon (for example of an image) on the desktop a preview appeared that showed that image in a quite larger size. Since 42.1 this preview image is even smaller than the icon itself and thus isn't really helpful... I can't change the size of the preview image shown when mouse is over the icon - or I haven't found where... using folder view for desktop "show preview" for the corresponding filetypes is set in dolphin the preview works as desired -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1025735] New: Update QCA to 2.1.3
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1025735 Bug ID: 1025735 Summary: Update QCA to 2.1.3 Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: drizt(a)land.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- QCA 2.1.3 was realised. Please update it. New version here http://download.kde.org/stable/qca/2.1.3/src/qca-2.1.3.tar.xz . -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1021271] New: KDE session are not visible in who / last output
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1021271 Bug ID: 1021271 Summary: KDE session are not visible in who / last output Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Holm.Schubert(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Users running a KDE (Plasma 5) session are not visible in the output of "who" or "last". Same problem for IceWM session on a KDE installed system. Only open consoles (within the KDE session or in a text terminal) are listed by who/last. In a GNOME installation of 42.2 the error doesn't occur. The error was observed for the first time in Leap 42.1, persists in 42.2 and Tumbleweed but does not exist in openSUSE 13.2. Steps to reproduce: Login user A to a KDE session but do not open any console in this session. Switch to text terminal and login as user B. Check for running session of user A (who / last A). -- You are receiving this mail because: You are on the CC list for the bug.

1 8