I seem to be having an issue as far as shutting down or rebooting my machine. My screen will go dim and then set there for an untold amount of time. I can still do some things on my desktop, but it still wont shutdown or reboot. Is there any way to reveal what program might be causing this issue.
Can this be easily fixed, or need I reinstall my latest clone.
Most often such problems are hardware related. But you did not seem to tell us much about your installation except for your problem desccription. So, we need to know:
PC Hardware Make & Brand (Include info on your Video Chipset like Intel, AMD or nVIDIA)
openSUSE Version & 32 or 64 bit
Desktop that is used (Like KDE or GNOME)
How long have you been using openSUSE?
Any other Linux distro’s that work OK for you on this PC?
What you can do, is create a new user, login as that user and see if the issue arises for that new user. If not, the root of the issue is in your /home/YOURUSERNAME. The next step would be finding out what’s blocking normal behaviour for the existing user.
I just did a clean install (NOT an upgrade) from 11.4 to 12.2 (that is, I reformatted the / partition and installed 12.2, 64 bit). Seemed to be OK and computer reboots fine (for example, after updating the kernel). But it won’t shut down.
I have tried by:
a) right clicking on the desktop, then clicking <leave> then clicking <turn off computer>
or
b) in a shell as root typing <init 0>.
In either case the pooter starts to go through the shutdown process. (I can watch the steps its going through by pressing <Esc> when the green SuSE screen appears.) But then it stops and displays the following: [481.168672 System Halted]
Please note that I do not know if those numbers are the same each time the shutdown process stalls – these were the ones I got when I tried to shut down the most recent time.
Computer has Athlon II X2 240 processor, Nvidia C77 Geforce 8200 (on board) chipset, Biostar GF8200M2+ motherboard, and 4 GB memory. This is NOT a dual boot – SuSE only using KDE…
Pooter worked just fine with SuSE 11.4 and never exhibited this shutdown problem.
One other point… When I tried to install 12.2 the process hung right at the start where 12.2 looks for SuSE partitions. I had to type <acpi=off> at the beginning of the process to get the installation to proceed.
Tell me about your hardware that is not shutting down. Did you do a full system update after the install was complete? Would consider loading a different Linux kernel version (like 3.8.3) to see if it helps?
Yes, complete update. To get the “right” packages I followed (as best I think I understood) the “switch to packman repository” primer that’s on this forum. But I know that something got screwed up in the process (conflicting repositories?) because some (certainly not all) of my videos have blue people using Kaffeine (not mplayer or smplayer, just kaffeine). It’s like that problem we had with flash a few months back. Well it’s back on my pooter but does not seem to be related to flash.
It’s also not limited to certain extensions. For example, some .mp4s will play fine and others will have blue people. Same with some other extensions – only some within any category play blue.
I tried downgrading flash but that did not help. I did load kaffeine/KDE and that got rid of the blue people but then kaffeine takes over one of the two processors and pegs it at 100%. Won’t let go unless I kill the process.
So there seems to be more than one issue here and I’m very tempted just to reinstall 12.2.
I know you and the other experts hate that as it doesn’t allow the finding of a solution, but I need to get this computer running properly soon. It is my work computer and my productivity now is almost at a stand-still.
Which hardware is not shutting down? I don’t know. The pooter itself won’t shut down. It stops as I’ve described with a set of numbers and “System halted.”
Load another kernel? That may be getting a bit advanced for me. I’m not knowledgeable enough to be trying things somewhat out of the ordinary.
I then updated my packman repositories to those you show from jabobs-university.de. (I had been using the single community packman repository available by default through YaST).
I was able to install all of the missing packages EXCEPT gstreamer-0_10-plugins-fluendo_mp3.
I keep getting a message that says:
gstreamer-0_10-plugins-fluendo_mp3-0.10.18-3.6x86_64 conflicts with gstreamer-0_10-fluendo-mp3 > 0.10.18 provided by gstreamer-0_10-fluendo-mp3-12-7.1.3.x86_64
I am offered two options:
a) deinstallation of gstreamer-0_10-fluendo-mp3-12-7.1.3x86_64
b) do not install gstreamer-0_10-plugins-fluendo_mp3.10.18-3.6x86_64
I do not know what to do at this point.
Please do note that after the “tweaks” noted above the videos that were playing blue people in kaffeine still do that. So unless resolving this final gstreamer issue rids me of the blue people I will take your suggestion and open my videos with smplayer.
(Now, if I can only get smplayer to open in something other than a minimized (really small) sized window. ;o)
Thanks, James. Appreciate your help and vast expertise. :o)
bosdad
And if you did install Totem, why not try viewing a movie trailer from the iTunes Web site here and tell me if it works: iTunes Movie Trailers
I normally ask just how many movie viewers do you need? That is because I have found vlc to do all I need and while people are not blue in Kaffeine, too many oddities exist in it. Kaffeine was written to use the xine sound backend but PulseAudio works with Gstreamer, the openSUSE default, and nothing looks like it is going back to xine ever. It may be a good time to switch over.
When I click on one of the trailers at the iTunes website I get blue people.
If I save that trailer to my desktop and click it Kaffeine launches and I do NOT get blue people. Things look fine.
If I open that trailer with Totem it plays fine – no blue people.
I am not married to Kaffeine. In fact I use smplayer on my laptop and it’s great.
However, if I use smplayer on the desktop it opens in a very small window and I am at a loss on how to get it to open every time in a larger window the size of my choice.
I can set the consistent size of opening windows for everything except smplayer it seems.
Thx.
bosdad
>
> jdmcdaniel3;2537618 Wrote:
>> Tell me about your hardware that is not shutting down. Did you do a
>> full system update after the install was complete? Would consider
>> loading a different Linux kernel version (like 3.8.3) to see if it
>> helps?
>>
>> Thank You,
>
> Yes, complete update. To get the “right” packages I followed (as best
> I think I understood) the “switch to packman repository” primer that’s
> on this forum. But I know that something got screwed up in the process
> (conflicting repositories?) because some (certainly not all) of my
> videos have blue people using Kaffeine (not mplayer or smplayer, just
> kaffeine). It’s like that problem we had with flash a few months back.
> Well it’s back on my pooter but does not seem to be related to flash.
>
> It’s also not limited to certain extensions. For example, some .mp4s
> will play fine and others will have blue people. Same with some other
> extensions – only some within any category play blue.
>
> I tried downgrading flash but that did not help. I did load
> kaffeine/KDE and that got rid of the blue people but then kaffeine
> takes over one of the two processors and pegs it at 100%. Won’t let go
> unless I kill the process.
>
> So there seems to be more than one issue here and I’m very tempted
> just to reinstall 12.2.
>
> I know you and the other experts hate that as it doesn’t allow the
> finding of a solution, but I need to get this computer running
> properly soon. It is my work computer and my productivity now is
> almost at a stand-still.
>
> Which hardware is not shutting down? I don’t know. The pooter itself
> won’t shut down. It stops as I’ve described with a set of numbers and
> “System halted.”
>
> Load another kernel? That may be getting a bit advanced for me. I’m
> not knowledgeable enough to be trying things somewhat out of the
> ordinary.
>
> Thx.
> bosdad
>
I’m having same issue except mine stops at Power Down.
Manually I have tried both su -, sudo and as user who is authorized.
My install was clean also. It works every once in a while.