date:20101004

[Bug 655004] Re: gnome-display-properties assert failure: gnome-display-properties: ../../src/xcb_io.c:385: _XAllocID: Assertiva `ret != inval_id' falhou.

2010-10-04 Thread Daniel Che


** Attachment added: "CoreDump.gz"
   https://bugs.launchpad.net/bugs/655004/+attachment/1672731/+files/CoreDump.gz

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/655004/+attachment/1672732/+files/Dependencies.txt

** Attachment added: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/655004/+attachment/1672733/+files/Disassembly.txt

** Attachment added: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/655004/+attachment/1672734/+files/ProcMaps.txt

** Attachment added: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/655004/+attachment/1672735/+files/ProcStatus.txt

** Attachment added: "Registers.txt"
   
https://bugs.launchpad.net/bugs/655004/+attachment/1672736/+files/Registers.txt

** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/655004/+attachment/1672737/+files/Stacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/655004/+attachment/1672738/+files/ThreadStacktrace.txt

** Attachment added: "XsessionErrors.txt"
   
https://bugs.launchpad.net/bugs/655004/+attachment/1672739/+files/XsessionErrors.txt

** Visibility changed to: Public

-- 
gnome-display-properties assert failure: gnome-display-properties: 
../../src/xcb_io.c:385: _XAllocID: Assertiva `ret != inval_id' falhou.
https://bugs.launchpad.net/bugs/655004
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 585209] Re: .odt and .ods open with fileroller instead of openoffice

2010-10-04 Thread ipsi

This is affecting me too. I cannot create a new user on the target
system, as I do not have the correct permissions (and in any event it
doesn't have a GUI).

This did not occur under Ubuntu 9.10, and has only started happening
since I upgraded (I did *not* do a fresh install) to Ubuntu 10.04.

When I select properties for the file, then "Open With", I see that Open
Office is the only application selected. However, when I double-click on
the file to open it, I get the message "There is no application
installed for OpenDocument Text files". If I then select Open Office
manually, it opens a blank document. If I copy the file locally, then I
can open it and edit it.

I can open other files via SFTP (e.g. text files), so the blank document
part might be an open office problem. However, I'm unsure why it does
not think there is any application that is able to open .odt documents.

Running gnome-open from the command line gives me this:

# gnome-open sftp://u...@host/path/to/doc.odt
Error showing url: No application is registered as handling this file

Is there anything else I can provide you with that might help?

-- 
.odt and .ods open with fileroller instead of openoffice
https://bugs.launchpad.net/bugs/585209
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 640807] Re: Forces low refresh rate on CRT monitor

2010-10-04 Thread Martin Pitt

Just confirming, for me the bug manifests differently: I have a
1280x1024 external monitor, and X starts in that mode (with a little
help in xorg.conf). However, g-s-d tries to be too clever and switches
it to 1024x768, presumably because xrandr thinks that this is the
highest common resolution with my internal monitor (1280x800). So I now
get two unnecessary modeswitches during boot (my desktop session of
course switches it back to 1280x1024).

So this is indeed a regression.

-- 
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 585209] Re: .odt and .ods open with fileroller instead of openoffice

2010-10-04 Thread ipsi

** Changed in: nautilus (Ubuntu)
   Status: Invalid => Incomplete

** Changed in: nautilus (Ubuntu)
   Status: Incomplete => New

-- 
.odt and .ods open with fileroller instead of openoffice
https://bugs.launchpad.net/bugs/585209
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 608033] Re: Scrambled Login Screen

2010-10-04 Thread ttk1opc

This is what I am getting:
 [   10.050198] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing 
generic driver

I don't recall it in 10.04 but I did get the same scrambled screens when
I used the proprietary drivers in either 10.04 or 10.10

-- 
Scrambled Login Screen
https://bugs.launchpad.net/bugs/608033
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 654978] Re: ubiquity slideshow still mentions F-Spot even though replaced by Shotwell

2010-10-04 Thread Delan Azabani

This is actually a bug in ubiquity, as its package has the slideshow
data.

** Package changed: f-spot (Ubuntu) => ubiquity (Ubuntu)

** Changed in: ubiquity (Ubuntu)
   Status: New => Confirmed

-- 
ubiquity slideshow still mentions F-Spot even though replaced by Shotwell
https://bugs.launchpad.net/bugs/654978
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 127617] Re: GNOME Power Manager installation problem

2010-10-04 Thread Nuphar C

oooh, I thought I was alone there with this problem for a second!

For me though it made the access to linux denied altogether and I have to log 
on to windows instead...Every time I try to log in through the linux partition 
I get this "gnome power manager was installed incorrectly" small message at the 
top right side of the screen, and it doesn't allow me to log in. 
I don't know what caused it since it worked fine and then it just happened, 
don't remember doing something differently...
Any advice?

-- 
GNOME Power Manager installation problem
https://bugs.launchpad.net/bugs/127617
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 654978] Re: ubiquity slideshow still mentions F-Spot even though replaced by Shotwell

2010-10-04 Thread Sujith S

** Package changed: ubuntu => f-spot (Ubuntu)

-- 
ubiquity slideshow still mentions F-Spot even though replaced by Shotwell
https://bugs.launchpad.net/bugs/654978
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 654978] [NEW] ubiquity slideshow still mentions F-Spot even though replaced by Shotwell

2010-10-04 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Maverick's installer still mentions F-Spot in its installation
slideshow, and this should be changed to Shotwell.

** Affects: f-spot (Ubuntu)
 Importance: Undecided
 Status: New

-- 
ubiquity slideshow still mentions F-Spot even though replaced by Shotwell
https://bugs.launchpad.net/bugs/654978
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to f-spot in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 654981] Re: SRU empathy to 2.32.0.1 in maverick

2010-10-04 Thread Ken VanDine

** Changed in: empathy (Ubuntu)
   Importance: Undecided => Low

** Changed in: empathy (Ubuntu)
   Status: New => Triaged

-- 
SRU empathy to 2.32.0.1 in maverick
https://bugs.launchpad.net/bugs/654981
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 654981] [NEW] SRU empathy to 2.32.0.1 in maverick

2010-10-04 Thread Ken VanDine

Public bug reported:

Binary package hint: empathy

Binary package hint: empathy

uploaded to -proposed:

empathy (2.32.0.1-0ubuntu1) maverick-proposed; urgency=low

  * New upstream release
- auth client crashes when trying to connect (Cosimo Cecchi)
- show the "new message" icon regardless of focus, active tab (Guillaume 
Desmottes)
- Should leave fullscreen mode when call is disconnected (Guillaume 
Desmottes)
- doesn't check unique result (Guillaume Desmottes)
- Better heuristic to pick default individual (Guillaume Desmottes)
- Contacts list window triggers _NET_ACTIVE_WINDOW timestamp error from 
Metacity (Guillaume Desmottes)
- update Empathy to deprecation changes in GTK+ 2.22 (Diego Escalante 
Urrelo)
- Hitting redial doesn't clear error messages (Guillaume Desmottes)
- Empathy Loses ContactInfo data it doesn't support in the UI (Guillaume 
Desmottes)
- Always show status icon in contact right-click menu (for meta-contacts)
- Refers to a nonexistent UI item (Milo Casagrande)
- Recommended SIP provider no longer available (Milo Casagrande)

test case:
- install the new version from -proposed
- test that you still can chat with your contacts on different networks
- check that font size is more readable than previous version

** Affects: empathy (Ubuntu)
 Importance: Low
 Status: Triaged

-- 
SRU empathy to 2.32.0.1 in maverick
https://bugs.launchpad.net/bugs/654981
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to empathy in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 553162] Re: Set $LANGUAGE if the user picks a different locale in gdm, so that language-selector and gdm stop disagreeing

2010-10-04 Thread Gunnar Hjalmarsson

@ David
Thanks for your praising comment.

It seems to me that you, and possibly also Martin, assume that $LANG
ought to correspond to the first language in the $LANGUAGE list. That, I
believe, is a misconception, at least from a language-selector
perspective, and I fear that we have talked at cross-purposes so far.

In an attempt to help changing that, I wrote a wiki-page:
https://wiki.ubuntu.com/GdmLanguageSelectorDissonance

It summarizes my view on where we stand, where we want to go ("Desired
behavior"), and my proposed solution in English. It would be great if
you, Martin and anybody else with an interest in this issue could study
the page and add your possible objections and comments.

Basically, what I hope to convince you about is that since it's only language 
that the users can set from GDM, and not any other locale aspects, GDM should 
not do anything with the $LANG variable. Not at any point. Never.
Instead GDM should update $LANGUAGE and set $LC_MESSAGES. That appears to be 
sufficient to reliably control which language is used in menus and messages. 
$LANG is used for the non-translation locale aspects, and its value shall not 
be used as a fall back by programs that don't understand $LANGUAGE.

As regards apps that don't understand $LANGUAGE:
> Rather than using a workaround, would it not be better to fix the
> bug in the affected applications? I see you've followed up on
> Firefox already. 

If I have understood it correctly, $LANGUAGE is a gettext specific
variable, and certain applications' inability to understand that
variable is not a bug per se. Consequently I think that Ubuntu in any
case shall provide the preferred translation language also via the
$LC_MESSAGES variable, and I don't think that's a workaround. Rather
should the Firefox fix I provide at bug 550222 be considered a
workaround IMO.

I noted that you don't consider this issue a matter for the translation
community. But it's a borderline case, isn't it? ;-)

-- 
Set $LANGUAGE if the user picks a different locale in gdm, so that 
language-selector and gdm stop disagreeing
https://bugs.launchpad.net/bugs/553162
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 625793] Re: Keyboard layout automatically changes + 100% CPU usage [updated]

2010-10-04 Thread Dmitry Shachnev

** Description changed:

== General description ==

On some Ubuntu installs with two or more keyboard layouts (e.g. Russian
and US English), after some time the keyboard layouts start switching in
an endless loop and gnome-settings-daemon starts using more and more CPU
until it reaches 100%.

== Known information ==

1) Some people here confirm that this happens with non-GTK (Java or Qt)
windows more often then with native GTK. (probably, might be a coincidence)
2) Possible fixes are killing and restarting gnome-settings-daemon or
disabling the "Separate layout for each window" option in keyboard preferences
window.
3) The second fix, however didn't work for most people, though it might
really reduce the probability of the bug appearing.
4) The bug happens both on upgrade installs and clean installs of Ubuntu,
confirmed with RC and Alpha 3.
5) The bug is specific to Ubuntu, not existing in Arch Linux and AgiliaLinux.
6) There are users who experience this problem with Russian, Slovakian,
Macedonian, Hebrew layots. Having such a problem in final release will make
keyboard use very problematic for users from these countries, so Ubuntu can
lose many users.
7) The bug is still not fixed in GNOME 2.32, which again proves that it's an
Ubuntu-specific issue.
8) For some users, the bug disappears after 2 to 15 minutes of use.
9) Confirmed for almost any key set for switching layouts (Shift+Alt,
Shift+Ctrl, CapsLock, Alt, Ctrl)
10) Confirmed for both Latin and non-Latin layouts.
11) Permanent fix is to disable g-s-d keyboard plugin in gconf, not fully
confirmed though.
12) Confirmed as a g-s-d issue, both with and without indicators.

== Debug ==

APPORT DATA here:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/633167
and here:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/633346
MORE LOGS:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/636619
GDB DATA:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/629444
XSESSIONERRORS:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/630712
- RANDOM LOGS:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/640824
+ RANDOM LOGS:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/64082
+
XEV OUTPUT: infinite loop of
PropertyNotify event, serial 30, synthetic NO, window 0x601, atom 0x174
(XKLAVIER_STATE), time 11886812, state PropertyNewValue
+ [NEW] GSD output:
+ (gnome-settings-daemon:2057):
+ libappindicator-CRITICAL **: app_indicator_set_label: assertion
`IS_APP_INDICATOR (self)' failed

P.S. Do. Not. Touch. This. Please. There's more info here, which can
make the devs remove the Incomplete status. Не трогайте это, пожалуйста.
Здесь намного больше информации, чем во всех предыдущих описаниях, может
снимут Incomplete.

TO DEVELOPERS: Please, comment on what logs and other info you need to
get this problem solved.

** Description changed:

== General description ==

== Known information ==

1) Some people here confirm that this happens with non-GTK (Java or Qt)
windows more often then with native GTK. (probably, might be a coincidence)
2) Possible fixes are killing and restarting gnome-settings-daemon or
disabling the "Separate layout for each window" option in keyboard preferences
window.
3) The second fix, however didn't work for most people, though it might
really reduce the probability of the bug appearing.
4) The bug happens both on upgrade installs and clean installs of Ubuntu,
confirmed with RC and Alpha 3.
5) The bug is specific to Ubuntu, not existing in Arch Linux and AgiliaLinux.
- 6) There are users who experience this problem with Russian, Slovakian,
Macedonian, Hebrew layots. Having such a problem in final release will make
keyboard use very problematic for users from these countries, so Ubuntu can
lose many users.
+ 6) There are users who experience this problem with Russian, Slovakian,
Macedonian, Hebrew, Georgian layots. Having such a problem in final release
will make keyboard use very problematic for users from these countries, so
Ubuntu can lose many users.
7) The bug is still not fixed in GNOME 2.32, which again proves that it's an
Ubuntu-specific issue.
8) For some users, the bug disappears after 2 to 15 minutes of use.
9) Confirmed for almost any key set for switching layouts (Shift+Alt,
Shift+Ctrl, CapsLock, Alt, Ctrl)
10) Confirmed for both Latin and non-Latin layouts.
11) Permanent fix is to disable g-s-d keyboard plugin in gconf, not fully
confirmed though.
12) Confirmed as a g-s-d issue, both with and without indicators.

1 2 3 4 5 >

1 - 100 of 485 matches

Mail list logo