December 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 905110] New: Bugreporter fails reporting bugs
by bugzilla_noreply＠novell.com 06 Sep '17

06 Sep '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905110 Bug ID: 905110 Summary: Bugreporter fails reporting bugs Classification: openSUSE Product: openSUSE Factory Version: NO 13.2 BUGS!! Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: erwin.vandevelde(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Version: bugreporter 1.0-10.1 Failure after entering summary: bugreporter Welcome to the submit bug report module! The user has stored credentials. Connecting to Novell's Bugzilla... If you don't know which package you want to file a bug to, you can use the susebugreport aid command to get some help. Which is the package you want to file a report against? If you are not sure, you can just type the beginning of the name and use a '*' to invoke globbing. Also, you can type '?' to start the aid_user module that helps finding the correct package name. Package name (or '?'): wicked Package selected: wicked Please enter the bug summary (should be short!) --> Many packages unnecessarily depend on wicked Summary entered: Many packages unnecessarily depend on wicked Looking for similar existing bug reports... Traceback (most recent call last): File "/usr/bin/bugreporter", line 353, in <module> main() File "/usr/bin/bugreporter", line 343, in main do_submit() File "/usr/bin/bugreporter", line 152, in do_submit bug_list = bz.query({'summary': name}) File "/usr/lib/python2.7/site-packages/bugzilla/base.py", line 929, in query r = self._query(query) File "/usr/lib/python2.7/site-packages/bugzilla/base.py", line 919, in _query return self._proxy.Bug.search(query) File "/usr/lib64/python2.7/xmlrpclib.py", line 1234, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1588, in __request verbose=self.__verbose File "/usr/lib/python2.7/site-packages/bugzilla/base.py", line 170, in request return self.parse_response(stringio) File "/usr/lib64/python2.7/xmlrpclib.py", line 1477, in parse_response p.feed(data) File "/usr/lib64/python2.7/xmlrpclib.py", line 562, in feed self._parser.Parse(data, 0) xml.parsers.expat.ExpatError: syntax error: line 1, column 62 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 819066] New: Cannot enter "kwallet" nor "ssh" key during logon with "ssh-add" turn on in "/etc/X11/xinit/xinitrc"
by bugzilla_noreply＠novell.com 30 Aug '17

30 Aug '17

https://bugzilla.novell.com/show_bug.cgi?id=819066 https://bugzilla.novell.com/show_bug.cgi?id=819066#c0 Summary: Cannot enter "kwallet" nor "ssh" key during logon with "ssh-add" turn on in "/etc/X11/xinit/xinitrc" Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: DOlsson(a)WEB.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 After having activated (i.e. removed the '#' comments in lines 48-50 in "/etc/X11/xinit/xinitrc") the call of "ssh-add", I am not able to enter neither the "kwallet" key (for which I am first asked for) nor the "ssh" key (which is asked for afterwards). The reason for this is that the keyboard is no active anymore. I am able to use the mouse to select the input field, but nothing that I try to type gets entered, nor can I move the focus from the input field to one of the buttons using the <TAB> key! Reproducible: Always Steps to Reproduce: 1. Install a fresh openSUSE 12.3 using KDE as desktop. 2. Edit the "/etc/X11/xinit/xinitrc" removing the '#' comments, thus enabling the call of "ssh-add" during logon. 3. Create a "ssh" key for the user. 4. Create a "kwallet" to keep the keys in. Actual Results: Unable to use the keyboard to enter the asked for keys. Expected Results: When the "kwallet" and "ssh-add" applications shows their pop-up windows, the input field should be selected and the keyboard focus should have been activated, thus allowing for the entering of the asked for keys. -- 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 17

[Bug 902067] New: Yast2 Live Installer has no icon in Gnome
by bugzilla_noreply＠novell.com 28 Aug '17

28 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=902067 Bug ID: 902067 Summary: Yast2 Live Installer has no icon in Gnome Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: sjharms(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The Yast2 Live Installer shows no icon when using Gnome 3 Live CD install -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 909730] New: YaST modules have no application icon shown
by bugzilla_noreply＠novell.com 27 Aug '17

27 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=909730 Bug ID: 909730 Summary: YaST modules have no application icon shown Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: i(a)marguerite.su QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hi, Currently YaST control center itself has an application icon set by setWindowIcon(QIcon), but separate YaST modules still use X icon. But in our codebase I did see such implementation eg: https://github.com/yast/yast-yast2/blob/master/library/desktop/src/modules/… Maybe I was wrong, but it would be better if common modules such as sw_single can have their own application icon (yast-sw-single) instead of X icon. Marguerite -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 730327] New: vusb-analyzer needs 'gnomecanvas'
by bugzilla_noreply＠novell.com 27 Aug '17

27 Aug '17

https://bugzilla.novell.com/show_bug.cgi?id=730327 https://bugzilla.novell.com/show_bug.cgi?id=730327#c0 Summary: vusb-analyzer needs 'gnomecanvas' Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: afaerber(a)suse.com QAContact: qa(a)suse.de Found By: --- Blocker: --- On openSUSE 12.1 RC2, `vusb-analyzer` resulted in: Traceback (most recent call last): File "/usr/bin/vusb-analyzer", line 13, in <module> from VUsbTools import Views, Log, Diff, Decode File "/usr/lib/python2.7/site-packages/VUsbTools/Views.py", line 15, in <module> from VUsbTools import Types, Style File "/usr/lib/python2.7/site-packages/VUsbTools/Types.py", line 20, in <module> except gnomecanvas: NameError: name 'gnomecanvas' is not defined Installing python-gnome package resolved this. A suitable Depends: should be added to the vusb-analyzer package. -- 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 3

[Bug 789020] New: no more /dev/disk/by-label/LABEL symlinks for LVM devices (udev/systemd?)
by bugzilla_noreply＠novell.com 18 Aug '17

18 Aug '17

https://bugzilla.novell.com/show_bug.cgi?id=789020 https://bugzilla.novell.com/show_bug.cgi?id=789020#c0 Summary: no more /dev/disk/by-label/LABEL symlinks for LVM devices (udev/systemd?) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa-bugs(a)suse.de Found By: Third Party Developer/Partner Blocker: --- After updating to today's FACTORY (last update was before openSUSE conf), my /space and /local partitions were no longer mounted: susi:~ # grep LABEL /etc/fstab LABEL=root-FACTORY / ext4 acl,user_xattr 1 1 # LABEL=local /local xfs noatime,logbufs=8,logbsize=262144 1 2 # LABEL=space /space xfs noatime,logbufs=8,logbsize=262144 1 2 (now commented out to get the system to boot) susi:~ # l /dev/disk/by-label/ total 0 drwxr-xr-x 2 root root 140 Nov 9 15:50 ./ drwxr-xr-x 6 root root 120 Nov 9 15:50 ../ lrwxrwxrwx 1 root root 10 Nov 9 15:50 BOOTLOADER -> ../../sda3 lrwxrwxrwx 1 root root 10 Nov 9 15:50 SYSTEM_DRV -> ../../sda1 lrwxrwxrwx 1 root root 10 Nov 9 15:50 Windows7_OS -> ../../sda2 lrwxrwxrwx 1 root root 10 Nov 9 15:50 root-FACTORY -> ../../sda6 lrwxrwxrwx 1 root root 10 Nov 9 15:50 root-stable -> ../../sda8 susi:~ # blkid /dev/sda1: LABEL="SYSTEM_DRV" UUID="7A0615220614E0C5" TYPE="ntfs" /dev/sda2: LABEL="Windows7_OS" UUID="64A42A12A429E6F0" TYPE="ntfs" /dev/sda3: LABEL="BOOTLOADER" UUID="519614e1-7c40-4866-b461-3ad4cb797538" SEC_TYPE="ext2" TYPE="ext3" /dev/sda5: UUID="fde71608-8ca9-4f2a-9a3e-501df23f8469" TYPE="swap" /dev/sda6: LABEL="root-FACTORY" UUID="71f5bfb4-3d29-4c9c-929a-3fb795cf0fd9" TYPE="ext4" /dev/sda7: UUID="3387ae99-507c-41eb-80c8-ee7b4a62353a" TYPE="crypto_LUKS" /dev/sda8: LABEL="root-stable" UUID="6983d635-99c0-48e9-b62a-74cd3b27c636" TYPE="ext4" /dev/sda9: UUID="jRlUY0-8mt0-09TE-MeAf-IqRj-TSzl-tK83Uk" TYPE="LVM2_member" /dev/mapper/main-local: LABEL="local" UUID="ac293f98-8e30-440f-8845-d067ee49d42d" TYPE="xfs" /dev/mapper/main-space: LABEL="space" UUID="17676f0d-fe6e-4b47-80bb-6d6493574569" TYPE="xfs" /dev/mapper/main-vdr: UUID="4b5b5706-84bb-4a2c-8f91-fda2784aea86" TYPE="ext4" /dev/mapper/cr_sda7: LABEL="cryptohome" UUID="98741ffb-5913-43ca-afac-500ff16d0f57" TYPE="ext3" susi:~ # blkid|grep LABEL= /dev/sda1: LABEL="SYSTEM_DRV" UUID="7A0615220614E0C5" TYPE="ntfs" /dev/sda2: LABEL="Windows7_OS" UUID="64A42A12A429E6F0" TYPE="ntfs" /dev/sda3: LABEL="BOOTLOADER" UUID="519614e1-7c40-4866-b461-3ad4cb797538" SEC_TYPE="ext2" TYPE="ext3" /dev/sda6: LABEL="root-FACTORY" UUID="71f5bfb4-3d29-4c9c-929a-3fb795cf0fd9" TYPE="ext4" /dev/sda8: LABEL="root-stable" UUID="6983d635-99c0-48e9-b62a-74cd3b27c636" TYPE="ext4" /dev/mapper/main-local: LABEL="local" UUID="ac293f98-8e30-440f-8845-d067ee49d42d" TYPE="xfs" /dev/mapper/main-space: LABEL="space" UUID="17676f0d-fe6e-4b47-80bb-6d6493574569" TYPE="xfs" /dev/mapper/cr_sda7: LABEL="cryptohome" UUID="98741ffb-5913-43ca-afac-500ff16d0f57" TYPE="ext3" As you can see, the non-LVM devices are there in /dev/disk/by-label, but the LVM devices are not. I guess this is a glitch of the new udev version. -- 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 904987] New: Dracut not working as expected with full-disk encryption
by bugzilla_noreply＠novell.com 18 Aug '17

18 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=904987 Bug ID: 904987 Summary: Dracut not working as expected with full-disk encryption Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: fedev(a)gmx.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 613252 --> http://bugzilla.opensuse.org/attachment.cgi?id=613252&action=edit Screenshot - emergency console after upgrade Hi there, My laptop has full disk encryption with luks. It was working without problems until openSUSE 13.2. It seems dracut checks for encrypted partitions and volumes on crypttab however I did not have the partition listed in crypttab because all this time the luks partition information was added by grub (if not mistaken). Well, dracut seems can't recognize an unlocked luks partition/volume on its own nor from the previous used settings. Dracut was then trying to look for the volumes for home and root without trying to unlock first for the encrypted partition. There are two workarounds for this. One, use the kernel boot parameter rd.luks.uuid the other, add the disk to crypttab and then re-run dracut -M --force This however it is not obvious for those doing an upgrade. After doing an upgrade from 13.1 to 13.2, the system is no longer bootable unless you take care of the above first. Thank you. Regards, Fede -- You are receiving this mail because: You are on the CC list for the bug.

1 42

[Bug 901565] New: YaST forgets bridged devices when not visiting "Bridged Devices" tab
by bugzilla_noreply＠novell.com 15 Aug '17

15 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=901565 Bug ID: 901565 Summary: YaST forgets bridged devices when not visiting "Bridged Devices" tab Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: leen.meyer(a)ziggo.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When editing the network settings of a bridge, YaST forgets the bridged devices if one does not visit the "Bridged Devices" tab. A bridge without devices means no working network (via that bridge). This happens in a fresh install of 13.2-RC1 in a virtual machine: virt-install --connect qemu:///system --graphics=vnc --name=os-13-2.site --os-type=linux --os-variant=opensuse12 --ram=2048 --vcpus=1 --network=bridge=br0,mac=02:00:0A:00:0D:02 --disk=path=/var/lib/libvirt/images/os-13-2.site.img,size=10 --cdrom=/var/lib/libvirt/images/openSUSE-13.2-DVD-Build0019-x86_64.iso Precondition: a bridge (br0) with an attached device (eth0) Reproducable: always (minimal text-mode and graphical with KDE) Expected behavior: YaST remembers the bridged devices and sets up the bridge as it was before running yast lan. Next instructions are for text-mode (konsole or non-graphical). brctl show br0 --> 1 device listed (eth0) yast lan --> edit bridge br0 --> do NOT visit the "Bridged Devices" tab, but just press "Next", press "OK". brctl show br0 --> No devices! yast lan -> edit bridge br0 --> visit the "Bridged Devices" tab, checkmark eth0, press "Next", press "OK". brctl show br0 --> 1 device listed: eth0 yast lan --> edit bridge br0 --> visit the "Bridged Devices" tab, note that eth0 is checkmarked, press "Next", press "OK". brctl show br0 --> 1 device listed: eth0 Kind regards, Leendert Meyer -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 911165] New: plasma-mediacenter crashes without backtrace.
by bugzilla_noreply＠novell.com 13 Aug '17

13 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=911165 Bug ID: 911165 Summary: plasma-mediacenter crashes without backtrace. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 618292 --> http://bugzilla.opensuse.org/attachment.cgi?id=618292&action=edit output from terminal while starting plasma-mediacenter KDE 4.14.3 Plasma-mediacenter from Extra-repo Plasma-mediacenter crashes immediately after starting via the icon. A useful backtrace is not available. I join what I get through Dr Konqi....which is not much. Application: Plasma Mediacenter Shell (plasma-mediacenter), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc3098f37c0 (LWP 25993))] Thread 4 (Thread 0x7fc2f5417700 (LWP 25996)): #0 0x00007fff64800b6c in ?? () #1 0x0000000000007fc2 in ?? () #2 0x0000000100000000 in ?? () #3 0xf00030e000000000 in ?? () #4 0xf5416c6800007fc2 in ?? () #5 0xf5416c0000007fc2 in ?? () #6 0x7fffffff00007fc2 in ?? () #7 0x06ee000000000000 in ?? () #8 0xf5416c7000007fc3 in ?? () #9 0x0655a43d00007fc2 in ?? () #10 0xf5416c6400007fc3 in ?? () #11 0x06e05d4700007fc2 in ?? () #12 0x0000000000007fc3 in ?? () #13 0x7fffffff00000000 in ?? () #14 0x0000057600000000 in ?? () #15 0x0973115f00000000 in ?? () #16 0xf00009a000007fc3 in ?? () #17 0x06ee187500007fc2 in ?? () #18 0x06ee055000007fc3 in ?? () #19 0xf5416c6400007fc3 in ?? () #20 0xf5416c7000007fc2 in ?? () #21 0xf5416c6800007fc2 in ?? () #22 0x0000000000007fc2 in ?? () #23 0x06edff8c00000000 in ?? () #24 0x0000000000007fc3 in ?? () #25 0x0000000000000000 in ?? () Thread 3 (Thread 0x7fc2ef8d7700 (LWP 25997)): #0 0x00007fc30651f6cd in nanosleep () from /lib64/libc.so.6 #1 0x00007fc306547184 in usleep () from /lib64/libc.so.6 #2 0x00007fc262927a1a in ?? () from /usr/lib64/libsqlite3.so.0 #3 0x00007fc26295da7f in ?? () from /usr/lib64/libsqlite3.so.0 #4 0x00007fc26295ee02 in ?? () from /usr/lib64/libsqlite3.so.0 #5 0x00007fc26295f999 in ?? () from /usr/lib64/libsqlite3.so.0 #6 0x00007fc262986034 in ?? () from /usr/lib64/libsqlite3.so.0 #7 0x00007fc26298a7df in sqlite3_step () from /usr/lib64/libsqlite3.so.0 #8 0x00007fc262be0a2c in ?? () from /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so #9 0x00007fc262be1758 in ?? () from /usr/lib64/qt4/plugins/sqldrivers/libqsqlite.so #10 0x00007fc302a52682 in QSqlQuery::exec() () from /usr/lib64/libQtSql.so.4 #11 0x00007fc2f42b795f in Baloo::FileMapping::fetch(QSqlDatabase) () from /usr/lib64/libbaloofiles.so.4 #12 0x00007fc2ed0ee400 in ?? () from /usr/lib64/kde4/baloo_filesearchstore.so #13 0x00007fc2ef9f1592 in Baloo::XapianSearchStore::url(int) () from /usr/lib64/libbalooxapian.so.4 #14 0x00007fc2ed0ee218 in ?? () from /usr/lib64/kde4/baloo_filesearchstore.so #15 0x00007fc2f44e0454 in Baloo::ResultIterator::text() const () from /usr/lib64/libbaloocore.so.4 #16 0x00007fc2f471ef17 in ?? () from /usr/lib64/kde4/pmc_baloosearch.so #17 0x00007fc2f471fc7d in ?? () from /usr/lib64/kde4/pmc_baloosearch.so #18 0x00007fc2f47200a0 in ?? () from /usr/lib64/kde4/pmc_baloosearch.so #19 0x00007fc306ecb59e in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #20 0x00007fc3078cd76c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #21 0x00007fc3078d3cad in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #22 0x00007fc3090acbaa in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #23 0x00007fc306eb32ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #24 0x00007fc306eb657d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #25 0x00007fc306ee08fe in ?? () from /usr/lib64/libQtCore.so.4 #26 0x00007fc30213ba04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #27 0x00007fc30213bc48 in ?? () from /usr/lib64/libglib-2.0.so.0 #28 0x00007fc30213bcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #29 0x00007fc306ee00be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #30 0x00007fc306eb1e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x00007fc306eb2165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #32 0x00007fc306daf0bf in QThread::exec() () from /usr/lib64/libQtCore.so.4 #33 0x00007fc306db179f in ?? () from /usr/lib64/libQtCore.so.4 #34 0x00007fc303b780a4 in start_thread () from /lib64/libpthread.so.0 #35 0x00007fc30654d7fd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fc2ee4d7700 (LWP 25998)): #0 0x00007fc303b7c05f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fc302e0f8cb in ?? () from /usr/lib64/libQtScript.so.4 #2 0x00007fc302e0f909 in ?? () from /usr/lib64/libQtScript.so.4 #3 0x00007fc303b780a4 in start_thread () from /lib64/libpthread.so.0 #4 0x00007fc30654d7fd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fc3098f37c0 (LWP 25993)): [KCrash Handler] #5 0x00007fc30649d187 in raise () from /lib64/libc.so.6 #6 0x00007fc30649e538 in abort () from /lib64/libc.so.6 #7 0x00007fc306da72b4 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/libQtCore.so.4 #8 0x00007fc306da7439 in ?? () from /usr/lib64/libQtCore.so.4 #9 0x00007fc306da7c44 in qFatal(char const*, ...) () from /usr/lib64/libQtCore.so.4 #10 0x000000000040c702 in ?? () #11 0x000000000040e986 in ?? () #12 0x00007fc3090b3dca in ?? () from /usr/lib64/libkdeui.so.5 #13 0x00007fc3090b3e45 in ?? () from /usr/lib64/libkdeui.so.5 #14 0x00007fc3090b4053 in ?? () from /usr/lib64/libkdeui.so.5 #15 0x00007fc3054cdd4d in ?? () from /usr/lib64/libQtDBus.so.4 #16 0x00007fc3054ceed9 in ?? () from /usr/lib64/libQtDBus.so.4 #17 0x00007fc3054cf9bd in ?? () from /usr/lib64/libQtDBus.so.4 #18 0x00007fc3054cfa8b in ?? () from /usr/lib64/libQtDBus.so.4 #19 0x00007fc306ecb59e in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #20 0x00007fc3078d2733 in QApplication::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #21 0x00007fc3078cd76c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #22 0x00007fc3078d3cad in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #23 0x00007fc3090acbaa in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #24 0x00007fc306eb32ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #25 0x00007fc306eb657d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4 #26 0x00007fc306ee08fe in ?? () from /usr/lib64/libQtCore.so.4 #27 0x00007fc30213ba04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00007fc30213bc48 in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00007fc30213bcec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00007fc306ee00be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #31 0x00007fc30796a676 in ?? () from /usr/lib64/libQtGui.so.4 #32 0x00007fc306eb1e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #33 0x00007fc306eb2165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #34 0x00007fc306eb75b9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #35 0x000000000040a1fe in ?? () #36 0x00007fc306489b05 in __libc_start_main () from /lib64/libc.so.6 #37 0x000000000040a5d8 in _start () The output you get from terminal is as indicated in the attachment. This is a fresh install on a 64 bit system with nvidea gpu and nouveau driver. What the software does: crashes immediately. What it should: work as forseen (open the mediacenter) This bug is perfectly repeatable, the software is 100% unusable. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 903972] New: System upgrade procedure from DVD from 13.1 to 13.2 fails because it cannot setup the network
by bugzilla_noreply＠novell.com 13 Aug '17

13 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903972 Bug ID: 903972 Summary: System upgrade procedure from DVD from 13.1 to 13.2 fails because it cannot setup the network Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stakanov(a)freenet.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Try to setup the new 13.2 on a Lenovo 201 with or without docking station. Although the network is present and the machine branched directly to the modem router the networksetupprocedure will stay on the dialog choice between "setup the network now" yes or no, because it just jumps back to it. Either no network is found or the dialogue is hanging? As a result, no internetconnection is found and all repos are lost. A real upgrade is therefore not possible from DVD-64. You get of course a big bunch of missing dependencies. This is constant, whether you use the ultrabase for the installation or the standalone notebook. -- You are receiving this mail because: You are on the CC list for the bug.

1 34