February 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 803021] New: akonadi crashes when starting
by bugzilla_noreply＠novell.com 12 Feb '13

12 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=803021 https://bugzilla.novell.com/show_bug.cgi?id=803021#c0 Summary: akonadi crashes when starting Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: aj(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Product Management Blocker: --- After updating to RC1 kmail crashes when starting up, backtrace is: Application: SUSE of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f87845bf780 (LWP 6454))] Thread 2 (Thread 0x7f8772359700 (LWP 7168)): #0 0x00007f878001a87d in poll () from /lib64/libc.so.6 #1 0x00007f877ed6faa4 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f877ed6fbc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f8783a271c6 in QEventDispatcherGlib::processEvents (this=0x7f8768006bf0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x00007f87839f79bf in QEventLoop::processEvents (this=this@entry=0x7f8772358de0, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f87839f7c48 in QEventLoop::exec (this=0x7f8772358de0, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f87838fa0c0 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542 #7 0x00007f8782646ad7 in KIMAP::SessionThread::run (this=0xea9b20) at /usr/src/debug/kdepimlibs-4.10.0/kimap/sessionthread.cpp:183 #8 0x00007f87838fd09c in QThreadPrivate::start (arg=0xea9b20) at thread/qthread_unix.cpp:338 #9 0x00007f877f8c8e0f in start_thread () from /lib64/libpthread.so.0 #10 0x00007f87800237dd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f87845bf780 (LWP 6454)): [KCrash Handler] #6 0x0000000000000000 in ?? () #7 0x00007f87826676ee in qDeleteAll<QList<KIMAP::Job*>::const_iterator> (end=..., begin=...) at /usr/include/QtCore/qalgorithms.h:322 #8 qDeleteAll<QQueue<KIMAP::Job*> > (c=...) at /usr/include/QtCore/qalgorithms.h:330 #9 0x00007f878265c694 in KIMAP::SessionPrivate::clearJobQueue (this=0xeaa440) at /usr/src/debug/kdepimlibs-4.10.0/kimap/session.cpp:407 #10 0x00007f8783a0d65e in QObject::event (this=0xe8b9a0, e=<optimized out>) at kernel/qobject.cpp:1203 #11 0x00007f8782da286c in QApplicationPrivate::notify_helper (this=this@entry=0x8468b0, receiver=receiver@entry=0xe8b9a0, e=e@entry=0x7f876800aff0) at kernel/qapplication.cpp:4562 #12 0x00007f8782da6ceb in QApplication::notify (this=0x7fff6ac387b0, receiver=0xe8b9a0, e=0x7f876800aff0) at kernel/qapplication.cpp:4423 #13 0x00007f8780f09cb6 in KApplication::notify (this=0x7fff6ac387b0, receiver=0xe8b9a0, event=0x7f876800aff0) at /usr/src/debug/kdelibs-4.10.0/kdeui/kernel/kapplication.cpp:311 #14 0x00007f87839f8c6e in QCoreApplication::notifyInternal (this=0x7fff6ac387b0, receiver=receiver@entry=0xe8b9a0, event=event@entry=0x7f876800aff0) at kernel/qcoreapplication.cpp:946 #15 0x00007f87839fc5d1 in sendEvent (event=0x7f876800aff0, receiver=0xe8b9a0) at kernel/qcoreapplication.h:231 #16 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x81b0b0) at kernel/qcoreapplication.cpp:1570 #17 0x00007f8783a27013 in sendPostedEvents () at kernel/qcoreapplication.h:236 #18 postEventSourceDispatch (s=0x841940) at kernel/qeventdispatcher_glib.cpp:279 #19 0x00007f877ed6f7d5 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #20 0x00007f877ed6fb08 in ?? () from /usr/lib64/libglib-2.0.so.0 #21 0x00007f877ed6fbc4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #22 0x00007f8783a271a6 in QEventDispatcherGlib::processEvents (this=0x820d10, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #23 0x00007f8782e42c1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #24 0x00007f87839f79bf in QEventLoop::processEvents (this=this@entry=0x7fff6ac36c00, flags=...) at kernel/qeventloop.cpp:149 #25 0x00007f87839f7c48 in QEventLoop::exec (this=0x7fff6ac36c00, flags=...) at kernel/qeventloop.cpp:204 #26 0x00007f87832569c8 in QDialog::exec (this=0xb51970) at dialogs/qdialog.cpp:554 #27 0x0000000000417f44 in _start () -- 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 1

[Bug 803221] New: website hangs firefox and causes konqueror (webkit) to use 100%+ of CPU
by bugzilla_noreply＠novell.com 12 Feb '13

12 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=803221 https://bugzilla.novell.com/show_bug.cgi?id=803221#c0 Summary: website hangs firefox and causes konqueror (webkit) to use 100%+ of CPU Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox AssignedTo: bnc-team-mozilla(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 If I go here: http://www.thinkmate.com/System/STX_XD24-2210/SSD_Caching firefox *hangs* (becomes unresponsive) and uses 100% of CPU konqueror actually ends up using /more/ than 100% of the CPU, doesn't hang, but doesn't respond, either. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 1

[Bug 801618] New: Gnome shell sometimes loses the application entry in top panel
by bugzilla_noreply＠novell.com 12 Feb '13

12 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=801618 https://bugzilla.novell.com/show_bug.cgi?id=801618#c0 Summary: Gnome shell sometimes loses the application entry in top panel Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: badshah400(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=522930) --> (http://bugzilla.novell.com/attachment.cgi?id=522930) Screenshot with problem User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Gnome-shell would sometimes stop showing the application entry (which is supposed to appear just beside the "Activities" button on top left) in the top panel, making it impossible to close applications like nautilus, gnome-documents, etc when they are maximised (unless either by restoring them, or by using keyboard shortcuts). Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 4

[Bug 735864] New: PackageKit zypp backend: doesn't properly support printer driver search
by bugzilla_noreply＠novell.com 11 Feb '13

11 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=735864 https://bugzilla.novell.com/show_bug.cgi?id=735864#c0 Summary: PackageKit zypp backend: doesn't properly support printer driver search Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: dmacvicar(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: jsmeix(a)suse.com CC: jsmeix(a)suse.com, vuntz(a)suse.com Found By: --- Blocker: --- the zypp backend's what_provides() function apparently lacks support for proper mapping of searches for type PK_PROVIDES_ENUM_POSTSCRIPT_DRIVER (and others). For printers the backend needs to add "postscriptdriver(" for example. How to test: - run gnome - rpm -q --provides gutenprint - rpm -e gutenprint - plug in some printer that matches one of the provides => the automatism (or if that doesn't work use sytem-config-printer manually) should automatically suggest to install gutenprint -- 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 803177] New: build-compare: case-insensitively compare *release*
by bugzilla_noreply＠novell.com 11 Feb '13

11 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=803177 https://bugzilla.novell.com/show_bug.cgi?id=803177#c0 Summary: build-compare: case-insensitively compare *release* Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: General AssignedTo: adrian(a)suse.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: adrian(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Actually, there are two issues: 1. the Open Build Service is listed as 'openSUSE Build Service' in bugzilla. It probably ought to default to setting the Product Version to the latest stable (2.3 as of this writing), too. 2. srpm-check.sh doesn't compare release case-insensitively. Technically, all rpm tags are case-insensitive, but since the OBS increments the release number, specfiles with "release" (instead of "Release") or any case-variation thereof always show up as a changed specfile. Stand by for a patch for (2). Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 2

[Bug 776204] New: "Edit Search" clears "A Comment Matches" (edit search does not edit previous search)
by bugzilla_noreply＠novell.com 11 Feb '13

11 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=776204 https://bugzilla.novell.com/show_bug.cgi?id=776204#c0 Summary: "Edit Search" clears "A Comment Matches" (edit search does not edit previous search) Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure AssignedTo: mrueckert(a)suse.com ReportedBy: mrmazda(a)earthlink.net QAContact: lrupp(a)suse.com Found By: --- Blocker: --- Bugzilla.novell.com's advanced search deviates from bugzilla.mozilla.org's in having <input> "A Comment Matches" instead of <select> "Comment". On both mozilla.org and novell.com, clicking "Edit Search" reopens the previous search for editing, except novell.com doesn't exactly, clearing "A Comment Matches", while mozilla.org retains the previous "Comment", and every other field, exactly. Novell.com's behavior makes it difficult to search efficiently and wastes bandwidth, causing search results containing hundreds or thousands of search results due to the empty "A Comment Matches" field, which in many cases is crucially important, yet easily overlooked due to intent to make a trivial edit to e.g. date range, product, classification, etc. Mozilla.org's preservation of the field obviates need to remember and replicate the previous search, while novell.com's clearing of the field forces the user to remember precisely in order to be able to institute appropriate changes after search results were unhelpful and need to be repeated only slightly differently. "A Comment Matches" should not be cleared when the search page from clicking the "Edit Search" link opens. Better yet, dispense with the "A Comment Matches" field entirely, and institute the default mozilla.org "Comment:" field, complete with its behavior of retaining the previous search exactly after an "Edit Search" click. I have to think it would be an easier fix to more closely conform to the OEM Bugzilla configuration. -- 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 2

[Bug 794505] New: AutoYaST uses inappropriate space when free space not contiguous (DELL T5600 with LSI MegaRAID 2008)
by bugzilla_noreply＠novell.com 11 Feb '13

11 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=794505 https://bugzilla.novell.com/show_bug.cgi?id=794505#c0 Summary: AutoYaST uses inappropriate space when free space not contiguous (DELL T5600 with LSI MegaRAID 2008) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: AutoYaST AssignedTo: fehr(a)suse.com ReportedBy: pjb1008(a)cam.ac.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=517129) --> (http://bugzilla.novell.com/attachment.cgi?id=517129) Fragment of XML config containing partitioning information User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.1.1 Firefox/3.6.13 Install Windows 7, yielding this partition: [47 heads, 36 sectors/track, 2308478 cylinders] Start | End | Start | Size Hd Sec Cyl | Hd Sec Cyl | Blocks | Blocks 9 33 1 | 46 36 1023 | 2048 | 22528000 The AutoYaST configuration file says to create a partition for /boot of 100MB, which it does. It then creates a logical volume for everything else, with size 'max'. AutoYaST picks the first cylinder for the logical volume (ie. the tiny space) instead of the space at the end of data (nearly the entire disk). Reproducible: Always Steps to Reproduce: 1. Install windows 7 with this type of RAID card. (Hopefully it'll do the same if you just create a appropriate partition on a blank disk.) 2. Install OpenSUSE using the attached disk config. Actual Results: On the screen, the following message is displayed. Error A logical volume with the requested size could not be created. Expected Results: Windows partition left alone near the start of the disk. Linux ext3 /boot just after. Linux LVM PV for the VG occupying the remainder of the disk. Output of fdisk -l -u=cylinders: Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 47 heads, 36 sectors/track, 2308478 cylinders Units = cylinders of 1692 * 512 = 866304 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x66b2d02d Device Boot Start End Blocks Id System /dev/sda1 * 2 133146 112640000 7 HPFS/NTFS/exFAT Output of fdisk -l: Disk /dev/sda: 1999.8 GB, 1999844147200 bytes 47 heads, 36 sectors/track, 2308478 cylinders, total 3905945600 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x66b2d02d Device Boot Start End Blocks Id System /dev/sda1 * 2048 225282047 112640000 7 HPFS/NTFS/exFAT /var/log/YaST2/disk_sda.info: <?xml version="1.0"?> <disk> <name>sda</name> <device>/dev/sda</device> <size_k>1952972800</size_k> <major>8</major> <minor>0</minor> <range>256</range> <geometry> <cylinders>2308478</cylinders> <heads>47</heads> <sectors>36</sectors> </geometry> <label>msdos</label> <max_primary>4</max_primary> <ext_possible>true</ext_possible> <max_logical>255</max_logical> <udev_path>pci-0000:04:00.0-scsi-0:2:0:0</udev_path> <udev_id>scsi-3690b11c01e94a1001849db2b14812561</udev_id> <udev_id>wwn-0x690b11c01e94a1001849db2b14812561</udev_id> <partition> <name>sda1</name> <device>/dev/sda1</device> <size_k>112640000</size_k> <major>8</major> <minor>1</minor> <numeric>true</numeric> <number>1</number> <fs_type>ntfs-3g</fs_type> <fs_uuid>2C12F02612EFF32E</fs_uuid> <fs_label>Windows 7 x64</fs_label> <mount_by>id</mount_by> <region> <start>1</start> <length>133145</length> </region> <partition_type>primary</partition_type> <partition_id>7</partition_id> <boot_flag>true</boot_flag> </partition> </disk> -- 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 11

[Bug 798337] New: ntfs and fat filesystem corruption with windows 8 systems - ntfs-3g vfat state saved across shutdowns
by bugzilla_noreply＠novell.com 11 Feb '13

11 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=798337 https://bugzilla.novell.com/show_bug.cgi?id=798337#c0 Summary: ntfs and fat filesystem corruption with windows 8 systems - ntfs-3g vfat state saved across shutdowns Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: boris(a)steki.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 Windows 8 has new functionality called fastboot, which in background is some sort of hibernation and when in linux fs is changed it will corupt itself,patch already exist for ntfs-3g to disallow mount of given partitions if ntfs metadata matches version. we should look into incorporating said patch or maybe even change yast to check for windows version on windows partition(?). This info should be mentioned in release notes, so users are aware of potential issues. Reproducible: Always Steps to Reproduce: 1. boot windows, change files, shutdown 2. boot linux, change files on ntfs, shutdown 3. boot windows , file system corruption... Expected Results: no corruption A lot more info can be found at http://www.h-online.com/open/features/Linux-and-Windows-8-Fast-Startup-puts… -- 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 802749] New: GNOME crashes on 16bit graphics
by bugzilla_noreply＠novell.com 11 Feb '13

11 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=802749 https://bugzilla.novell.com/show_bug.cgi?id=802749#c0 Summary: GNOME crashes on 16bit graphics Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: All OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: bwiedemann(a)suse.com QAContact: qa-bugs(a)suse.de CC: cwh(a)suse.com Found By: System Test Blocker: --- because of bug 799216 (cairo (and possibly Mesa) problems with 24bit graphics) we switched KVM's cirrus KMS driver's default to 16bit but this now causes GNOME to crash on xterm and many other applications Message says "Oh no! Something has gone wrong" -- 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 4

[Bug 802870] New: Make Live-CD volume name string more indicative
by bugzilla_noreply＠novell.com 11 Feb '13

11 Feb '13

https://bugzilla.novell.com/show_bug.cgi?id=802870 https://bugzilla.novell.com/show_bug.cgi?id=802870#c0 Summary: Make Live-CD volume name string more indicative Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium AssignedTo: coolo(a)suse.com ReportedBy: badshah400(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 The Live-CD volume name string for RC1 LiveCD's are simply "CDROM". It should be made something more informative, such as "openSUSE-12.3-GNOME" etc. so that it can be identified in the file managers etc. without having to look at its contents. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 8