December 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 954453] New: Can't "Unify Outputs" with KDE System Settings
by bugzilla_noreply＠novell.com 13 Apr '18

13 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=954453 Bug ID: 954453 Summary: Can't "Unify Outputs" with KDE System Settings Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: fweiss(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- When I try to unify my monitors in the "Display Configuration" menu of "System Settings" it only unifies the resolution but not the content. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 954268] New: IRC client quassel, part quassel-core: not able to connect to SQLite and create a user there.
by bugzilla_noreply＠novell.com 13 Apr '18

13 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=954268 Bug ID: 954268 Summary: IRC client quassel, part quassel-core: not able to connect to SQLite and create a user there. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mcaj(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- quassel-core not able to connect to SQLite When I installed prure and fresh openSUSE Leap 4.1 and tried to setup the quasselcore service I found this , I think its a bug. Steps to reproduce are: 1. on openSUSE Leap 42.1 fresh updated machine install the quassel include these packages: quassel-core quassel-base quassel-client quassel-mono. 2. setup SSL there via this howto: openssl req -x509 -nodes -days 365 -newkey rsa:4096 -keyout ~/.config/quassel-irc.org/quasselCert.pem -out /var/lib/quasselcore/quasselCert.pem 3. enable listen the core on $MACHINE-IP-ADDRESS in the file /etc/sysconfig/quasselcore add line: QUASSELCORE_LISTEN="$MACHINE-IP-ADDRESS" 4. start service via:# systemctl start quasselcore.service and if you check the status you can see this output: systemctl status quasselcore.service quasselcore.service - Quassel Core Loaded: loaded (/usr/lib/systemd/system/quasselcore.service; disabled) Active: active (running) since Mon 2015-11-09 15:20:29 CET; 4s ago Main PID: 25284 (quasselcore) CGroup: /system.slice/quasselcore.service └─25284 /usr/bin/quasselcore --listen=$MACHINE-IP-ADDRESS --configdir=/var/lib/quasselcore --logfile=/var/log/quassel/quasselcore Nov 09 15:20:29 $MACHINE quasselcore[25284]: ("QSQLITE") Nov 09 15:20:29 $MACHINE quasselcore[25284]: Core is currently not configured! Please connect with a Quassel Client for basic setup. so far so good now let do the basic setup with the client run :# quasselclient 5. add the core as your hostname $MACHINE or $MACHINE-IP-ADDRESS on port 4242. If you connect into the core you shold see the core configuration wizard. click on "next". Now we are creating the Admin user, it can be any user let say user: ircmaster with some *safe* password then click on next and select only one storage Backed is available: SQLite and "Commit" it we see please way window never finish .... 6. on the log file there are these messages: 2015-11-09 15:24:31 Info: Client connected from $MACHINE-IP-ADDRESS 2015-11-09 15:24:31 Info: Closing server for basic setup. 2015-11-09 15:27:58 Warning: Unable to open database SQLite for thread 0x9b7700 2015-11-09 15:27:58 Warning: - out of memory Error opening database 2015-11-09 15:27:58 Warning: Database connection "SQLite" for thread QThread(0x9b7700) was lost, attempting to reconnect... 2015-11-09 15:27:58 Warning: Unable to open database SQLite for thread 0x9b7700 2015-11-09 15:27:58 Warning: - out of memory Error opening database 2015-11-09 15:27:58 Error: FATAL: Selected storage backend is not available: "SQLite" and if we check the service status: # systemctl status quasselcore.service -l quasselcore.service - Quassel Core Loaded: loaded (/usr/lib/systemd/system/quasselcore.service; disabled) Active: failed (Result: exit-code) since Mon 2015-11-09 15:27:58 CET; 2min 59s ago Process: 25284 ExecStart=/usr/bin/quasselcore --listen=${QUASSELCORE_LISTEN} --configdir=/var/lib/quasselcore --logfile=/var/log/quassel/quasselcore (code=exited, status=1/FAILURE) Main PID: 25284 (code=exited, status=1/FAILURE) PS for the SQL lite I installed: sqlite2 and sqllite3, python-pysqlite, libQt5Sql5 and libQt5Sql5-sqlite packages. if the quassel-core need different package it should be installed automatically I think... -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 951414] New: Adding printer requests root password, but denies passwword
by bugzilla_noreply＠novell.com 13 Apr '18

13 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=951414 Bug ID: 951414 Summary: Adding printer requests root password, but denies passwword Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 RC1 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix(a)suse.com Reporter: minimerrill(a)gmail.com QA Contact: jsmeix(a)suse.com Found By: --- Blocker: --- When adding a printer through the KDE System Settings, a prompt pops up asking to 'enter username and password to continue.' If I put in root for user and root password in the password space, it incorrectly says the password is incorrect. I have double-checked the password in other situations and it is fine, but the prompt for the printer refuses to accept it. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 949510] New: wireless lan deauthentication
by bugzilla_noreply＠novell.com 13 Apr '18

13 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=949510 Bug ID: 949510 Summary: wireless lan deauthentication Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Beta 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: rommel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It seems that after transferring a few megabyte of data my wireless connection is always dropped. In dmesg I get: [ 1253.168846] wlan0: authenticate with 00:24:fe:ac:6e:e1 [ 1253.177179] wlan0: send auth to 00:24:fe:ac:6e:e1 (try 1/3) [ 1253.180669] wlan0: authenticated [ 1253.180732] ath5k 0000:02:08.0 wlan0: disabling HT/VHT due to WEP/TKIP use [ 1253.181344] wlan0: associate with 00:24:fe:ac:6e:e1 (try 1/3) [ 1253.185252] wlan0: RX AssocResp from 00:24:fe:ac:6e:e1 (capab=0x411 status=0 aid=1) [ 1253.185397] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 1253.190762] wlan0: associated [ 1309.812699] wlan0: deauthenticated from 00:24:fe:ac:6e:e1 (Reason: 1=UNSPECIFIED) [ 1309.825404] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA This happens with a 02:08.0 Ethernet controller: Qualcomm Atheros AR5212/AR5213 Wireless Network Adapter (rev 01) The kernel driver used is 'ath5k'. Other messages regarding ath5k or cfg80211: [ 11.849116] cfg80211: Calling CRDA to update world regulatory domain [ 13.086344] ath5k 0000:02:08.0: registered as 'phy0' [ 13.852701] ath5k: phy0: Atheros AR2414 chip found (MAC: 0x79, PHY: 0x45) [ 13.852815] cfg80211: Calling CRDA to update world regulatory domain [ 35.883396] ath5k 0000:02:08.0 wlan0: disabling HT/VHT due to WEP/TKIP use [ 37.056068] cfg80211: Calling CRDA to update world regulatory domain [ 483.049422] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA [ 1784.524063] ath5k: ath5k_hw_get_isr: ISR: 0x00040001 IMR: 0x00000000 [ 1784.599781] ath5k 0000:02:08.0 wlan0: disabling HT/VHT due to WEP/TKIP use On the same machine, a SLES12 system was running without problems for months. -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 959988] New: No password queried for encrypted devices after resume from suspend to disk
by bugzilla_noreply＠novell.com 13 Apr '18

13 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=959988 Bug ID: 959988 Summary: No password queried for encrypted devices after resume from suspend to disk Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When having suspended to disk (manually or automatically), the subsequent resume continues to the graphical login prompt (the first screen you see) without querying a password, even if multiple encrypted partitions exist (e.g. root and swap). IMHO this makes an encrypted swap (holding the suspend data) rather ridiculous. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 950934] New: Creating an encrypted LVM during install fails
by bugzilla_noreply＠novell.com 13 Apr '18

13 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=950934 Bug ID: 950934 Summary: Creating an encrypted LVM during install fails Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 RC1 1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: kmhamich(a)upb.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.3.0 Build Identifier: Exact error message can be found here: http://www.hamich.net/img/opensuse_bug_pvm.jpg Reproducible: Always Steps to Reproduce: 1. Copy RC 1 Image to USB stick 2. Try to install openSUSE Leap RC1 with a LVM encrypted partition layout 3. Fails every time Actual Results: Installation fails! Expected Results: An encrypted LVM should be create and the Install should go on as expected. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 918949] New: Kstars will not compile to include INDI for remote telescope control
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=918949 Bug ID: 918949 Summary: Kstars will not compile to include INDI for remote telescope control Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: john_82(a)tiscali.co.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64) Presto/2.12.388 Version/12.16 Build Identifier: I have tried various ways of obtaining Kstars/Ekos and INDI but have had no luck at all. Kstars should include the extras if INDI has been installed. I haven't got far enough to see if the digital single lens remote camera control software can be added Reproducible: Always Steps to Reproduce: 1.Install / Compile Kstars with the requisites for including Ekos and indi around 2. 3. Actual Results: No signs of the control facilities in Kstars Expected Results: Control facilities in Kstars This web page shows what should happen http://www.indilib.org/about/ekos/setup.html :-( Ubuntu provide the lot in one package. There may also be a problem with installing the remote digital camera control sofware for canon, nikon and others. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 908383] New: VirtualBox Kernelmodule not loaded if fstab with not mountable cifs mountpoint
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.opensuse.org/show_bug.cgi?id=908383 Bug ID: 908383 Summary: VirtualBox Kernelmodule not loaded if fstab with not mountable cifs mountpoint Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: juergenhuber(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- 1. Install openSUSE 64bit from scratch 2. Install VirtualBox-qt with yast, install all recommended dependencies 3. Create a new Machine with an .iso - CD-ROM-File -> test Startup of VM -> VM starts up. 4. Add an remote cifs mountpoint to your fstab which isn't online 5. Reboot the Machine 6. Try to start the even working new VM -> VirtualBox reports that the startup isn't possible because the kernel module is missing. 7. Remove the fstab Entry from 4. -> Reboot -> Restart VM, Works again. My sample-Entry to fstab: //192.168.0.1/dat /server cifs users,credentials=/etc/.pass-pw,gid=users,uid=jue 0 0 The credentials-file was available (double-checked). In my case the remote-share is inside of a VM, so the first mount during startup will fail. Since the error appears the mount will never work because the VM cannot come up. Same configuration on openSUSE 12.3 worked. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 956997] New: GNOME Keyring Manager interfering with usage of GPG Smartcards
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=956997 Bug ID: 956997 Summary: GNOME Keyring Manager interfering with usage of GPG Smartcards Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: bhertwig(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to access a GPG-Smartcard, connected to the machine via a Smartcard Reader, the GNOME Keyring Manager acts as a man in the middle, preventing GPG from successfully accessing the data on the Smartcard. benjamin@linux-6l3e:~> gpg --card-status gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent. gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system! gpg: selecting openpgp failed: Nicht unterstütztes Zertifikat gpg: OpenPGP Karte ist nicht vorhanden: Nicht unterstütztes Zertifikat A workaround to this issue, is to run the command in a root-shell. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 953836] New: laptop with KDE4: kde/powermgmt applet: when using multiple sessions on battery, all power mgmt applets can and will trigger suspend actions although one session is active all the time
by bugzilla_noreply＠novell.com 12 Apr '18

12 Apr '18

http://bugzilla.suse.com/show_bug.cgi?id=953836 Bug ID: 953836 Summary: laptop with KDE4: kde/powermgmt applet: when using multiple sessions on battery, all power mgmt applets can and will trigger suspend actions although one session is active all the time Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: kde-maintainers(a)suse.de Reporter: rens.groenewegen(a)xs4all.nl QA Contact: qa-bugs(a)suse.de CC: eshmarnev(a)suse.com, kde-maintainers(a)suse.de Depends on: 741893 Found By: --- Blocker: --- problem is still there. it's like 3-4 years old now, any intention of doing something about it ?? +++ This bug was initially created as a clone of Bug #741893 +++ User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 laptop KDE4: kde/powermgmt applet: when using multiple sessions, all power mgmt applets can and will trigger suspend actions although one session is active all the time. My use case is as follows: 1 session for linux desktop ( tty7) 1 session for linux desktop running vmware-view VDI session fullscreen ( tty8 ) If I am active in tty7, tty8 will trigger a suspend after 10 minutes and vice versa, although mouse and keyboard are active. Reproducible: Always Steps to Reproduce: 1.start extra session on tty8, run laptop on battery mode or configure powermanager to suspend after some minutes. 2. ensure powermgmt applet is loaded on both tty7 and tty8 session 3. start working in any of tty7 /tty8 and wait until powermanagement in the non-active tty suspends the system Actual Results: laptop suspends, in the midst of working. Expected Results: powermgmt should watch activity on keyboard / mouse, irrespective of which active terminal i think this is a major feature broken, *if* you are working on a laptop. for desktops, this "bug" doesnt matter much. -- You are receiving this mail because: You are on the CC list for the bug.

1 4