http://bugzilla.suse.com/show_bug.cgi?id=798308http://bugzilla.suse.com/show_bug.cgi?id=798308#c12
--- Comment #12 from Egbert Eich <eich(a)suse.com> ---
Maybe to word Alex' question a little more for a non-developer:
The monitor that doesn't light up is an external one connected thru DP.
Now the external monitor has different power states, the 'on' state is usually
signalled by a green light. Any suspended state is signalled by an amber light.
Also, when the display comes on, the backlight needs to come on. Even with a
fully black screen you usually see the backlight - especially when the ambient
light is dimmed.
Koenraad,
- can you check which color the monitor power light has when the monitor is
expected to be on?
- can you check if the backlight is on (although the screen appears to be
blank)?
- In this state, please run 'xrandr --verbose' and attach the output.
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=953479http://bugzilla.suse.com/show_bug.cgi?id=953479#c5
Zhao Qiang 赵强 <qzhao(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i(a)marguerite.su
Flags| |needinfo?(i(a)marguerite.su)
--- Comment #5 from Zhao Qiang 赵强 <qzhao(a)suse.com> ---
(In reply to Mark Fairbairn from comment #4)
> it seems that fcitx does not have a current bug tracking system (as far as I
> can tell).
> They were using google code which has recently been shut down (Aug) and I
> can't find an alternative
>
> https://code.google.com/p/fcitx/issues/list
>
> ???
Marguerite Su:
I saw you are a member of fcitx org, Could you communicate with community about
this issue?
https://github.com/fcitx
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=955962http://bugzilla.suse.com/show_bug.cgi?id=955962#c12
ill lume <illumilore(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(illumilore@gmail. |
|com) |
--- Comment #12 from ill lume <illumilore(a)gmail.com> ---
I think kde partition manager, gparted, and most other partion managers will
tell you when it is successful or failed. That seems to be standard for gui
programs.
Could you add more details?
It said something about special device not existing. The error stopped after I
used gparted instead to partition it.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=954549http://bugzilla.suse.com/show_bug.cgi?id=954549#c4
ill lume <illumilore(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #4 from ill lume <illumilore(a)gmail.com> ---
Then the man page should be fixed. The -i and -f option descriptions imply that
mv will overwrite or prompt when it encounters something already existing in
the target. It doesn't even mention directory behaviour specifically.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=910728
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard| maint:planned:update |maint:planned:update
| |ibs:running:1587:moderate
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=927407
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard| |ibs:running:1585:moderate
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=867990http://bugzilla.suse.com/show_bug.cgi?id=867990#c8
--- Comment #8 from Dieter Nützel <Dieter(a)nuetzel-hh.de> ---
(In reply to Marcus Meissner from comment #7)
> this seems to be a hidden dependency on specific mozilla-nspr versions. :/
>
>
> i hope its not happening anymore though
Hello Marcus!
I'm on openSUSE 13.2 for over a year, now.
In move to Leap 42.1 or better Tumbleweed on my devel machine (x64 finally) ;-)
On 13.2 I have this:
Name : mozilla-nspr
Version : 4.10.10
Release : 9.1
Architecture: x86_64
Install Date: Di 10 Nov 2015 05:08:49 CET
So this could be CLOSED from my side.
Happy New Year!
Dieter
--
You are receiving this mail because:
You are on the CC list for the bug.