Ok, I guess this is embarrassing, but as I was trying James' workaround
in #92 , I started thinking that somehow the signal was weak or
intermittent. A few minutes later, Solaar (the GUI that displays status
of Logitech wireless devices) tells me that the battery level in the
mouse was down to 5%.
Same as Kristin #85 :
Disconnecting the USB receiver in a port, and connecting it in the USB
port just besides it, has been working for some time now. Middle click
is now recognized in System Settings. Ubuntu 16.04, NVIDIA drivers.
xinput list
⎡ Virtual core pointer id=2
I guess this is obvious. But this bug still happens in Xenial.
lmilano@grisell:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
lmilano@grisell:~$ dpkg -l |grep cups-client
ii cups-client
Just a quick note.This problem persists after the official release of
15.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504698
Title:
NetworkManager crashes after reboot
To manage
*** This bug is a duplicate of bug 1500399 ***
https://bugs.launchpad.net/bugs/1500399
Public bug reported:
I upgraded my HP Chromebook 14 from 15.04 to 15.10 beta. After cold
boot, NetworkManager crashes and I get the popup to send a bug report
for a NM crash. There is no network, either.
*** This bug is a duplicate of bug 1500399 ***
https://bugs.launchpad.net/bugs/1500399
An automatic comment stating that this bug is a duplicate has been
added, but the allegedely original bug doesn't seem to exist.
--
You received this bug notification because you are a member of Ubuntu
** This bug is no longer a duplicate of private bug 1500399
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1504698
Title:
NetworkManager crashes after reboot
To manage notifications about this bug
Thank you, Till, I was looking for the proper place to change the tag :)
Cheers,
Leo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1422004
Title:
pkservice.py crashed with AttributeError in
Hi
I enabled 'proposed' vivid updates, installed hplip 3.15.2-0ubuntu4.1 ,
and I could successfully run the hp-plugin component. As far as my local
machine goes, the package fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After upgrading to Vivid, my HP LaserJet M1212nf MFP would not work
anymore, and trying to install the binary driver, as prompted by the
HPLIP utility would fail. After fiddling for a good hour, I realized
that the utility was failing to load the python modules for hplip:
Yes, indeed, the crashes are not happening anymore, sorry, I should have
updated this.
On Apr 13, 2015 9:11 AM, Till Kamppeter 1437...@bugs.launchpad.net
wrote:
Most probably fixed in cups-browsed 1.0.67-0ubuntu2. Please update and
re-open this bug if you still have problems.
** Information
Same here, I am running the current version of Xubuntu 15.04 on an HP
Chromebook 14 Falco, and the (50s) delay disappears when using the
tpm_tis.force=1 option in grub.
I wonder if this has to do with loading Ubuntu from coreboot, since the setting
is related to Trusted Platform management
Ok, before rebooting, I just removed the offending file. It is growing
at a rate of 1Gb every 10s or so. I will try logging out and in, and see
if the log is still growing continuously ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It just happened here. I will need to clean up and reboot. This is how
it looks like
lmilano@grisell:upstart$ ls -lh unity7.log
-rw-r- 1 lmilano users 53G Nov 12 16:03 unity7.log
lmilano@grisell:upstart$ tail unity7.log
_xgeWireToEvent: Unknown extension 148, this should never happen.
To be clear: I removed the file before rebooting, but it got regenerated
and refilled at a furious pace, with the same message: _xgeWireToEvent:
Unknown extension 148, this should never happen.
At that time, top was reporting upstart as the most process, obviously
caught in an infinite loop
Same here, Ubuntu 14.10, Intel Haswell i5 graphics. The following
workaround (suggested in the chromium issue shown above) works for me:
google-chrome -disable-gpu-sandbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Christopher, I am not sure what you mean. I experienced exactly the same
bug as described here (Touchpad not detected on Ubuntu 14.10) on exactly
the same hardware (Dell XPS 13), under the exact same conditions
(upgrade from 14.10). I am providing information in the interest of
helping handle the
Same here. I have an xps 13 running ubuntu 14.10. When I upgraded from
12.04 (as installed by dell) into 14.04, I had to blacklist i2c_hid.
After upgrading to 14.10, i needed to remove the blacklisting, as others
reported. Here is the interesting thing: I needed to blacklist two
different i2c
Same here. My 120Gb SSD just filled up. Good thing I'm an advanced user
and I could manage to find the offending folder. A newbie would just
need to give up. The harddrive analyzer would not give any info (maybe
because the disk was full).
In my case, it was unity7.log, which was about 50Gb.
Is
Hi Chris
Thank you for uploading the package. Unfortunately, I already upgraded
the machine where I had the crash to Utopic. I tried on another machine
running trusty, and both before and after enabling proposed (and
therefore upgrading to 0.93-3ubuntu0.1 ), pitivi loads just fine. So,
all I can
Another update. As of today, pitivi is not crashing anymore. I've been
running updates daily, though I didn't see remember having seen any
pitivi update. The changelog doesn't show any recent changes, either:
http://changelogs.ubuntu.com/changelogs/pool/universe/p/pitivi/
I guess some
Ouch, it might be the same issue. I don't have gnome-shell installed,
and installing the metapackage didn't enable a session in lightdm. The
Ubuntu (Unity) shell prouces the same crash. But sudo pitivi works
fine.
I'll look around to enable a gnome-shell session and try from there.
Thanks for the
Ok. It looks like running from the gnome-shell doesn't help.
This is what I added to my Kubuntu install:
* gnome-shell
* ubuntu-gnome-desktop
Now I can login to Ubuntu (unity), Gnome (gnome-shell, I believe), Gnome
Classic, KDE Plasma and others. Pitivi crashes in all of them, whether
from
I just tested installing the Unity package to see if a more typical
Ubuntu installation would not crash, but I had not luck. I'll gladly
help with testing if anyone has any ideas of what to try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I just upgraded to Kubuntu 14.04 (Trusty) yesterday, and pitivi stopped
working. It segfaults immediately, with the following stdout error:
lmilano@grisell:crash$ pitivi
Missing soft dependency:
- pycanberra not found on the system
- enables sound notifications when
** Attachment added: Apport crash report from /var/crash
https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1307746/+attachment/4083897/+files/_usr_bin_pitivi.1002.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- I just upgraded to Kubuntu 12.04 yesterday, and pitivi stopped working.
- It segfaults immediately, with the following stdout error:
+ I just upgraded to Kubuntu 14.04 (Trusty) yesterday, and pitivi stopped
+ working. It segfaults immediately, with the following stdout
Same here. I have a Dell Vostro A90 with a Minimal KDE install, and
lightdm as the DM, running 13.04 daily updates . It is set up to
autologin. In thefin last couple days, upon reboot, the computer comes
to a command line login. You can login, and then run sudo lightdm, or
sudo service lightdm
Confirmed! I launched BUM, and lightdm was not selected. I activated it,
rebooted, and everything is back to normal (the graphical login goes on
normally). Hope this helps!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same here. Patrick's workaround (thanks) wasn't quite enough. I needed
to run it on the python program
sudo apt-get install -o APT::Force-LoopBreak=1 python
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is still an issue in Oneiric. Here is my case:
* a computer with two hard-drives. One of the MBR of these is used to bottup
normally
* I introduced a USB stick with Kubuntu 11.04, booted from USB, and upgraded
to Oneiric (11.10)
After the upgrade, the MBR in the HD of the desktop
I just had another crash. Even though I had some success with the
migration, KMail sometimes freezes, folders take a long time to refresh
and show the contents of the emails, and this is the most recent crash
(I will install the debug symbols). Soprano is disabled right now, as it
tends to crash
And this is the standard output of the previous crash
lmilano@grisell:~$ kmail
[1] 3308
lmilano@grisell:~$ /usr/bin/kmail(3309) Soprano:
org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
And this is a new stack trace, now that I installed the debug symbols.
By the way, folks, help here is appreciated, but venting is
inappropriate. This is not a forum, but a bug tracker.
Thread 1 (Thread 0x7f878f9787a0 (LWP 3309)):
[KCrash Handler]
#6 deref (this=0x7f877f3c2bd8) at
So, here is a summary of the migration (see comment #18 above):
• it completed successfully after a long time (more than one hour for
about 20k emails on a 3core fast desktop)
• it added a new IMAP Google account/folder I didn’t have and seemed to
slow things down significantly
•
Thanks, Clay! I removed ~/.kde/share/config/kmail-migratorrc and re-
ran kmail-migrator --interactive. This time I got a the migration
tool to complete and show a succeeded check mark at the end. The
command line showed some errors or warnings. The message notification
widget showed a bunch of
Same here. I lost all my email settings. The migration failed in the
first login after the upgrade. I got a pop up asking me to run kmail-
migrator --interactive manually. But if I do, I get the following
error:
lmilano@grisell:config$ kmail-migrator --interactive
kmail-migrator(9148) main:
Hi Clint
Thanks for the changes in failsafe.conf, neat work! A ten second
countdown would probably give slightly better feedback to the user (but
it isn't essential or anything):
$PLYMOUTH message --text=Waiting up to 60 more seconds for network
configuration... || :
sleep 10
Yes, Damian, this is the same bug. To double check, you can temporarily
edit that file (using sudo), and add a # character in from of the ppp0
related lines. This should bring your boot time back to normal.
So, a couple questions, mostly because it's not clear who is affected:
1) have you ever
Clint: something to consider. How would people (except for advanced
users) fix their interfaces files? Can we provide a bash script
installed by default, that will allow people to quickly install a
vanilla interfaces files? It could also save a backup, and optionally
restore it with another
Jeremy: Could either a new bug for this issue be opened or [...]
Done!
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
** Description changed:
In certain situations, ubiquity writes an auto ethN line
/etc/network/interfaces. This means that the boot up process, including
- bringing up the X system by upstart, will be delayed for whatever grace
- period is defined in /etc/init/failsafe.conf . This is currently
Sorry for the typo in my last statement, the new bug report is bug
#847782
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/847782
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
I think this is mostly a duplicate of bug # 839595 . And the short of
it, is that upstart seems to be doing the right thing, but ubiquity
seems to be the problem.
A new bug report has been reported for ubiquity, bug #847782
--
You received this bug notification because you are a member of
Scott: it seems clear that a permanent connection in a machine needs to
be there, yes. However, it is assuming that any user who has ethernet
plugged in needs that. This seems dangerous, particularly because it
makes people have subsequent 3 minute boot up times. Why not just ask
the user? (and
Public bug reported:
In certain situations, ubiquity writes an auto ethN line
/etc/network/interfaces. This means that the boot up process, including
bringing up the X system by upstart, will be delayed for whatever grace
period is defined in /etc/init/failsafe.conf . This is currently 120
Clint: good point about annoying vs safer.
Overall, I don't think we know, at installation time, what the user
intends to do. In my case, for instance, I never intended to create any
static connection. Actually, I configured a DHCP ethernet connection. I
really had no intention of persisting the
** Description changed:
- In certain situations, ubiquity writes an auto ethN line
+ In certain situations, ubiquity writes an auto ethX line in
/etc/network/interfaces. This means that the boot up process, including
bringing up the X system by upstart, will be delayed for whatever
timeout
Thanks, Robert!
I will update the description, since this is very relevant. Basically,
the installer is always adding auto ethX to the interfaces file,
provided there is an ethernet connection at install time. This means the
problem will be much more widespread than we had thought. I think the
** Description changed:
- In certain situations, ubiquity writes an auto ethX line in
- /etc/network/interfaces. This means that the boot up process, including
- bringing up the X system by upstart, will be delayed for whatever
- timeout is defined in /etc/init/failsafe.conf (see bug 839595).
Clint, I'll give it a swirl. Where exactly do you add --verbose? Do you
mean to remove the quiet linux boot parameter? Or add splash=verbose
?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Will do. I assume you mean to run a grep on syslog right after I login
(or pls let me know otherwise).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
failsafe.conf's 30 second time out
Robert, Chris, I think you are both hitting also the other problem I
encountered, namely the fact that X is not starting until failsafe is up
(even though theoretically this should not be the case).
Could you please look at comment #21 by Clint and post the info he is
asking for as well? I will,
Clint. The biggest issues it that we are not sure, but it is plausible
that a large proportion of the existing systems will suffer a 2 minute
delay after the upgrade. How about we test this:
* remove the offending ethN line from /etc/networking/interfaces
* reboot
* connect the laptop/desktop to
Three is a crowd! I have 4 machines running kubuntu. Two started out
with regular CD/USB live image installed to disk. The other two were
installed from the netinstall mini-iso, connected to ethernet. These two
are the only ones where I see an auto ethN.
I also played in one of my machines
Yes, that's correct. Is that something that should not be there? Thanks!
santisofi@minime:~$ cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
Scott, is this how things are intended to work? My current understanding
is:
* pre-start exec sleep N means wait up to N seconds for the preconditions to
be satisfied. In this case, these are a network up and a fs up. I thought it
meant Wait at least N seconds, but I guess I was wrong.
* The
@ Scott: thanks for the detailed response. It all makes sense now. I am
guessing perhaps wicd wrote that entry in my interfaces file. I haven't
edited this file by hand.
@ Clint: yes, I think it makes sense to add this to the release notes.
Thanks for updating the description. It seems like this
.
Cheers
-- Leo
#!/bin/bash
#
# 2009, Leo Milano
#
# Credits: http://www.perlmonks.org/?node_id=11582
#
http://www.linuxscrew.com/2007/09/04/two-way-conversion-of-unix-time-seconds-since-1970-and-regular-time/
#
# Customize this if needed
log_file=~/boot_time.log
# A trick to make sure
Hi,
Just an update: Lightdm also gets penalized and waits the sleep time
declared in failsafe.conf before loading
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
failsafe.conf's 30
Hi
After installing this version of upstart is making, my netbook takes
extra 100 seconds to boot. CTRL-ALT-F1 shows me that that the network
security us being brought up. Any thoughts? Could this be a coincidence?
Boot time (as measured with a script) has regressed incredibly over the
last few
Oh yes, changing that value in failsafe.conf brings back the old boot times:
tried setting to 12 and then 1, and it definitely fixed things: ( I added the
//comments )
Wed Sep 7 17:13:34 PDT 2011. Boot Time [s]: 156 // Sleep 120
Wed Sep 7 18:59:59 PDT 2011. Boot Time [s]: 51 // Sleep 12
** Attachment added: dmesg for a boot with sleep = 1
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+attachment/2370271/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One more thought, just by looking at the script and the behaviour on my
system. The bug description states as far as I can understand, the 30
second sleep in failsafe.conf means that /etc/init/rc-sysinit.conf will
start within AT MOST 30 seconds of 'filesystem' and 'ifup lo' having
occurred.
It
Colin: do my logs shed any light? Let me point out that updates to grub
during the life of the distro did not ruin the MBR. It has only (and
consistently) happened when upgrading to a newer distro version.
With that in mind. Why don't we ask the user for confirmation before
writing to the MBR?
Hi Colin,
I am attaching the required info. Apparently I can only add one at a
time.
Thank you so much for looking into this. Cheers!
Leo
** Attachment added: sudo debconf-show grub-pc grub-pc.txt
** Attachment added: sudo cat /var/log/installer/partman partman.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110797/+files/partman.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: sudo cat /var/log/installer/syslog syslog.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110798/+files/syslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: df -h df-h.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110800/+files/df-h.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/496435
Title:
** Attachment added: sudo blkid blkid.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110801/+files/blkid.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/496435
Ok, I added all the info, I hope it helps. I took the liberty to add a
couple more useful outputs.
My computer boots from /dev/sdb , but I always keep a grub in /dev/sda
just in case. Both of them failed to load grub after the upgrade (I only
run grub-install /dev/sda every once in a while, I
I noticed a reference to a third partition in the grub-pc output:
grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD1001FALS-00J7B1_WD-
WMATV1484210-part3
Does this mean that the upgrade is trying to install grub on a partition
instead of the MBR? But, assuming that's the case, why does the old
Same here. My desktop system with 2 sata hard drives just rendered
itself unbootable after upgrading Kubuntu 10.10 - 11.04
As far as I can tell, Fix Released is not a proper characterization for this
bug's status, and this is a CRITICAL bug. I really don't mean to flame, but we
can't afford
Hi Jacob, All,
I restored (+r) to both binaries and Skype is still working fine. It
really seems to have been a regression introduced by ia32-libs (and now
fixed).
Good work everyone!
--
skype crashes after signing in
https://bugs.launchpad.net/bugs/646862
You received this bug notification
Here the workaround was enough to let me start skype but I had no audio
(mic/speakers) in skype. The new ia32libs restored audio, good enough
to complete a call (however I never undid the workaround, that is I
didn't restore the original file permissions)
--
skype crashes after signing in
I had the same crash, Kubuntu 64 bit, after upgrading from 10.04 to
10.10 beta. Removing all the obex related packages did the trick, many
thanks to Erdewit.
This is a really problematic bug. It would prevent networkmanagement
from working at all (the computer would not connect to the wireless
Same here, it hit me when upgrading from Kubuntu 10.04 to 10.10beta, on
an amd64 system with multiple sata drives. I had to boot from the live
image and chroot.
Shouldn't that part of a grub/system upgrade ask for user input, since
this is SO critical? This is a killer for non-experts!
--
*** This bug is a duplicate of bug 496435 ***
https://bugs.launchpad.net/bugs/496435
Hi
This is a duplicate of bug # 496435
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435
Cheers
Leo
** This bug has been marked a duplicate of bug 496435
upgrades of the grub-pc package can
Here is something encouraging.
This morning (May 9) I tried the xorg-edgers ppa again, and now the
crash on logout is gone. No workarounds, no mess. This is, again, in
Kubuntu/KDM.
If anyone wants to try, here are the instructions. From the command
line:
To install:
sudo add-apt-repository
Hi all
I just tested the hpcups driver from the proposed repository in my
system (Kubuntu Lucid, HP Deskjet F380), and the bug is fixed. I no
longer get the black background.
Great work everyone involved! Cheers,
-- Leo
--
/usr/lib/cups/filter/pdftoraster failed
Hi Till
I just tested the hpcups driver from the proposed repository in my
system (Kubuntu Lucid, HP Deskjet F380), and the bug is fixed. I no
longer get the black background. I will also post the good news in bug
539708.
Great work everyone involved! Cheers,
-- Leo
--
Printing on hp printer
** Attachment added: Screenshot of my printer config
http://launchpadlibrarian.net/47699568/printer-hpcups.png
--
Printing on hp printer has black background
https://bugs.launchpad.net/bugs/553573
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
With my hardware (ATI HD 3500), I get the black screen in Kubuntu with
the open source stack (radeon, etc). If I enable fglrx in the Hardware
Drivers section, the issue is gone. The latest packages from the xorg-
edgers ppa also produce the crash.
--
[RS480] black screen after a few user
Same behavior here, ATI open source driver, current Lucid, but this is
with KDM and Kubuntu. I'll probably try with a more current mainline
kernel.
--
black screen when switching between multiple X session
https://bugs.launchpad.net/bugs/529882
You received this bug notification because you are
Just to confirm, this is still happening in Lucid, Dell Mini 9 (Vostro
A90).
--
Black screen + freeze when suspending or hibernating with mounted SD Card
https://bugs.launchpad.net/bugs/464712
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same here, I needed the FRAMEBUFFER=y workaround.
Not that kubuntu-desktop _is_ installed here, but cryptsetup is not.
Meaning: if you don't know about the workaround, you won't get the
splash screen. Is this a packaging issue?
Thanks!
--
Hide console messages while Plymouth is running
I just printed an email from gmail, using Chrome, and I got a full page
in black. Solid black. This is using an HP F380 AIO. I tried again from
Adobe (a previously saved PDF), same problem. This is in Lucid. The same
printer works fine in Karmic.
--
hp printer prints totally wrong - non-text
Ouch. Too bad. I was going to ask what driver you were using :-). My
machine was using hpijs in karmic, and when I upgraded to Lucid it was
picked up as hpcups, which was not working fine. From the KDE System
Settings I reconfigured the printer to use hpijs (instead of the
_recommended_ hpcups),
I can confirm the fix here, too (Radeon HD3450, Kubuntu Lucid, KMS).
Great work!
I'll follow up in the smooth transition bug 540177
--
boot hangs on splash screen, doesn't switch to KDM
https://bugs.launchpad.net/bugs/538524
You received this bug notification because you are a member of Kubuntu
I'll provide feedbback for this, I am running Kubuntu Lucid + KMS with a
Radeon HD3450.
Right now, plymouth shows perfectly at shutdown. On boot up, though, it
only pops up _very_ late (about a second before KDM loads), and it's
only displayed for a fraction of a second.
Cheers!
--
KDM needs
@nerdy_kid: I believe this bug HAS been fixed, and I marked it as such
above. However, Lynx marked this as NEW again, and undid this.
I think the confusion has to do with what this bug is about, although it
was explained above by Jonathan in post #64. We need a new bug report
for the missing
I am not sure if I am in the right bug report, I found several similar
reports when trying to file a gub with ubuntu-bug. I have an R600 card
(Radeon HD3450). KMS has been working fine in Lucid, but the latest
update to plymouth killed it (boot up hangs at the plymouth screen).
This is Kubuntu
Thanks Scott, and sorry for the misreport.
--
plymouth broken on radeon 7500
https://bugs.launchpad.net/bugs/527083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Same here, I am trying to report a critical bung in plymouth. This is
the console output:
l...@grisell:~$ apport-bug plymouth
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such
file or directory
QFileSystemWatcher: failed to add paths: /home/leo/.config/ibus/bus
Wow! I am running latest Lucid and I just realized that policykit-kde is not
available for Lucid, either!
This is the behavior:
* policykit-1-gnome is installed
* If I open KPackageKit and select updates, I can install them with NO
authentication! (Is this expected?)
* If I install new packages
Has anyone tried in Lucid? The worlaround (acpi_enforce_resources=lax)
works here in Karmic, but it doesn't in current Lucid.
l...@grisell:~$ dmesg |grep lax
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-15-server
root=UUID=e1c15c83-23cf-4bfb-a043-ba9469332293 ro quiet splash
Ouch! Thanks Hernando!!! Yes, I can confirm that the workaround still
works (and it's still needed, unfortunately)
--
it87 (sensors) module broken, needs automatic adding of a kernel line during
installation
https://bugs.launchpad.net/bugs/418246
You received this bug notification because you
I just tested in latest Lucid, same issue. Is this a local problem in my
computer or a packaging issue? I don't really use Lubuntu, but I am
trying to help because I came across this bug and it seems like a
biggie.
--
unable to make /etc/lxdm/default.conf.dpkg-tmp a symlink to
Hi Julien,
Yes, that certainly works, the install script is missing the check for
/etc/lxdm
l...@grisell:~$ sudo mkdir /etc/lxdm
[sudo] password for leo:
l...@grisell:~$ sudo apt-get install lubuntu-default-settings
Reading package lists... Done
Building dependency tree
Reading state
Public bug reported:
Binary package hint: lubuntu-default-settings
In the latest upgrade of lubuntu-default-settings for Lucid (version
0.5), I got the error described in the bug report summary. Uninstalling
and re-installing didn't help. It seems to be a missing target for a
symlink. Here is a
1 - 100 of 193 matches
Mail list logo
