Please report bugs

English Install/Boot/Login
#1

The check-in deadline for RC2 is Friday, Oct. 8. Any bugs that are not reported
soon will be in the 12.1 release!

#2

Nov.8?? Exept for the Ncurses and qt yast install software bugs in the installation DVD I haven’t seen any bugs lol!

#3

I am guessing that you mean Oct 28. At least that’s a Friday, ends in “8”, has not passed already, and is before the announced release date for rc2.

Apart from the DVD installer problems (which others have reported), the bugs I have been following have been there since Beta1 or earlier. They are all reported, and I have updated reports where there was a change with rc1.

I will report another one soon, though it probably goes back to 11.3 or earlier and is low priority.

#4

Using XFCE main menu

Settings-> Prefetences -> Bluetooth
fails to launch “gnome-control-center bluetooth”

Also bluetooth icon won’t show in notification area (testen under Virtualbox with USB support)
so i guess BT is not working

#5

On 10/25/2011 01:56 PM, nrickert wrote:
>
> lwfinger;2397263 Wrote:
>> The check-in deadline for RC2 is Friday, Oct. 8.
> I am guessing that you mean Oct 28. At least that’s a Friday, ends in
> “8”, has not passed already, and is before the announced release date
> for rc2.
>
> Apart from the DVD installer problems (which others have reported), the
> bugs I have been following have been there since Beta1 or earlier. They
> are all reported, and I have updated reports where there was a change
> with rc1.
>
> I will report another one soon, though it probably goes back to 11.3 or
> earlier and is low priority.

Yes, I meant this coming Friday, Oct 28.

#6

On 10/25/2011 03:56 PM, sobrus wrote:
>
> Using XFCE main menu
>
> Settings-> Prefetences -> Bluetooth
> fails to launch “gnome-control-center bluetooth”
>
> Also bluetooth icon won’t show in notification area (testen under
> Virtualbox with USB support)
> so i guess BT is not working

Is the BT hardware USB-based? If not, VB will not see it.

Reporting it here WILL NOT get it fixed. You need to file a BUG report.

#7

For any who don’t know, there is guidance here for raising bug reports: openSUSE:Submitting bug reports - openSUSE … and you can use your openSUSE forum username and password when logging on to bugzilla to raise the bug report.

#8

October 8th??? Alright, guys, give me back my TARDIS! :stuck_out_tongue:

#9

We are expecting the release of 12.1 RC2 on Thursday, Nov. 3rd.

#10

Sorry to bother in this thread, but I just went to report this bug, and I can’t see whether it has already been reported or not; when I tried to go ahead and report it, I couldn’t find openSuSE 12.1 in the operating system list for the bug report, even though it was in the preliminary list at the top of that page. Anyway, I suspect that others must surely have already seen and reported this:

Running 12.1 RC-1 on a variety of notebooks and netbooks, every one of them has problems with connecting to a wireless network. If I have no wireless connection defined or configured, all available networks are displayed. If I then select one and configure it to connect automatically, then reboot, about 80% of the time it does not connect, and if I look at the list of available wireless networks, it is not displayed? If I take off the auto-connect attribute, then reboot, it is displayed in the list again and I can connect manually, still using the stored key.

This problem occurs on all six of the notebooks and netbooks I have tried, which have a variety of Broadcom, Atheros and Ralink wireless adapters. It does NOT happen with various other Linux distributions on those same notebooks and netbooks.

If this is not a known problem, I would be happy to report it - if I could only figure out how to select openSuSE 12.1 in the report!

jw

#11

I spotted 2:

#12

j_a_watson, openSUSE 12.1 is selected in the Product field, not in the OS.

As for the topic, I reported a 100% reproducible kernel panic two days ago :slight_smile: https://bugzilla.novell.com/show_bug.cgi?id=726194

#13

I have no had this problem.

Can you indicate whether you are using KDE or Gnome or other desktop. There are two different applets, depending on your desktop.

#14

A second reply to j_a_watson.

On second thoughts, yes I have seen this “bug”, except that it was a user error. Once I recognized my mistake, I move on and forgot about it. However, I did briefly mention it in a guide to setting up network manager in KDE.

Here’s what I think you did:

1: You are using KDE;
2: In the KDE applet, you clicked on “ADD” to add a new wireless network.
3: You were prompted for a choice between “wireless” and “shared”. You chose “shared”.

That last step was the mistake. You must choose “wireless” at that point. If my analysis is correct, then delete the connections that you have defined, then define them again choosing “wireless”. When you choose “shared”, you inadvertently setup your connection as an ad hoc network, and that’s why things go wrong.

#15

First, thanks to all who took the time to read, reply and try to help. I genuinely appreciate it.

I am using KDE, sorry, I should have mentioned that.

I did not make the mistake mentioned in the last post above. What I did was boot 12.1 RC1, then click on the network applet in the panel. It gave me a list of available wireless networks, and I clicked on mine in the list. That brought up the “manage networks” window, where I could enter the wireless key and select that I wanted to connect to this network automatically. When I finished that, the “KDE Wallet” application (sorry, name is probably not quite right) came up, and THIS might be where I am going wrong (or at least different from most). I have had a long-standing dislike and distrust for these kinds of “wallet” applications, combined with the experience that they tend to disappear or change radically between releases. So I simply clicked “Finish” without entering a Wallet password. The network manager has always noticed that in previous releases, and it brings back up the “simple” network manager where I can again enter the network key and it is then stored - probably in plain text, but I don’t care. However this time the network manager didn’t come back. Being determined, and stubborn, and knowing what “should have happened”, I went back to the network manager manually again, and entered the network key there.

After all of that, if I logout or reboot, the wireless network seldom connects automatically (less than 25% of the time), and strangely, when it doesn’t connect if I click on the network manager applet, the list of available networks comes up but my wireless network is not listed - so I can’t even “give it a kick” to get it to connect.

I suppose what I should do is go back and do it all again, and go ahead and give the Wallet manager thing a password to make it happy. Maybe that would work - and maybe that is why so few others have seen this problem.

Thanks again for the help. I really do hope that this is just a matter of me doing something wrong, or taking an unusual path, so that it will not be a problem in the final release.

jw

#16

I have had a problem when upgrading to RC1 using zypper dup. After the upgrade I get only a shell text login. To get the graphical (KDE) screen I have to log in as root, then init 5 etc. After log out and shut down a restart still comes up in text mode.

I am either doing something stupid (not impossible!) or there is a bug.

Please can anyone suggest how I can get the graphics log in after boot without logging in as root?

Thank you in advance.

#17

My hiccups so far are:-

  1. kscd crashes everytime i use it

  2. i can’t import my address book with kmail (again it crashes)

  3. using webkit as the engine for konqueror crashes quite often

#18

Do you have an external hard drive with a mount point that is not attached? if so attach it or remove the mount point

#19

Thank you Dale. I do not have an external drive - my machine is a Toshiba laptop that dual boots with openSUSE 11.3. The problem is associated with the actions that occur during boot after Grub.

#20

Are you being thrown into a rescue shell?
Maybe the text just before you are asked for the root password will give a hint