I don't think it's a proprietary DVI (on the part of the MacBook Pro) as
it fits a regular DVI cable. dual-link DVI is what wikipedia says the
MacBook Pro has.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https:/
Both states last I recall worked on the latest release. I'm testing
trusty right now but both states aren't accessible via synapse
presently. I don't know if they will but expect it to be so. I'll try to
dig around for the line commands ...
--
You received this bug notification because you are a
The screen on the model I reported has failed on me. I now use an
external monitor hooked up via vga. I still get blanking but inquiries
tell me that this is due to variability in card and monitor resolution
tolarancy. So, I can't speak to this any longer.
Now if Ubuntu recognized the monitor via
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1031621
Title:
External Citizen
I'm runing trusty and it's not an issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1047146
Title:
xorg fails to configure native 1440 x 900 on LCD widescreen
Status in “xorg” packa
@ Sebastien: I guess I would say that "unity-greeter (or associated
package) should depend on lightdm", and not "unity-greeter should depend
on unity".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.
My fix being reinstalling unity-greeter. It installs a whole lot of
stuff, one of which surely fixed my low resolution issue. For some
reason I can't list the other greeters in lightdm.conf as doing so gives
a low resolution message. So I'm stuck with unity-greeter, but at least
I can run lightdm r
I came across another fix, when changing the greeter stopped working.
For those who removed Unity, removing it sometimes uninstalls unity-
greeter and reinstalling it installs a whole lot of stuff some of which
fixed my low resolution issue. For some reason the other greeters don't
work.
--
You r
Sebastian: There sure is a connection. I' ve seen it myself where
removing Unity (because it doesn' t run well on my machine) eventually
removes unity-greeter and I start to get the low resolution error
message. Reinstalling unity-greeter (which pulls in many things)
results in a working lightdm (
I started to get the low res complaints after uninstalling Unity. You
can only uninstall so many things (unity desktop, unity menu stuff )
before things get wacky (on various fronts).
It took me months but I found out that removing unity components (menu,
desktop, etc) using the howtos on the net
So being sent into low graphics mode would be one problem and the screen
overshooting (low tolerance for defective EDID) would be another, the
prior being solved and the later to be seen in 13.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
I know this bug report has been closed but I'd still like to leave a
record for myself and for any other having the same problems.
@Rolf
You might have been right about there being more than one issue at play here.
Since reporting this, I've had to stop using lightdm because of it sending me
in
@Rolf
I'm connecting via VGA. In truth, my macbook pro has a HDMI, and it came
with a " HDMI to VGA" adaptor. So my monitor receives a VGA signal, in
the end.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.l
*** This bug is a duplicate of bug 985065 ***
https://bugs.launchpad.net/bugs/985065
Has anyone tried manually deleting additional layouts, leaving the
default original, then pressing the default button in gnome preference's
Layout pane?
See my bug report and fix: https://bugs.launchpad.net/u
6. Of course, add layouts back before attempting to change to them.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/986322
Title:
Can't change layout using Unity indicator
Anyway (for those that might come across this), I found a fix, my fix.
1. Open the gnome preference "keyboard layout" pane
2. Move the layout order, if you have more than one
3. Delete all layouts except the default one (mine was a US layout)
The previous two steps have been suggested as fixes o
I got the error while adding a layout. It crashed but the layout had
been added,. or so one would think because it's listed, although the
preview shows the same layout regardless of which one is selected
--which may be a problem in of itself.
--
You received this bug notification because you are
I haven't noticed getting this while using pulseaudio,but I usually have
vlc open and constantly watching something with audio. The only other
common denominator, at least for me, is that I always get this while
logged in using OpenBox. It's always after a gnome-settings-daemon error
that my theme
I gather this is related to the low tolerance of faulty EDID I reported
in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156 Here's
what I reported therein.
Solution:
I've had to force the resolution with the following.
xrandr --newmode "1440x900_60.00" 106.47 1440 1520 1672 1904 900 90
After the system configured itself, it still boots into 1224 x 768
(4:3), which makes real estate go off-screen at the right and bottom,
affecting both lightdm and the desktop environment. See my bug report at
https://bugs.launchpad.net/lightdm/+bug/1047140
Solution:
I've had to force the resoluti
@2vi1: Do you have the same overshooting issue once logged into your
desktop environment?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1047140
Title:
lightdm overshoots physical sc
@2vi1: Yeah, it overshoots at the bottom, too.
I found two work-arounds. From memory,
A.
1. select your wm,
2. tab (once if I recall),
3. press enter, then the dialogue window will change or go back to the log-in
dialogue,
4. input your password if you haven't done so already and see yourself
"I'd say this is a bug in glib (gio) where it needs to remove the target
if cancelled at the "wrong" place.¨
https://mail.gnome.org/archives/gvfs-list/2009-April/msg8.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in U
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/1048421
Title:
empathy: Error contacting the Account Manager
Status in “empathy” package in Ubuntu:
New
Bug description:
Problem:
Public bug reported:
Problem:
I've got accounts setup properly, facebook IM and gmail. I know they work
because I access the accounts with other IM clients using the same credentials.
Details:
Upon starting empathy I get the following message twice:
"There was an error while trying to connect to
It's a widescreen.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1047140
Title:
lightdm overshoots physical screen size
Status in “lightdm” package in Ubuntu:
New
Bug description
The monitor has an active display area of 410.4 mm x 256.5 mm
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1047140
Title:
lightdm overshoots physical screen size
Status in “lightdm
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1047140
Title:
lightdm overshoots physical screen size
Status in “lightdm” package in Ubuntu:
New
Bug description:
Problem: lightdm
Public bug reported:
Problem: lightdm displays excessively large
Symptoms: I can't confirm change of window manager and top menu leaks
over to right hand side.
The screen is a LCD Citizen C19604HD that should run 1440x 900 at 60 Hz.
Upon entering the desktop the session is also excessively large
This is a selected excerpt taken from a related bug reported by moi. I
intended to copy pertinent info over but must have never gotten it. I'd
also hoped that it was noticed and taken care upstream but seeing now
that 12.10 still has issues with changing layouts, here it is.
1) Changing the layout
It's affecting me and I'm not using a live-CD, just an ordinary HD
install. In my case, I'm constantly logged back into Openbox, which I
like but sometimes want back into Unity, regardless of choosing Ubuntu
(Unity) in lightdm.
@Newfie & Sebastien: If it were a problem with the password, it would
This happens in 12.10 too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/749550
Title:
gnome-settings-daemon crashed with SIGABRT in raise()
Status in “gnome-settings-
I'm getting this same error on an upgrade to 12.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/410534
Title:
gnome-settings-daemon crashed with SIGSEGV in g_slice_al
*** This bug is a duplicate of bug 985065 ***
https://bugs.launchpad.net/bugs/985065
And I don't think this bug is a duplicate of bug #985065 because that
regards French layout. I'm using US style layouts and I have the ATM
/phone-style problem.
--
You received this bug notification because
*** This bug is a duplicate of bug 985065 ***
https://bugs.launchpad.net/bugs/985065
I think issues reported here are getting off topic. This bug report
concerns the failure to implement the phone style number pad, at least
in the description of the bug. If not, then feel free to contribute to
My mistake.
I thought Metacity played some minor role, especially since Unity is slightly
more stable after issuing compiz --replace from within a running instance of
Unity 3D. In this case, what I'm doing is simply restarting Unity 3D. Perhaps
it's a perceptual thing.
I just had compiz crash
Although my fix takes care of random crashes, there's still issues with
flickering and unforeseen freezes, which brought me to write another bug
and temporary solution.
See: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1031612
--
You received this bug notification because you are a memb
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/1031609
Title:
Metacity causes unity to crash using Gallium 0.4 on ATI RV530
Status in “metacity” package in Ubuntu:
New
Bug descrip
Public bug reported:
I gather the issue is with compiz because
compiz --replace
takes care of some random crashes and flickering.
Another solution is to edit
/usr/share/gnome-session/sessions/ubuntu-2d.session
so that on the line that reads
DefaultProvider-windowmanager=
metacity
is repla
There's a solution for trackpads.
xinput list-props will give you something like this:
Code:
Device 'SynPS/2 Synaptics TouchPad':
Device Enabled (133): 1
...
Synaptics Two-Finger Pressure (269): 282
Synaptics Two-Finger Width (270): 7
Synaptics Scrolling Distance (271): 112, 1
*** This bug is a duplicate of bug 966237 ***
https://bugs.launchpad.net/bugs/966237
And someone reported it upstream, actually two people.
https://bugzilla.gnome.org/show_bug.cgi?id=675047
https://bugzilla.gnome.org/show_bug.cgi?id=674716 which interestingly reads,
but it seems this fix i
I am having keyboard layout issues. See
But I don't think it's related since I "found the problem".
The caps-lock key is at fault.
Now, before everyone assumes I select it before rebooting. I don't. And
the strange thing is that if the caps lock state is indeed persistent
across reboots, then re
I thought about calling it a regression but for that to be valid, I
would think the bug would have need to have existed prior to now, so as
to regress to a previous (broken) state. What's happening here is that
it simply isn't working, in a __new__ way.
--
You received this bug notification becau
And by the way, I think this bug should be reported directly to gnome or
gtk people, or both.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/951123
Title:
nautilus not natural scroll
You might classify the issue into two parts.
Cosmetic problem:
What happens when I try to change the layout, say to the second from the top
layout is that the global menu icon will go from showing "en" to "en2", the 3rd
from the top to "en3", etc, all the way to 4 (which apparently is the limit
dconf /org/gnome/libgnomekbd/keyboard/layouts:
['us\tintl', 'us\talt-intl', 'us\taltgr-intl']
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"
--
You received this bug notification because you are a member of Desktop
Pa
** Summary changed:
- Can't change layout using Unity "applet" nor Gnome Control Center --Precise
upgrade
+ Can't change layout using Unity indicator nor Gnome Control Center --Precise
upgrade
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
I just re-logged in to get this error, and I didn't even open nautilus.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/905686
Title:
nautilus assert failure: nautilus: ../../src/xcb_
"Workaround
-seems to be to choose the layout from lightdm."
Although the layout does indeed change in X (and not in console, unless
perhaps a reboot effectuates the change), it is not reflected in ~/.dmrc
nor in /etc/default/keyboard. So where are the layouts that take
precedence come from?
Chan
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/986354
Title:
Logging in at lightdm sometimes repeatedly fails --Precise upgrade
Status in “lightdm” package in Ubuntu:
New
Bug descr
Public bug reported:
Logging in at lightdm sometimes repeatedly fails, no matter how
carefully I type. Having a look at the layout menu shows that I'm using
the layout I always do.
Workaround:
1) reboot, the easiest solution
2) move into tty *, and doing something like sudo /etc/init.d/lightdm re
The way I see it, there are at least two issues here.
1) The issue of not being able to change a layout within a session from the
Unity "applet", /etc/default/keyboard not keeping sync with applet --I am
supposing it is supposed to keep in sync.
2) And the issue of /etc/default/keyboard not ke
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/986322
Title:
Can't change layout using Unity "applet" nor Gnome Control Center
--Precise upgrade
Status in “gnome-contro
Public bug reported:
Problem:
I can't use the keyboard mapping recently chosen.
Details:
Selecting anything other than the US International with dead keys layout from
the Unity applet doesn't invoke a layout change. Going to
gnome-keyboard-properties and high lighting and moving desired layou
Precise upgrade and I got it simply seconds after logging in from a
fresh boot. Can we have the status changed to confirmed since so
multiple people are getting it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/984248
Title:
Logging out of sessions results in a transitional black textual screen
--Precise upgrade
Status in “lightdm” package in
Public bug reported:
When I log out of sessions, a black screen appears before lightdm
appears. I don't know if it's Xorg's, Unity's or lightdm's fault but it
needs to be addressed as it gives an unprofessional look.
Precedure to reporoduce:
The obvious, log out of Unity.
ProblemType: Bug
Distro
** Also affects: nautilus
Importance: Undecided
Status: New
** Also affects: gtk
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/95
So natural scrolling is part of something larger called smooth scrolling
in Gnome and it's automatically enabled if it picks up on a tablet or
some other ultra-portable medium. But where does leave us mouse/pad
users --be that of desktops or laptops-- that prefer natural scrolling?
Apparently, the
Sebastien:
I've tested the if my macbook pro pad registers natural scrolling and it does
not. To clarify, when my fingers glide over the pad towards me, the on-screen
document scrolls to the bottom of the page rather than to the top (as it should
in natural/reverse scrolling).
So unless settin
Apparently the bug Vadeem links this as a duplicate to is fixed.
Sebastien says (therein) that any continued problems are likely to be
other bugs. So, since we continue to have the same problem, this should
not be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/949465
--
You
ubutn2-fan: My comment was not geared towards you but informing
Sebastian as to what it was. And you're correct, it does not work. It
doesn't work in software center, or update manager, neither.
I even reported it as so, see:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/971564
ht
And I've marked my reports as duplicates of this one.
Cheers.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/951123
Title:
nautilus not natural scrolling
Status in “nautilus” packa
*** This bug is a duplicate of bug 951123 ***
https://bugs.launchpad.net/bugs/951123
** This bug has been marked a duplicate of bug 951123
nautilus not natural scrolling
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-cen
"When Apple releases Mac OSX Lion, one of the changes is the switching of the
trackpad/mouse scrolling direction. Instead of scrolling the mouse wheel down
to move down the page, you have to scroll up to move down. Apple imported this
feature from iOS and call[s] this feature “natural scrolling”
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/971513
Title:
Natural scrolling does not work in gnome-control-center on Precise
Beta
Status in “gnome-control-center” pa
Public bug reported:
Natural scrolling using ".Xmodmap": pointer = 1 2 3 5 4 7 6 8 9 10 11 12
doesn't work anymore.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic i68
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/971510
Title:
Natural scrolling does not work in Nautilus on Precise Beta
Status in “nautilus” package in Ubuntu:
New
Bug descriptio
Public bug reported:
Natural scrolling using ".Xmodmap": pointer = 1 2 3 5 4 7 6 8 9 10 11 12
doesn't work anymore.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic i686
ApportVers
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/970822
Title:
package python-uno 1:3.5.1-1ubuntu1 failed to install/upgrade:
subprocess new pre-installation script returned error
Public bug reported:
Was doing a update/upgrade/distupgrade when there was a conflict with
python-uno and a libreoffice ackage (libreoffice-emailmerge).
This is the second time during the development of Precise that this
occurs and I believe that this has happened during previous upgrades,
albeit
71 matches
Mail list logo