Bug 1080082 has been marked as a duplicate of this one, although I'm not
sure it is (I use fglrx).
Anyway, my workaround for 1.5 months with no issues and no need for
arbitrary sleep has been to modify /etc/init/lightdm.conf and adding
"respawn" like this:
...
stop on runlevel [016]
respawn # <-
Public bug reported:
I'm running 12.10, and since installing the stable release in October I
didn't install any upgrades. This week, after installing the latest
upgrades, lightdm stopped working: the Xserver starts, and dies
immediately, leaving me on a tty7 with remains of log messages.
If I log
Might be related to bug #838586 and question #208880 ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1080082
Title:
Lightdm killed during boot (kills itself?)
Status in Ligh
Just to add, I've tried multiple workarounds, and the best one (works
every time) and less intrusive is modifying the file
/etc/init/lightdm.conf adding "respawn" like this:
...
stop on runlevel [016]
respawn
emits login-session-start
emits desktop-session-start
emits desktop-shutdown
---
--
@Robert: This is a firefox+nvidia proprietary linux driver issue.
Other browsers and drivers do not have it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/605567
Title:
Extremely slo
@Clint: But honestly, why not deploy the workaround by default?
It has 0 bad effects when you don't have the issue, and is the difference
between some strange flickering and most people not being able to get a working
system at all.
--
You received this bug notification because you are a member
> I have not seen data that proves it has 0 bad effects. I'd suspect that
> it would have a minor impact on time between power-on and login for
> those users who are not affected, but I also have no data on that either.
Sorry... say what!? I will just quote it for you, from canonical's upstart
do
Is this both a lightdm bug and a failsafe-x bug?
Because I don't get failsafe-x when lightdm fails, I just get a tty.
--
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/969489
Title:
ligh
I had this with fglrx, so either both amd and nvidia suffer from the same bug,
or it is elsewhere.
It's just a pity that this is treated as such low priority.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bug
Public bug reported:
My logout has been slow for months. Finally I decided to look it up, and it
seemed that tomboy could cause this, but the bug should be fixed according to:
https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/880299
https://launchpad.net/ubuntu/+source/tomboy/+changelog
But
Interesting, I too use btrfs for root and home.
--
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/969489
Title:
lightdm tries (and fails) to start too early?
Status in Upstart:
New
St
As peke said in comment #30: It's fixed in Firefox 19 (thanks!) but it
can still happen when using hardware acceleration.
I turned on layers.acceleration.force-enabled today (Firefox 20 / Ubuntu
12.10 64-bit / nvidia 310.14) and started noticing the issue again.
I can see it clearly in gmail, and
Ah, my bad! No need to screencast, the issue is exactly what kokoko3k
said in comment #28, but it doesn't need to be on a native widget (I see
it on gmail).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.l
@Comment #33: I'm not sure, I just tried to reproduce your issue and couldn't.
Have you tried it on another machine, just to be sure?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/10977
I think this bug should be attacked in two ways:
1) try to work with firefox and nvidia to fix this and
2) fix launchpad. The bug is elsewhere, but launchpad being broken with the
default ubuntu browser with pretty much the default configuration of any nvidia
linux user is very bad usability. And
Kpackagekit also breaks with updates (see my previous comment, its
latest version is called Apper) so... yeah. Not the solution also.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/85579
I also saw this.
It's a pity that both Apper (Bug# 905415) and Muon are broken for system
upgrades.
Shouldn't this be attributed to qapt or something like that? It seems
that packages do upgrade fine with apt-get, aptitude, synaptic, etc.
--
You received this bug notification because you are a
As an update, I never saw this issue again, so indeed it seems it is
caused by a race in logind.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/471457
Title:
Shutdown does
Just made a clean install of Ubuntu saucy and this started happening to
me sometimes.
I believe the issue happens due to systemd-logind, which is set to
always standby a laptop when you close the lid, and the supposed
solution can be found here: http://askubuntu.com/questions/360615
/ubuntu-server
Reported as a logind issue:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1311648
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/471457
Title:
Shutdown does not h
Ok so recently I got surprised by this issue. Unfortunately it is not
fixed in 13.10 and I don't believe it will be in 14.04 either. The
"changing driver" workaround did work for me.
The strange thing was, I installed the latest HP drivers on windows xp
and I got the exact same behavior! And also
Public bug reported:
When an HP Officejet Pro K550 is connected, by default CUPS picks hpcups
as a driver.
Unfortunately, hpcups is broken for this printer, and it has been for a long
time.
https://bugs.launchpad.net/hplip/+bug/981473
It was first broken in 11.04 and has been broken since. It h
Can this please be backported to at least Ubuntu 14.04? Otherwise users
will be afected by this issue for years to come.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1311697
Title:
HP
Thanks, I'll test as soon as it is posted! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1311697
Title:
HP Officejet Pro K550 should use hpijs by default
Status in “hplip” package
I successfully tested hplip/3.14.3-0ubuntu3.2 and it fixes my issue.
Thanks a lot!
---
To test:
I removed all printers from my system, and then added the printer again (with
the system-config-printer menu) with the old version, and hpcups was selected.
I then removed the printer again, upgraded
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1311697
Title:
HP Officejet Pro K550 should use hpijs by default
St
+1 thank you Ruslan.
I'm guessing that at this point we should be asking for this to be
implemented on Wayland, as it seems that X will be deprecated soon
enough and its input code is complex and strange enough (no screensaver
when a pop-up menu is open, for instance) that this won't make it.
--
Thanks for the answer. Upstream has since released wpa 2.5 which
includes those patches so I'll open a new request asking for that
version instead of the backport.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bug
Public bug reported:
Upstream release 2.5 has come out recently, including a number of
security bugfixes and additional channel selection and performance
improvements to 5GHz networks. Please update to it :)
Changelog:
2015-09-27 - v2.5
* fixed P2P validation of SSID element length befor
The current wpa version in debian testing includes the 5GHz band selection
improvements patch backports:
https://packages.qa.debian.org/w/wpa/news/20150906T154058Z.html
Would it be possible to also include these patches? As far as I've checked,
they were not included in the ubuntu 2.4 version.
(
It would be awesome to watch closely for the new version including the 5GHz
improvements:
http://blog.sesse.net/blog/tech/2015-07-14-21-25_wpa_supplicant_5ghz_improvements.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubunt
31 matches
Mail list logo
