November 2011 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 728646] New: GNOME Shell crashed with fglrx driver (GNOME 3.2 / openSUSE 12.1 RC2 / AMD Catalyst Beta 11.11)
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=728646 https://bugzilla.novell.com/show_bug.cgi?id=728646#c0 Summary: GNOME Shell crashed with fglrx driver (GNOME 3.2 / openSUSE 12.1 RC2 / AMD Catalyst Beta 11.11) Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: freespacer(a)gmx.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Ubuntu/10.04 Chromium/15.0.874.106 Chrome/15.0.874.106 Safari/535.2 Hi, I test the beta of AMD Catalyst 11.11 (fglrx) with GNOME 3.2 (openSUSE 12.1 RC2). I am the officially packaging script maintainer for AMD installer and beta tester. I am in constant contact with AMD. AMD (and me) have tested this driver with GNOME 3.2 and openSUSE 12.1 RC1. It works. But now with openSUSE 12.1 RC2, it does not work anymore and that is really annoying. The gnome shell crashed immediately after booting. AMD assumed that a regression patch was trigger the error. The GNOME maintainer should check this. # gnome-shell --sync --replace (gnome-shell:2383): Gdk-WARNING **: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'GLXBadRenderRequest'. (Details: serial 181 error_code 153 request_code 137 minor_code 1) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) There is no further information in /var/log/Xorg.0.log. I try to debug this with gdb. But I get also no information. That is really crazy. How we can fix this in GNOME 3.2 (openSUSE 12.1 RC2) asap? Reproducible: Always Steps to Reproduce: 1. Install openSUSE 12.1 RC2 with GNOME 3.2 2. Install fglrx driver 3. Reboot the computer Actual Results: GNOME Shell crashed Expected Results: GNOME Shell should run -- 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 28

[Bug 731451] New: After update, touchpad don't works
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=731451 https://bugzilla.novell.com/show_bug.cgi?id=731451#c0 Summary: After update, touchpad don't works Classification: openSUSE Product: openSUSE 12.1 Version: Final 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: rauhmaru(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I updated my notebook cp -rfv /etc/zypp/repos.d /etc/zypp/repos.d.old sed -i 's/11.4/12.1/g' /etc/zypp/repos.d/* zypper ref && zypper dup But, after the update, my touchpad don't works. Reproducible: Always Steps to Reproduce: 1. sed -i 's/11.4/12.1/g' /etc/zypp/repos.d/* 2. zypper ref && zypper dup 3. And touchpad fails Actual Results: Touchpad don't work Expected Results: Touchpad works -- 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 6

[Bug 730135] New: at boot time the wallpaper is a distorted picture, instaed of normal Wallpaper
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=730135 https://bugzilla.novell.com/show_bug.cgi?id=730135#c0 Summary: at boot time the wallpaper is a distorted picture, instaed of normal Wallpaper Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: pierre.5933(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1 at boot time the wallpaper is a distorted picture. This image comes in part from a previous assignment with an operating system. This O S may be the one which I use in routine work, for exemple suse 11.4 annd a windows of libre office , Chrome or someting else! I am obliged to go to systemsetting >>>Background>>>>walpaper and select my wall paper Some times it is a distorded picture and I cannot recognize from where it is comming I used the same swap for all my Operating systems Reproducible: Sometimes Steps to Reproduce: 1.stop en OS 2.restart 3.the first wall paper is generaly a strange picture Expected Results: to get immediatly the correct wall paper -- 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

[Bug 728530] New: Wi-Fi Drops Out Periodically in openSUSE 12.1 RC 2 (Gnome)
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=728530 https://bugzilla.novell.com/show_bug.cgi?id=728530#c0 Summary: Wi-Fi Drops Out Periodically in openSUSE 12.1 RC 2 (Gnome) Classification: openSUSE Product: openSUSE 12.1 Version: RC 2 Platform: PC OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: matty.fong(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 After a while of general use, wi-fi seems to stop transferring data between computer and router. Thought it could have been an ISP issue but even access to the router's IP was cut off. Connectivity seems to resolve itself but then cuts out again. Turning off the computer's wi-fi and turning it on again seems to resolve it also temporarily. Reproducible: Didn't try Steps to Reproduce: 1.Just seems to happen randomly 2.In fact, it just happened as I tried to submit this 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 13

[Bug 731559] New: metacity login makes controlls unusable - trap with autologin and access to last session
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=731559 https://bugzilla.novell.com/show_bug.cgi?id=731559#c0 Summary: metacity login makes controlls unusable - trap with autologin and access to last session Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: melchiaros(a)aol.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 I know that Mutter is the actual windowmanager for GNOME, but I have the option on login screen to access metacity. I´ve done this and it is a trap when you have autologin enabled. The login work, but in metacity I have no mouse no keyboard and also no access to shell. -> bad think. A newstart of the system bring me again to metacity(last desktop is accessed by default), because I had automatic login enabled(again without controlls=. It was necessary to start the system again and in shell mode to edit DISPLAYMANAGER_AUTOLOGON in etc/sysconfig to get the system back to another desktop(KDE with controls). Reproducible: Always Steps to Reproduce: 1.Install openSUSE12.1 with autologin 2.switch from a kde session to a metacity session -> see that you have no keyboard or mouse 3.make a hard reboot of the system 4.see that you access metacity automatically(because of autologin and last session access) again without keyboard and mouse. Expected Results: What I expect is to bring metacity in a state in which you have mouse and keyboard or to dismiss the metacity option at the login screen. What it is in the moment is to dangerous. When you not know how to get out of the trap I described you a near by to make a new install or try with rescue. I was surprised to see metacity in the options of the login screen. I thought that metacity was the window manager of GNOME2 and not a stand alone thing. -- 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

[Bug 728598] New: gnome-shell-extension-dock broken in factory and RC 2, SOLUTION/FIX!
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=728598 https://bugzilla.novell.com/show_bug.cgi?id=728598#c0 Summary: gnome-shell-extension-dock broken in factory and RC 2, SOLUTION/FIX! Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: All OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: smartdumbguy22(a)yahoo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.106 Safari/535.2 package gnome-shell-extension-dock GNOME shell extension: Dock is broken in openSUSE:Factory & RC 1, RC 2,+. Shell Extension: Dock, Fails to load due to incompatibility with current GNOME Version. (Fails with any gnome-shell > 3.2.0) gnome-shell version = 3.2.1 SOLUTION/FIX: There is a typo in the file in /usr/share/gnome-shell/extensions/dock(a)gnome-shell.extensions.gnome.org/metadata.json - "shell-version": [ "3.2.0" ], + "shell-version": [ "3.2.0", "3.2" ], The above change adding "3.2", changes the metadata.json for the Dock extension to the same configuration as other working extensions. All other extensions are already configured this way. Reproducible: Always Steps to Reproduce: 1. zypper install gnome-shell-extension-dock 2. enable extension with "Advanced Settings" 3. Alt+F2 (in GNOME); lg [enter]; view Errors tab Actual Results: 1. zypper install gnome-shell-extension-dock 2. enable extension with "Advanced Settings" 3. Alt+F2 (in GNOME); lg [enter]; view Errors tab Extension fails to load due to incompatibility with current GNOME-Shell version. Expected Results: Extension should have loaded fine. SOLUTION/FIX: Correct version string in gnome-shell-extension-dock installed file /usr/share/gnome-shell/extensions/dock(a)gnome-shell.extensions.gnome.org/metadata.json - "shell-version": [ "3.2.0" ], + "shell-version": [ "3.2.0", "3.2" ], -- 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 18

[Bug 634578] New: Secure file permissions prevent shutdown due to overheating
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=634578 https://bugzilla.novell.com/show_bug.cgi?id=634578#c0 Summary: Secure file permissions prevent shutdown due to overheating Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: martin(a)etainable.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b4) Gecko/20100817 SUSE/4.0b-13.1 Firefox/4.0b4 Changed file permissions from "easy" to "secure" on a Lenovo W500 laptop. This makes power management commands privileged. In gnome when you start it asks for root to enable drive power-down. Key issue is if you walk away and machine is running in high CPU state and can start to overheat. Machine will not shut down on a APCI temperature event as it is awaiting input. (I am working "why is it overheating" separately.) For system safety, system should be able to shut itself down to maintain integrity. Would like to know what to fix so system can shutdown for safety to resolve this. Reproducible: Always Steps to Reproduce: 1.enable secure file permissions 2.let "tracker" run for a few hours in a new gnome user (or any other behavior that causes system to stay in high CPU state in powertop) 3.system will get hot 4. Gnome dialog will state waiting on user input before shutting down... Actual Results: system gets hot and will wait until it fails before shutting down. Expected Results: Would like it to shutdown for safety. -- 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 623732] New: "Automatic Download Printer Driver" not works when plug the printers usb cable.
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=623732 http://bugzilla.novell.com/show_bug.cgi?id=623732#c0 Summary: "Automatic Download Printer Driver" not works when plug the printers usb cable. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: kota.seki(a)avasys.jp QAContact: jsmeix(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; GTB6.5; NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E) * I reported same bug information at https://bugzilla.redhat.com/show_bug.cgi?id=616281 The system-config-printer supported "Automatic Download Printer Driver". (When Printer USB cable plugs to the PC, then printer driver is downloaded from internet and installed it) But when I try the above, printer driver was not downloaded. (I use GNOME desktop) Reproducible: Always Steps to Reproduce: 1. Edit the yum repository setting file. # vi /etc/yum.repos.d/lsb.repo [lsb-drivers] baseurl=http://linux.avasys.jp/drivers/lsb/Epson-inkjet/stable/RPMS enabled=1 gpgchecnk=1 2. Get and register the gpg key. # wget https://linux.avasys.jp/drivers/lsb/epson-inkjet/key/pubkey.asc # rpm --import pubkey.asc 3. Turn on the Printer and Plugs the Printer's USB cable to the PC. Actual Results: Printer Driver was not downloaded and installed. Expected Results: When printer is plugged, it should be download the driver. Then it will install. I tried to see system-config-printer's log. # system-config-printer --setup-printer='file:/tmp/printout' --devid='MFG:Epson;MDL:Stylus Photo TX800FW' --debug When I type this, then I found logs about "jockey". ... Asking Jockey to install drivers Got Jockey error: org.freedesktop.DBUS.Error.ServiceUnknown: The name com.ubuntu.DeviceDriver was not provided by any .service files ... -- 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 5

[Bug 661991] New: FreeBSD (0xA5) partitions appearing in nautilus and other applications open/save dialogs
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=661991 https://bugzilla.novell.com/show_bug.cgi?id=661991#c0 Summary: FreeBSD (0xA5) partitions appearing in nautilus and other applications open/save dialogs Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: hippolyte(a)shaw.ca QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101203 SUSE/3.6.13-0.2.1 Firefox/3.6.13 FreeBSD primary partitions are seen by udev as being from type "ufs" and usage "filesystem". As a consequence these partitions show up in nautilus filemanager and other applications' file dialogs under Linux. User defined udev rules intended to hide them either with ENV{ID_FS_TYPE}=="ufs",ENV{UDISKS_PRESENTATION_HIDE}="1" or ENV{UDISKS_PARTITION_TYPE}=="0xa5",ENV{UDISKS_PRESENTATION_HIDE}="1" have no effect. Neither does adding type 0xa5 to the list of partition types which desktops should not display in /lib/udev/rules.d/80-udisk.rules. Reproducible: Always Steps to Reproduce: start nautilus file browser or open/save file dialog of applications (such as the Gimp) under Gnome, Kde or Lxde on any sytem containing one or more FreeBSD primary partitions. Actual Results: The primary 0xA5 partition shows up as a filesystem. Expected Results: Since these partitons are containers for Unix slices and do not include a filesystem themselves, they are not mountables (just like the Linux extended partition) and should never appear anywhere in filemanagers or on the desktop or applications file dialogs. It doesn't occur while using XFCE or Icewn as window manager (!) It concerns all Linux distros with Gnome, KDE, LXDE. It can been easily solved by adding entries for FreeBSD partitions in /etc/fstab using the mountpoint "none" and the filesystem type "ignore". However this hack should not be necessary as such partitions should be ignored by default. -- 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 629961] New: no visual feedback of umount
by bugzilla_noreply＠novell.com 29 Sep '13

29 Sep '13

http://bugzilla.novell.com/show_bug.cgi?id=629961 http://bugzilla.novell.com/show_bug.cgi?id=629961#c0 Summary: no visual feedback of umount Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: sbrabec(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- In openSUSE 11.2 there was a visual feedback of umount progress. If it tool more than about a second, a pop-up appeared that informed me about umounting progress. In openSUSE 11.3 this feedback disappeared. How to reproduce: 1. Attach an USB flash disc 2. Write thousands of files into a large directory. 3. Disconnect the medium in Nautilus Actual behavior: - Icon disappears and nothing indicated write in progress. - Write continues in next few minutes. (sync hangs and LED on the device flashes, if there is one) Expected behavior: - Visual feedback: "Writing data to the device." Marking the bug as Critical: It causes data losses and medium corruption for LED-less flash dongles and SD/CF cards. -- 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 1