@Timo
Yeah, I believe it's gnome, more so.
It's part of a long time attitude on the part of gnome developers,
constantly breaking their own software, be it simple themes, standard
desktop norms, or as we have here ... mouse configurability, all against
user wishes.
Apparently it's fixed as
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: xserver-xorg-video-ati (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031621
Title:
External Citizen monitor does not autoconfigure
I'm runing trusty and it's not an issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047146
Title:
xorg fails to configure native 1440 x 900 on LCD widescreen
To manage notifications about this
Leaving nothing but the following lines in /etc/adobe/mms.cfg solved it
for me.
EnableLinuxHWVideoDecode=0
OverrideGPUValidation=true
http://ubuntuforums.org/showthread.php?t=1985689
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Simon Schneegans
Yeah, tried your ppa to no avail. Your program wants libbamf3-1 but
chokes since only libbamf3-2 is available. I'm running Saucy.
wajig install gnome-pie
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could
** Description changed:
Symptoms:
Excessive fan use.
Ran fine with Ubuntu Natty Narwhal, but successive upgrades resulted in both
fans running full shortly after bootup (regression). I justified it thinking
that Ubuntu had higher requirements, until infrequent failed attempts to boot
There are two issues, a timing one and a firmware one.
Thanks to
http://forums.gentoo.org/viewtopic-t-573272-view-previous.html?sid=dc5a86b654f0b9d93e91e7438f8bf05c
and http://www.thinkwiki.org/wiki/Intel_Core_2_Duo_%28Merom%29 I learned that
the core2Duo has a microcode update and that it
Although the last few updates in Raring introduced system freezes, I
can't say they were LIRC/Atheros related. They seemed to be related to
un/mounting of USB pendrives, but I didn't bother to stick around. I
upgraded to avoid the problem altogether.
I can say the first I recognized the kernel
I just had a kernel panic with ath9k. The odd thing about it is that the
trace made mention of appleir and up funtionality despite not touching
the remote. It ocurred while closing off Parole.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
And I don't have Parole configured to work with lirc. Althoug I think I
had vlc running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222070
Title:
Kernel Panic --not syncing fatal exception in
I recently read that Atheros can work either with ath5k or ath9k so I
blacklisted the prior and enabled the latter on bootup the following
way.
sudo nano /etc/modprobe.d/blacklist.conf
blacklist ath5k
sudo nano /etc/modules
ath9k
Again, this allows me to start vlc with ir support enabled and
There, I've identified a bug, confirmed it's reproducible and how,
established the culprits involved but to summarize:
identified bug:
Kernel Panic --not syncing fatal exception in interrupt
how it's reproducible:
Start mplayer to watch a video or
vlc with infrared enabled or
$ irrecord -d
OK, I think I may be onto something. The only thing that comes close to
the error message are problems with wireless.
Before I go further, vlc is crashing on startup because ir support is
now enabled.
http://forum.ubuntu-fr.org/viewtopic.php?id=1258711 makes mention of Atheros
issues est
I just tried linux-
image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386.deb
last night and it has the same issue. Interestingly, vlc doesn't respond
to the remote but this does not immediately cause the kernel panic, not
until I startup totem, but that may have been because infrared
call trace
** Attachment added: P1010856.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833927/+files/P1010856.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
call trace
** Attachment added: P1010852.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833929/+files/P1010852.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
call trace
** Attachment added: P1010855.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833928/+files/P1010855.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
call traces
** Attachment added: P1010857.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833917/+files/P1010857.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
call trace
** Attachment added: P1010854.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222070/+attachment/3833930/+files/P1010854.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I reinstalled
lirc lirc-x gnome-lirc-properties
Considering that my previously working/etc/lirc/hardware.conf mentions
/dev/usb/hiddev0 I ran the following and was able to immediately elicit
a kernel panic response.
irrecord -d /dev/usb/hiddev0 -H macmini output_conf_file
--
You received this
Considering that my previously working/etc/lirc/hardware.conf mentions
/dev/usb/hiddev0 I ran the following and was able to immediately elicit
a kernel panic response.
irrecord -d /dev/usb/hiddev0 -H macmini output_conf_file
and that as regular user!
--
You received this bug notification
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222070
Title:
Kernel Panic --not syncing fatal exception in interrupt
To manage notifications about this
problem exists running linux-
image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_i386.deb
By the way, I get the following when trying to follow:
kernel-bug-exists-upstream-VERSION-NUMBER
See:
this sounds an awful lot like a bug reported last year in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066449.
AND
http://ubuntuforums.org/showthread.php?t=2142150
Although the latter inculpates jupiter.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Yes, my issue started with the upgrade.
I still have the issue and I'm running 3.11.0-7-generic.
For comparative purposes, linux-
image-3.11.0-031100-generic_3.11.0-031100.201309021735_i386.deb from
https://wiki.ubuntu.com/KernelMainlineBuilds (the one all the way at the
bottom) has the same
Public bug reported:
Using the infrared remote control results in a kernel panic. This is
reproducible using mplayer.
1) lsb_release -rd
Description:Ubuntu Saucy Salamander (development branch)
Release:13.10
2) apt-cache policy linux
linux:
Installed: (none)
Candidate: 3.11.0.4.5
Public bug reported:
Symptoms:
Excessive fan use.
Ran fine with Ubuntu Natty Narwhal, but successive upgrades resulted in both
fans running full shortly after bootup (regression). I justified it thinking
that Ubuntu had higher requirements, until infrequent failed attempts to boot
finally
By the way, the other suggestion, to put modprobe coretemp into /etc/rc.local
doesn't work as on reboot dmesg | grep coretemp outputs the same issue:
[ 45.462182] coretemp: Errata AE18 not fixed, update BIOS or microcode of the
CPU!
[ 45.462194] coretemp: Errata AE18 not fixed, update BIOS
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807353/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807357/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807356/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807351/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807354/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807355/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807349/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807358/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807352/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
Title:
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807359/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807350/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
Title:
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807360/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
Title:
apport information
** Tags added: apport-collected saucy staging
** Description changed:
Symptoms:
Excessive fan use.
Ran fine with Ubuntu Natty Narwhal, but successive upgrades resulted in both
fans running full shortly after bootup (regression). I justified it thinking
that Ubuntu had
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807361/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807363/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1222112/+attachment/3807362/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222112
Title:
It almost goes without saying that the infrared works with LIRC.
wajig show lirc
Package: lirc
State: installed
Automatically installed: yes
Version: 0.9.0-0ubuntu3
wajig show lirc-x
Package: lirc-x
State: installed
Automatically installed:
I get the mentioned output when X locks up (mouse movement excluded)
running with a radeon x1600 video card, Gallium 0.4 on ATI RV530. I
usually manage to get to tty* to see the error repeatedly posted and
sometimes, with the addition of [drm:radeon_cs_chunk] *ERROR* failed to
schedule IB!.
Oops, I read black screen for some reason. My problem is a hard lock.
Please ignore my comments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156525
Title:
Back screen after wakeup
To manage
I get the same issue on a macbook Pro intel with an ATI (Mobility)
Radeon X1600 (ATI RV530/M56-P) video card with the 3. series kernel.
This issue doesn't seem to have occurred with prior kernels, certainly
not earilier than a week or two.
--
You received this bug notification because you are a
video card with the 3.8 series kernel, 3.8.0-17-generic to be exact.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1156525
Title:
Back screen after wakeup
To manage notifications about this bug go
I should mention that in my case, it's from the blackening of the screen
due to inactivity that my laptop sometimes does not wake up from, not
from closing the lid shut. As a workaround, I' ve gone to brightness and
lock (gnome settings) and set Turn screen off when inactive for to
Never and
By the way, when the black screen occurs, my keyboard is unresponsive as
I can't get my keyboard's Num Lock indicator to light up. Sysrq key
combinations also fail to work (as noticed by the fact that the b
combination does not result in a reboot and I don't get control over
keyboard input back).
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.
--
You received this bug notification because you are
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
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
@ 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
And don't list anything else but unity-greeter in lightdm.conf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070150
Title:
Intermittent black screen or low graphics mode message
To manage
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
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 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
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 Ubuntu
Bugs, which is subscribed
Changing the greeter invoked worked like a charm for me. I wrote about
the fix in https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1047156
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070150
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 on
*** 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:
6. Of course, add layouts back before attempting to change to them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986322
Title:
Can't change layout using Unity indicator nor Gnome Control Center
Replacing it might be an option as this seems to be an ongoing problem.
Anyone know of a stand in?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/898336
Title:
tumblerd crashed with SIGSEGV in
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
@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
@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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047140
Title:
lightdm overshoots physical screen size
To
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
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 901
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'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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048421
Title:
empathy: Error contacting the Account Manager
To manage notifications about this bug go to:
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047140
Title:
lightdm overshoots physical screen size
To manage notifications about this bug go to:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047140
Title:
lightdm overshoots physical screen size
To manage notifications about
Another carry over to 12.10 beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031604
Title:
cntrl-alt-del does not kill Xorg
To manage notifications about this bug go to:
This again happens in 12.10 beta. It was fine till a few updates ago.
This always seems to be the case in early betas until it's borked
shortly before release.
** Summary changed:
- Logging out of sessions results in a transitional black textual screen
--Precise upgrade
+ Logging out of
It's a widescreen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047140
Title:
lightdm overshoots physical screen size
To manage notifications about this bug go to:
Public bug reported:
The screen is a LCD Citizen C19604HD that should run 1440x 900 at 60 Hz
(as per manual). Upon entering the desktop the session is also
excessively large, 1224 x 768 (4:3) and only allows a worse setting of
800 x 600 (4:3).
I must say, that every once in a while, Display
Correction: Upon entering the desktop the session is also excessively
large, 1024 x 768 (4:3) ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047146
Title:
xorg fails to configure native 1440 x
Public bug reported:
Ubuntu has new strict EDID guidelines that does not allow LCD widescreen
configuration.
Symptoms:
Constant flickering on and off of screen content, including distortion similar
to a bad tv reception.
The screen is a LCD Citizen C19604HD that should run 1440x 900 at 60 Hz
My video card is a Radeon X1600, Gallium 0.4 on ATI RV530 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047146
Title:
xorg fails to configure native 1440 x 900 on LCD widescreen
To manage
It happens to me when downloading a file from Firefox passed onto a line
command downloader.
The problem
is not with Firefox or the downloader but as I recall with tumbler daemon,
tumblerd if I recall, whose job it is to create images to downloaded files.
Steps to reproduce
-Download media
This bug is still existent in 12.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031604
Title:
cntrl-alt-del does not kill Xorg
To manage notifications about this bug go to:
This bug is still existent in 12.10 beta.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031593
Title:
ATM/phone-style number pad fails to implement
To manage notifications about this bug go to:
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
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
step 1: I log in using lightdm
step 2: lay back a minute
step 3: receive the error message
step4: use the desktop environment as an ordinary end user for everyday
purposes, (open Firefox, Thunderbird, Marlin, Openbox with tint2, SeaMonkey)
step5: at some random moment latter in the session,
This happens in 12.10 too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/749550
Title:
gnome-settings-daemon crashed with SIGABRT in raise()
To manage notifications about this bug go to:
Yeah, I always get a crash error on start-up and asks if I want to start
it up again, despite that when I check it's still running. It doesn't
affect functionality, apparently, just plain annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Invoking update-manager results in the following message.
An unresolvable problem occurred while calculating the upgrade.
Please report this bug against the 'update-manager' package and include the
following error message:
E:Error, pkgProblemResolver::Resolve generated
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041049
Title:
update-manager can't resolve calculating an update to latest 12.10
To manage notifications about this bug go to:
Here's a complaint (from another user) and an explanation:
http://askubuntu.com/questions/89826/what-is-tumblerd
Thunar apparently still has the same issue (on Precise), but Nautilus on
Precise doesn't, although on 12.10 beta it (Nautlilus) does. Apparently,
this is a prevalent issue.
--
You
The issue seems to have worked itself out on Precise, and on 12.10 it's
not an issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1031612
Title:
Unity freezes using Gallium 0.4 on ATI RV530
To
1 - 100 of 372 matches
Mail list logo
