December 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 793541] New: CodeAnalyst has been failing to build in Factory for a long time
by bugzilla_noreply＠novell.com 12 Dec '12

12 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=793541 https://bugzilla.novell.com/show_bug.cgi?id=793541#c0 Summary: CodeAnalyst has been failing to build in Factory for a long time Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: tonyj(a)suse.com ReportedBy: christian.morales.vega(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: --- CodeAnalyst has been failing to build in Factory for a long time By the way, the metadata of the package says: <person userid="janblunck" role="maintainer"/> <person userid="jones_tony" role="maintainer"/> <person userid="suravee" role="maintainer"/> <person userid="suravee" role="bugowner"/> I couldn't assign it to suravee since bugzilla didn't recognise the email. The latest version is 3.4 and we are packaging 2.12.3. And in general from the Changelog it doesn't look like there is any real main maintainer. Could you please clean the metadata with the correct, updated information. Or drop the package if nobody is really maintaining it? -- 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 7

[Bug 793550] New: oprofile has been failing to build in Factory for a long time
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=793550 https://bugzilla.novell.com/show_bug.cgi?id=793550#c0 Summary: oprofile has been failing to build in Factory for a long time Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: tonyj(a)suse.com ReportedBy: christian.morales.vega(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: --- oprofile has been failing to build in Factory for a long time -- 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 462467] inkscape fails to open .cdr files
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=462467 https://bugzilla.novell.com/show_bug.cgi?id=462467#c9 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P5 - None CC| |dimstar(a)opensuse.org Component|GNOME |GNOME Version|Final |12.3 Milestone 1 Product|openSUSE 11.1 |openSUSE Factory --- Comment #9 from Dominique Leuenberger <dimstar(a)opensuse.org> 2012-12-11 17:21:19 UTC --- As uniconvertor is still not part of the distribution, I very much expect this bug to still exist... moving to openSUSE:Factory in an attempt to ever get a fix for this. -- 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 0

[Bug 779418] New: /usr/share/doc/packages/NetworkManager-vpnc/README is empty
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=779418 https://bugzilla.novell.com/show_bug.cgi?id=779418#c0 Summary: /usr/share/doc/packages/NetworkManager-vpnc/README is empty Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Network AssignedTo: os.gnome.maintainers(a)gmail.com ReportedBy: lmuelle(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: No The README file included with the NetworkManager-vpnc package at /usr/share/doc/packages/NetworkManager-vpnc/ is empty. The file should either not packaged or if it is required by which reason ever it should include the reason why it is included and point the curious reader to some documentation which might best be available on the system or somewhere in the wild internet. -- 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 626149] New: jhbuild should require or recommend "patch"
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

http://bugzilla.novell.com/show_bug.cgi?id=626149 http://bugzilla.novell.com/show_bug.cgi?id=626149#c0 Summary: jhbuild should require or recommend "patch" Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: i586 OS/Version: openSUSE 11.3 Status: NEW Severity: Minor Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: mwelinder(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 I installed jhbuild only to have it fail when patch was needed. The jhbuild package should recommend patch as it does git-core. 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 3

[Bug 752424] New: exit from su shell takes seconds
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=752424 https://bugzilla.novell.com/show_bug.cgi?id=752424#c0 Summary: exit from su shell takes seconds Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jslaby(a)suse.com QAContact: qa-bugs(a)suse.de CC: werner(a)suse.com, fcrozat(a)suse.com Found By: --- Blocker: --- $ su Password: # exit ...killed. <--- takes seconds to show up $ This is a regression. It is very disturbing when you want to close all your open shells on a desktop with ctrl+d held. It takes ages to do that. -- 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 30

[Bug 788756] New: iscan-free does not work with epson perfection 1650 scanner
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=788756 https://bugzilla.novell.com/show_bug.cgi?id=788756#c0 Summary: iscan-free does not work with epson perfection 1650 scanner Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: petr.m(a)seznam.cz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 iscan-free does not work with epson perfection 1650 scanner."No scanner was detected". I tried to install the iscan from avasys and it works. Driver epson from sane is also functionally suse:~ # lsusb Bus 004 Device 004: ID 04b8:0110 Seiko Epson Corp. Perfection 1650 Bus 004 Device 002: ID 0557:0204 ATEN International Co., Ltd Bus 005 Device 002: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller Bus 005 Device 003: ID 0aec:3260 Neodio Technologies Corp. 7-in-1 Card Reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub suse:~ # sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04b8 [EPSON], product=0x0110 [EPSON Scanner]) at libusb:004:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. suse:~ # scanimage -L device `epson2:libusb:004:004' is a Epson GT-8200 flatbed scanner device `epson:libusb:004:004' is a Epson GT-8200 flatbed scanner suse:~ # grep -v '^#' /etc/sane.d/dll.conf epson epson2 epkowa Reproducible: Always -- 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 20

[Bug 793829] New: /run/systemd/syslog.core Assignment outside of section. Ignoring.
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=793829 https://bugzilla.novell.com/show_bug.cgi?id=793829#c0 Summary: /run/systemd/syslog.core Assignment outside of section. Ignoring. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 I noticed the following couple of lines when browsing /var/log/messages: systemd[1]: [/run/systemd/syslog.core:3] Assignment outside of section. Ignoring. systemd[1]: [/run/systemd/syslog.core:4] Assignment outside of section. Ignoring. /run/systemd/syslog.core contains this: # Warning: Do not edit as this file has been and will be autogenerated # by /lib/systemd/system-generators/syslog-service-generator Requires=network.target After=network.target [Service] Type=forking PIDFile=/var/run/syslog-ng.pid Sockets=syslog.socket StandardOutput=null ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service ExecStartPre=-/var/run/syslog-ng/addsockets ExecStart=/sbin/syslog-ng ExecReload=/sbin/killproc -p /var/run/syslog-ng.pid -HUP /sbin/syslog-ng Reproducible: Always -- 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 779042] New: Unable to increase screen resolution
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=779042 https://bugzilla.novell.com/show_bug.cgi?id=779042#c0 Summary: Unable to increase screen resolution Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: X11 3rd Party Driver AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mike1264(a)btinternet.com QAContact: sndirsch(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) Following installation there is a screen resolution problem. I have installed to a Sony Vaio Desktop VGC - JS1E machine with an Intel(R) G45/G43 Express Chipset. The standard screen resolution for this machine is 1680x1050. Following installation of openSuse 12.2 (as in previous versions) an ugly monitor display is created with wide areas of the screen greyed out and unusable. I understand 12.2 uses xf86-video-intel 2.20.0 which does not overcome this problem. Reproducible: Always Steps to Reproduce: 1. Install OpenSuse 2. Load OpenSuse 3. Actual Results: Screen resolution locked on 1280x700 Expected Results: Screen resolution of 1680x1050 I have tried installing version 12.2 previosuly with the same results. -- 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 793231] New: GIMP "save as" no longer allows usual image formats (PNG JPEG etc.) other than XCF; must use "Export"
by bugzilla_noreply＠novell.com 11 Dec '12

11 Dec '12

https://bugzilla.novell.com/show_bug.cgi?id=793231 https://bugzilla.novell.com/show_bug.cgi?id=793231#c0 Summary: GIMP "save as" no longer allows usual image formats (PNG JPEG etc.) other than XCF; must use "Export" Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: me(a)kalenz.eu 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 It used to be possible to open an image file (e.g.: JPEG, PNG) in GIMP, edit, then "save" (to the same name, in the same format), or "save as" (new name, same format, or new format). At present (GIMP 2.8.0 on KDE4) it is no longer possible to handle the usual image formats, such as JPEG and PNG, through the "Save" and "Save As" functions. These functions only allow the XCF format. To save an image as JPEG or PNG, the "Export" function must be used, even if saving in the same format as the originally opened image. When closing the image, even if it has just been "exported", the warning dialogue appears: "IMG_0001 has not been saved. All modifications of the past 3 minutes will be lost! Close without saving?" which is complete nonsense because the image was just "exported" so there is no loss of data on closing (other than restrictions imposed by the chosen output format). It seems clear that this is an upstream decision to "encourage" (/coerce?) users to use the XCF format. Which, let's be honest, nobody uses. In applications like web design and photography, GIMP is used routinely to edit JPEG and PNG files, which are the predominant formats for lossy and lossless image data, respectively. The insistence on "Export" and the nagging dialogues seriously reduce productivity, and increase accidental mis-saving or non-saving of images. Regardless of upstream choices, I strongly feel that openSUSE should choose for maximum flexibility, freedom of choice, and productivity (which I believe is the general spirit, anyway). As such, I suggest you return to the previous style, where the "Save As" dialogue allowed all supported image formats, and the "Save" function simply overwrites the same file in the same format. Reproducible: Always -- 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 5