opensuse 11.2 RC1 bugs...

2 bugs. Amsn failes to start with a TkCimage loading failure.

2on and more importand. When adding files in desktop they do not appear unless i refresh it manually…

Issues I have found so far

1 - Volume Control buttons do not work on my laptop

2 - On login screen pull down boxes not displaying data properly

3 - Laptop’s internal mic does not appear to be recognized. Was hoping this might get fixed in 11.2. Have had this issue with prior releases as well.

4 - KDE network manager would not connect to my wireless. Admittedly I have not done much to troubleshoot it yet. Was able to jump over to gnome and it just worked.

All in all I am liking the looks of this release. So far in gnome I have not found any thing that prevents me from continuing to use this release.

same here (although i use kde4) - will carry on using the rc as my main p/c until the formal release next month

On 10/16/2009 09:36 AM, hamiltdl wrote:
>
> Issues I have found so far
>
> 1 - Volume Control buttons do not work on my laptop
>
> 2 - On login screen pull down boxes not displaying data properly
>
> 3 - Laptop’s internal mic does not appear to be recognized. Was hoping
> this might get fixed in 11.2. Have had this issue with prior releases
> as well.
>
> 4 - KDE network manager would not connect to my wireless. Admittedly I
> have not done much to troubleshoot it yet. Was able to jump over to
> gnome and it just worked.
>
> All in all I am liking the looks of this release. So far in gnome I
> have not found any thing that prevents me from continuing to use this
> release.

I hope you have files proper bug reports. The developeers do not read
this forum, and they will not be fixed unless properly reported.

Agreed! Same on my side, actually this was there in M8 (don’t for previous).

Have you logged a bug yet? If yes I will vote.

Yup, same old story not only with this forum.

People using unstable releases, explicitely marked for testing and complain in $FORUM, but in most cases you don’t find the respective bug reports (and nearly nobody links them if they exist).

Let me tell you a little story.

This is a little story about four people named Everybody, Somebody, Anybody, and Nobody.

There was an important job to be done and Everybody was sure that Somebody would do it.

Anybody could have done it, but Nobody did it.

Somebody got angry about that because it was Everybody’s job.

Everybody thought that Anybody could do it, but Nobody realized that Everybody wouldn’t do it.

It ended up that Everybody blamed Somebody when Nobody did what Anybody could have done.

I hope you get the point.

I had that problem in M8 but not RC1.

I plan on filing the bugs just have not had the chance yet to do it. No time to play at work. This evening I will start filing them.

Mics can be tricky to get working in Linux. Incredibly careful and precise attention is needed when setting up the mixer.

There is limited guidance here: Microphone - openSUSE

Key to that guidance is doing the mic test from a terminal with:

arecord -vv -fdat foo.wav

Further testing has shown the internal mic to work.

Congratulations.

The mic on our Dell Studio 1537 laptop gives my wife no end of grief under openSUSE-11.1. In order to help her out, I took two screen snapshots of the mixer configuration when the mic works. One for external mic. One for internal mic. Then I saved those snapshot’s on my wife’s desktop.

When she goes to use the Mic, she now has a reference/guide of a working configuration to compare with.

I know this will read like over kill to many, but of late it has saved me many a rant from her, when she has been unhappy with the Linux mic/mixer setup.

I thought it was not going to work with the same results as I have seen in Opensuse 11.1 based on the fact that there is not input levels displaying in yast like there should be. but when I went to test audacity I started changing my inputs and it started recording like it knew what it was doing. Tried with the generic sound recorder and that worked as well.

Tested this issue a little more and found that it does not work in gnome but works fine in KDE. The graphics that come up to show your volume levels were not as fancy as I would have expected based on the rest of the KDE system but at least it worked. Bug report has been filed Access Denied

Am 16.10.2009 14:36, schrieb hamiltdl:
>
> Issues I have found so far
> 4 - KDE network manager would not connect to my wireless. Admittedly I
> have not done much to troubleshoot it yet. Was able to jump over to
> gnome and it just worked.
>
regarding the network, I filed a bug
https://bugzilla.novell.com/show_bug.cgi?id=547916

for me, i had no chance of getting any network working with rc1 (now I
am back at M8).
This is my first bugreport, so feel free to correct it with some comments.

On 10/17/2009 09:42 AM, Marco wrote:
> regarding the network, I filed a bug
> https://bugzilla.novell.com/show_bug.cgi?id=547916
>
> for me, i had no chance of getting any network working with rc1 (now I
> am back at M8).
> This is my first bugreport, so feel free to correct it with some comments.

I suspect that your problem was the “resolv.conf” problem. If you had
deleted /etc/resolv.conf, your network would have worked.

Am 17.10.2009 15:58, schrieb Larry Finger:
> On 10/17/2009 09:42 AM, Marco wrote:
>> regarding the network, I filed a bug
>> https://bugzilla.novell.com/show_bug.cgi?id=547916
>>
>> for me, i had no chance of getting any network working with rc1 (now I
>> am back at M8).
>> This is my first bugreport, so feel free to correct it with some comments.
>
> I suspect that your problem was the “resolv.conf” problem. If you had
> deleted /etc/resolv.conf, your network would have worked.

I will try that right away and update the bugreport if it works

Are you even able to get it to connect to a wireless network? My issue is it will not even make an attempt to connect. So I never get to the point where the resolv.conf issue comes into play. Will do some more troubleshooting and pull some logs for the Bug