June 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 902779] New: [Factory] Long boot delay "a start job is running for..."
by bugzilla_noreply＠novell.com 27 Aug '19

27 Aug '19

http://bugzilla.opensuse.org/show_bug.cgi?id=902779 Bug ID: 902779 Summary: [Factory] Long boot delay "a start job is running for..." Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: sb56637(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, My openSUSE Factory installation was taking at least 60 seconds longer than normal to boot. The delay always occurred on every boot. The delay occured before initializing the display manager with a message: "A start job is running for", and it would alternate between four different services: X display manager, Avahi, NetworkManager, and Modem Manager. I tried disabling the Modem Manager service, but it still kept hanging on Avahi and NetworkManager. I eventually tried disabling and later re-enabling the NetworkManager services, and it now boots quickly without hanging. I don't really know why this happened or what I did to fix it. Please let me know what additional information you need to prevent this bug from happening. Thanks a lot! -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 934055] New: yast2-network: Do not use .site as default TLD
by bugzilla_noreply＠novell.com 23 Aug '19

23 Aug '19

http://bugzilla.suse.com/show_bug.cgi?id=934055 Bug ID: 934055 Summary: yast2-network: Do not use .site as default TLD Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: mfilka(a)suse.com Reporter: lnussel(a)suse.com QA Contact: jsrain(a)suse.com Blocks: 923990 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #923990 +++ YaST should not set any domain at all anymore in /etc/hostname. The domain name entry box (eg https://openqa.opensuse.org/tests/67247/modules/yast2_lan/steps/3) should be removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 840485] New: Firefox 24.0/17.0.9esr security release
by bugzilla_noreply＠novell.com 16 Aug '19

16 Aug '19

https://bugzilla.novell.com/show_bug.cgi?id=840485 https://bugzilla.novell.com/show_bug.cgi?id=840485#c0 Summary: Firefox 24.0/17.0.9esr security release Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa-bugs(a)suse.de CC: security-team(a)suse.de Found By: --- Blocker: --- 2013-09-17 is the announced release date for the following Mozilla applications which contain security fixes (as always) (https://wiki.mozilla.org/Releases) Firefox 24.0 Firefox 17.0.9esr xulrunner 17.0.9esr Seamonkey 2.21 Thunderbird 17.0.9esr Thunderbird 24.0 (minimum NSPR 4.10 and NSS 3.15.1 requirements I think already met with last update round) I'll provide updates for openSUSE distributions as usual with one exception where I'd like to get some feedback: Thunderbird will do a big version update to 24.0 for non-esr versions. Since esr and non esr versions were 99,9% identical in the 17.0 series we have the choice to update to 17.0.9esr or 24.0 for released distributions which will only move the major upgrade around 12 weeks so I'm in favor to follow the big update now already. -- 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 46

[Bug 935339] New: gpgme fails to cleanly uninstall: install-info: No such file or directory for /usr/share/info/gpgme.info.gz
by bugzilla_noreply＠novell.com 05 Jul '19

05 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=935339 Bug ID: 935339 Summary: gpgme fails to cleanly uninstall: install-info: No such file or directory for /usr/share/info/gpgme.info.gz Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: gp(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Uninstalling gpgme, I get the following: 1 package to remove. After the operation, 355.3 KiB will be freed. Continue? [y/n/? shows all options] (y): y (1/1) Removing gpgme-1.5.5-1.1 .........................................................................................................[done] Additional rpm output: install-info: No such file or directory for /usr/share/info/gpgme.info.gz warning: %postun(gpgme-1.5.5-1.1.x86_64) scriptlet failed, exit status 1 # rpm -ql gpgme | grep info /usr/share/info/gpgme.info-1.gz /usr/share/info/gpgme.info-2.gz /usr/share/info/gpgme.info.gz This looks similar to bug #929415 and may have the same fix? -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 925561] New: NetworkManager should provide a way to designate any connection as a mobile data connection
by bugzilla_noreply＠novell.com 03 Jul '19

03 Jul '19

http://bugzilla.opensuse.org/show_bug.cgi?id=925561 Bug ID: 925561 Summary: NetworkManager should provide a way to designate any connection as a mobile data connection Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jrhodes(a)redpointsoftware.com.au QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Apper has an option in it's settings regarding when to automatically download and install updates. Under this setting there's an option "unless I am on a mobile data connection", which supposedly ensures that Apper doesn't download software updates while connected to a mobile (or metered) network. Unfortunately there doesn't appear to be any way in NetworkManager to designate a wireless or wired connection as being a mobile connection, i.e. a connection provided by a wireless hotspot or USB tethered phone. I'd really like to set Apper to automatically download and install updates as soon as they are available (I'm running on openSUSE Tumbleweed, which I believe is just Factory now?), but I can't do this because I occasionally have my laptop connected to my 4G hotspot, and I don't want to risk having packages download over 4G. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 914681] New: jing doesn't find Saxon extension
by bugzilla_noreply＠novell.com 01 Jul '19

01 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=914681 Bug ID: 914681 Summary: jing doesn't find Saxon extension Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: thomas.schraitle(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The jing package is used to validate an XML document with a RNG schema. When installing the jing package and running it without any options, you get: ----------------- $ rpm -q jing jing-20091111-19.1.3.noarch $ jing /usr/bin/build-classpath: error: Could not find saxon Java extension for this JVM /usr/bin/build-classpath: error: Some specified jars were not found Jing version 20091111 usage: java com.thaiopensource.relaxng.util.Driver [-i] [-c] [-s] [-t] [-C catalogFile] [-e encoding] RNGFile XMLFile... RELAX NG is a schema language for XML See http://relaxng.org/ for more information. ----------------- After investigating it, the respective line is this: BASE_JARS="jing xerces-j2 xml-commons-apis saxon xml-commons-resolver" This contains the list of all JAR files which is used by jing. However, "saxon" doesn't exist anymore, it should be "saxon6". The above line should be therefor look like this: BASE_JARS="jing xerces-j2 xml-commons-apis saxon6 xml-commons-resolver" -- You are receiving this mail because: You are on the CC list for the bug.

1 19

[Bug 901115] New: yast2-network overwrites postfix configuration
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=901115 Bug ID: 901115 Summary: yast2-network overwrites postfix configuration Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lmb(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 609975 --> http://bugzilla.suse.com/attachment.cgi?id=609975&action=edit main.cf mods caused by yast2 network After a long time, I used yast2-network to change something in the network configuration of my node. (Changed the hostname.) As a result, my postfix main.cf was overwritten and rendered unusuable. I'm entirely unsure why some of these parameters were touched - why would it unset mailbox_command, set mailbox_transport, unset relay_host? Yes, this was facilitated by me having /etc/sysconfig/mail:MAIL_CREATE_CONFIG="yes" at the default value, but normally, none of the yast2 tools overwrites manually modified files silently, without even creating an in-place backup. Especially since this looks as if unrelated parameters were touched. I might have understood rewriting "mydestination", but the other parameters make absolutely no sense. I'm attaching the diff here - I restored the main.cf from backup. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 917431] New: less doesn't open gzip'ed files unpacked anymore
by bugzilla_noreply＠novell.com 13 May '19

13 May '19

http://bugzilla.suse.com/show_bug.cgi?id=917431 Bug ID: 917431 Summary: less doesn't open gzip'ed files unpacked anymore 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: stephan.barth(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When looking at files with less like ARCHIVES.gz it unpacked it automatically. Since the recent updates this doesn't work anymore: # less ARCHIVES.gz "ARCHIVES.gz" may be a binary file. See it anyway? I tried to debug it a bit with "set -x", which didn't help. The funny thing is, that after issuing "set +x" less works as expected again. Using su (to root for example) breaks it again. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 606436] New: Incorrect VTY charset?
by bugzilla_noreply＠novell.com 09 May '19

09 May '19

http://bugzilla.novell.com/show_bug.cgi?id=606436 http://bugzilla.novell.com/show_bug.cgi?id=606436#c0 Summary: Incorrect VTY charset? Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/5332 (KHTML, like Gecko) Chrome/5.0.342.9 Safari/533.2 I installed openSUSE 11.3 Milestone 6 in the hungarian language. Interestingly when using the text-mode virtual terminals, (at least) two letters of the hungarian alphabet are displayed incorrectly: I get õ instead of ő, and û instead of ű. This is the same as displaying a hungarian text file (written in iso-8859-2) using iso-8859-1. Isn't it unicode? Or are just the characters wrongly positioned in the charset table? Also see: http://bugzilla.novell.com/show_bug.cgi?id=605575 Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 935419] New: with 3 monitors on 2 graphic cards Xorg crash on xrandr change
by bugzilla_noreply＠novell.com 07 May '19

07 May '19

http://bugzilla.suse.com/show_bug.cgi?id=935419 Bug ID: 935419 Summary: with 3 monitors on 2 graphic cards Xorg crash on xrandr change Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: tcech(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- I found some spare monitor and graphic card so I wanted to put that all together. I started with 2 monitors attached to Intel graphic card (probably onboard). In BIOS is integrated Intel graphics set as the primary video. HDMI 1 and HDMI 2 +--------+ +-----+ | 1920 | |1080 | | 1080 | |1920 | +--------+ | | | | +-----+ $ xrandr --output HDMI1 \ --mode 1920x1080 --primary \ --output HDMI2 \ --mode 1920x1080 --rotate left --right-of HDMI1 I connected third monitor to spare Radeon graphic card. I tried to write my configuration by hand but in the end I wiped all my changes to /etc/X11/xorg.conf.d and did reboot. Luckily XRandr shown all the monitors as hoped. Unfortunately, when I pass command like this, Xorg dies with SIGSEGV. $ xrandr --output DVI-1-0 --mode 1280x1024 --rotate left --right-of HDMI2 I tried to put it all into single command with the same result. Any workaround would be appreciated as well. GDB shown this backtrace (gdb) bt #0 DamageRegister (pDrawable=0x0, pDamage=0x25d8c80) at damage.c:1715 #1 0x00000000004bcd39 in xf86RotatePrepare (pScreen=0x2082ad0) at xf86Rotate.c:170 #2 xf86RotateRedisplay (pScreen=0x2082ad0) at xf86Rotate.c:191 #3 xf86RotateBlockHandler (pScreen=0x2082ad0, pTimeout=0x7ffc1fb04778, pReadmask=0x827300 <LastSelectMask>) at xf86Rotate.c:242 #4 0x0000000000441787 in BlockHandler (pTimeout=pTimeout@entry=0x7ffc1fb04778, pReadmask=pReadmask@entry=0x827300 <LastSelectMask>) at dixutils.c:390 #5 0x0000000000587cbc in WaitForSomething (pClientsReady=pClientsReady@entry=0x24f83a0) at WaitFor.c:215 #6 0x000000000043cda1 in Dispatch () at dispatch.c:361 #7 0x0000000000440e2b in dix_main (argc=10, argv=0x7ffc1fb04b78, envp=<optimized out>) at main.c:298 #8 0x00007f20ed1a08c5 in __libc_start_main (main=0x42c430 <main>, argc=10, argv=0x7ffc1fb04b78, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc1fb04b68) at libc-start.c:289 #9 0x000000000042c469 in _start () at ../sysdeps/x86_64/start.S:118 note that pDrawable=0 in damage.c you can see it has to die: 1713 DamageRegister(DrawablePtr pDrawable, DamagePtr pDamage) 1714 { 1715 ScreenPtr pScreen = pDrawable->pScreen; I can provide whole coredump if you tell me where to upload it. I'm running Tumbleweed, versions installed: # LC_ALL=C LANG=C zypper se -si xorg Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+-----------------------------+---------+------------------+--------+------------------ i | xorg-cf-files | package | 1.0.5-5.1 | noarch | repo-oss i | xorg-scripts | package | 1.0.1-10.1 | noarch | repo-oss i | xorg-sgml-doctools | package | 1.11-9.1 | noarch | repo-oss i | xorg-x11 | package | 7.6_1-16.1 | noarch | repo-oss i | xorg-x11-Xvnc | package | 7.6_1.0.1-15.1.3 | x86_64 | (System Packages) i | xorg-x11-devel | package | 7.6-47.1 | noarch | repo-oss i | xorg-x11-driver-input | package | 7.6_1-13.1 | noarch | repo-oss i | xorg-x11-driver-video | package | 7.6_1-15.1 | x86_64 | repo-oss i | xorg-x11-essentials | package | 7.6_1-16.1 | noarch | repo-oss i | xorg-x11-fonts | package | 7.6-31.2 | noarch | repo-oss i | xorg-x11-fonts-core | package | 7.6-31.2 | noarch | repo-oss i | xorg-x11-libX11-ccache | package | 7.6-20.1 | noarch | repo-oss i | xorg-x11-server | package | 7.6_1.17.1-8.1 | x86_64 | repo-oss i | xorg-x11-server-debuginfo | package | 7.6_1.17.1-8.1 | x86_64 | repo-debug i | xorg-x11-server-debugsource | package | 7.6_1.17.1-8.1 | x86_64 | repo-debug i | xorg-x11-server-extra | package | 7.6_1.17.1-8.1 | x86_64 | repo-oss i | xorg-x11-util-devel | package | 7.6_1-10.1 | noarch | repo-oss -- You are receiving this mail because: You are on the CC list for the bug.

1 8