December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 856478] New: gvim requires krb5-mini which conflicts with krb
by bugzilla_noreply＠novell.com 23 Dec '13

23 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=856478 https://bugzilla.novell.com/show_bug.cgi?id=856478#c0 Summary: gvim requires krb5-mini which conflicts with krb Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.28) Gecko/20120306 Firefox/3.6.28 Trying to rebuild vim, but it wants krb5-mini. I can't install that because it conflicts with already installed krb5. Shouldn't krb5 suffice for anything krb5-mini would? Reproducible: Always Steps to Reproduce: 1. 2. 3.build gvim and alrady have krb5 installed Actual Results: conflict -- cannot build Expected Results: no conflict Not being able to regenerate products is a major problem. So many products need to be reconfigured to be usable again after they've been suse-ized, roadblocks to prevent rebuilding if the user has the complete krb package installed are unnecessary obstacles. -- 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 856654] New: It is not possible to enable lircd --allow-simulate via sysconfig
by bugzilla_noreply＠novell.com 23 Dec '13

23 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=856654 https://bugzilla.novell.com/show_bug.cgi?id=856654#c0 Summary: It is not possible to enable lircd --allow-simulate via sysconfig Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bpoirier(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Although /etc/sysconfig/lirc does allow setting LIRCD_LISTENPORT, it does not allow setting an option that results in passing "--allow-simulate" to lircd. I would like to pass this option so that I can send remote commands to lirc via the network from an app running on my phone. Currently, I've worked around the issue by modifying the init script but that got overwritten when the package was upgraded, which prompted me to do the modification again and open this request. -- 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

Your Bugzilla bug list needs attention.
by bugzilla_noreply＠novell.com 22 Dec '13

22 Dec '13

[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://bugzilla.novell.com/) that require attention. All of these bugs are in the NEW orREOPENED state, and have not been touched in 7 days or more. You need to take a look at them, and decide on an initial action. Generally, this means one of three things: (1) You decide this bug is really quick to deal with (like, it's INVALID), and so you get rid of it immediately. (2) You decide the bug doesn't belong to you, and you reassign it to someone else. (Hint: if you don't know who to reassign it to, make sure that the Component field seems reasonable, and then use the "Reassign bug to default assignee of selected component" option.) (3) You decide the bug belongs to you, but you can't solve it this moment. Just use the "Accept bug" command. To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark it if you like!): http://bugzilla.novell.com/buglist.cgi?bug_status=NEW&bug_status=REOPENED&a… Or, you can use the general query page, at http://bugzilla.novell.com/query.cgi Appended below are the individual URLs to get to all of your NEW bugs that haven't been touched for 7 days or more. You will get this message once a week until you've dealt with these bugs! RepoType: "staticlinks" doesn't create links for tbz images -> http://bugzilla.novell.com/show_bug.cgi?id=853882

1 0

[Bug 856657] New: X11 stops forwarding after a while
by bugzilla_noreply＠novell.com 22 Dec '13

22 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=856657 https://bugzilla.novell.com/show_bug.cgi?id=856657#c0 Summary: X11 stops forwarding after a while Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jamesrome(a)alum.mit.edu QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1726.0 Safari/537.36 OPR/20.0.1353.0 (Edition Developer) Using 64-bit 13.1 remotely, I ssh in from a Mavericks Mac and do: jar@jarfx:~> su - Password: jarfx:~ # yast2 & [1] 2753 This works. Then (the next morning) I made some ssl certificates, and tried to edit the configuration: jarfx:/etc/apache2 # nedit /etc/sysconfig/apache2 & [2] 14842 jarfx:/etc/apache2 # NEdit: Can't open display jarfx:/etc/apache2 # exit logout [1]+ Exit 127 yast2 jar@jarfx:~> xterm & [1] 14922 jar@jarfx:~> xterm: Xt error: Can't open display: localhost:10.0 This happens all the time after a sufficient delay. Exiting su and redoing su - does not fix it. I have to log out and start a new session. Reproducible: Always Steps to Reproduce: 1. do su - to get root 2. Run an X11 program, which works 3. Wait some hours. 4. Try do launch an X11 program as root. It fails. 5. Exit root 6. Try to launch an X11 program as myself. It fails Actual Results: See details. X11 forwarding stops Expected Results: X11 should work -- 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 789579] New: The selection of the screen size in the first screen (F2) is not copied in the generated grub2 config
by bugzilla_noreply＠novell.com 21 Dec '13

21 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=789579 https://bugzilla.novell.com/show_bug.cgi?id=789579#c0 Summary: The selection of the screen size in the first screen (F2) is not copied in the generated grub2 config Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 After booting the iso DVD file of 12.3 M1 one can select a few screen sizes. I choose 1152 x 864 and used the default to use GRUB2 as the bootloader. After generating the system and doing the first boot of the ready system I do not get this size, but a much smaller size as the screen. Selecting in YaST System -> Bootloader and pressing the button Bootloader options it appears that the field VGA modus is empty. After selecting mode 0x34b (1152 x 864 24 bits) one gets the requested size of screen after booting the system. Reproducible: Always Steps to Reproduce: 1. Select a size in the first screen 2. Inspect the value in the mentioned field 3. Actual Results: Mentioned field is empty Expected Results: Field should contain the selected VGA value -- 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 856596] New: Missing package "nvidia-settings" on packman repo for 13.1
by bugzilla_noreply＠novell.com 20 Dec '13

20 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=856596 https://bugzilla.novell.com/show_bug.cgi?id=856596#c0 Summary: Missing package "nvidia-settings" on packman repo for 13.1 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: X11 3rd Party Driver AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: patrick.feucht(a)kabelbw.de QAContact: sndirsch(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:26.0) Gecko/20100101 Firefox/26.0 I wanted to upgrade from 12.3 => 13.1. I have choosen the packman repo and after that I saw that the package "nvidia-settings" is not available. Reproducible: Always Steps to Reproduce: 1.Update from 12.3 => 13.1 via network-CD. 2.Choose/activate packman-repo 3.No package "nvidia-settings" available Actual Results: I have aborted the upgrade. Expected Results: Package "Nvidia-settings" must be available in Packman-Repo 13.1. -- 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 848918] New: Unable to use emulated network devices in Xen HVM guests via libvirt
by bugzilla_noreply＠novell.com 20 Dec '13

20 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=848918 https://bugzilla.novell.com/show_bug.cgi?id=848918#c0 Summary: Unable to use emulated network devices in Xen HVM guests via libvirt Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jfehlig(a)suse.com ReportedBy: jfehlig(a)suse.com QAContact: jdouglas(a)suse.com CC: carnold(a)suse.com Found By: Development Blocker: --- When specifying an emulated network device (e.g. rtl8139 or e1000) for a Xen HVM guest via libvirt, the guest fails to start with 2013-11-04 18:22:01.945+0000: 4570: error : libxlVmStart:1045 : internal error: libxenlight failed to create new domain 'opensuse13' libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge add [4830] exited with error status 1 -- 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 14

[Bug 753744] New: dolphin switch to "all desktops" when opening fish:// remote server
by bugzilla_noreply＠novell.com 20 Dec '13

20 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=753744 https://bugzilla.novell.com/show_bug.cgi?id=753744#c0 Summary: dolphin switch to "all desktops" when opening fish:// remote server Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: jdd(a)dodin.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 I have 8 desktops and use to open dolphint in the lower left one, #5 I use dolphin to upload images to my photo gallery using fish:// and splitting dolphin in two pannels. Very often (but not always) I notice that after doing so I have dolphin stuck on all the desktops. I have to right click on the top of the window and choose "desktop 5" to remove this. Reproducible: Sometimes Steps to Reproduce: 1.open dolphin 2.split screen (two pannels) 3.clic on the left pannel where I have a link to root@myserver 4.the wallet opens to ask for passwd 5.I connect and begin to work 6.I notice dolphin is now visible in alls the 8 desktops Expected Results: dolphin should still be only on the origianl desktop No idea of what I can give as info to help :-( -- 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 799471] New: postgresql: issues with using postgresql 9.2.2.
by bugzilla_noreply＠novell.com 20 Dec '13

20 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=799471 https://bugzilla.novell.com/show_bug.cgi?id=799471#c0 Summary: postgresql: issues with using postgresql 9.2.2. Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 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: john4deidre(a)clear.net.nz 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 in the pg_hba.conf i made the following changes: 1. with host i changed both uncommented host all all ident (to md5) ipv4 and i did the same with the ipv6 as well. in the postgres.conf i made the following changes: 1. uncommented the port=5432 i have tried to set postgresql to start at start up and it won't do so giving an error of 'postgresql: failed to start service' or something similar to this. Reproducible: Always Steps to Reproduce: 1. install postgresql with server as well 2. use the settings i have provided 3. try and run runlevel and try to start postgresql as a service and save your changes. Actual Results: does not start service Expected Results: to start the service and save so it will run each time on start up. -- 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 37

[Bug 852132] New: KillUserProcesses=yes does not work at least with KillOnlyUsers
by bugzilla_noreply＠novell.com 20 Dec '13

20 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=852132 https://bugzilla.novell.com/show_bug.cgi?id=852132#c0 Summary: KillUserProcesses=yes does not work at least with KillOnlyUsers Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: systemd-maintainers(a)suse.de ReportedBy: werner(a)suse.com QAContact: qa-bugs(a)suse.de CC: werner(a)suse.com, fcrozat(a)suse.com Found By: Development Blocker: --- To see this /suse/werner> grep ^Kill /etc/systemd/logind.conf KillUserProcesses=yes KillOnlyUsers=linux after login, setting up a `batch job' with simply with sleep, and a simply logout: /suse/werner> ps aux | grep ^linux linux 3763 0.0 0.1 38096 2280 ? Ss 12:08 0:00 /usr/lib/systemd/systemd --user linux 3764 0.0 0.0 72912 1852 ? S 12:08 0:00 (sd-pam) linux 3816 0.0 0.0 4520 572 ? S 12:08 0:00 sleep 1000 .. I've rebooted the system before testing this to be sure that systemd-logind has read its corect configuration. This bug is related to bnc #849870 I'm asking me if upstream has something like QA managment :( -- 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