I'm seeing similar behaviour too - on a Ubuntu 14.04.4 box, completely
up to date. I just had it freeze, which marks the third or fourth time
I've either had to Magic-SysRq it, or pull the power, since the Badlock
date.
The box has "plenty" of RAM (it was recently upgraded from 8GB to 16GB
in
Public bug reported:
I have some cron.daily jobs which output in UTF-8 (due to doing file
operations on /etc which contains some files with UTF-8 characters).
These are run through Anacron and emailed through the Mandrill mail
service. Because there's no Content-Type headers sent with these,
I just tried this version of byobu on a system and it seems to work
fine, my .irssi screen session (started @reboot) is ignored by byobu and
I get dropped straight into the normal byobu shell with my normal
windows, .irssi is ignored. Thanks Dustin!
--
You received this bug notification because
Sorry, no, I think this is a terrible idea.
Sent from my iPhone as above at least has some use in that it's a
sort-of implied apology for an otherwise rudely short, misspelt, jumble
of thoughts masquerading as a real email. However even this I find
annoying and offensive when compared to a
Public bug reported:
Binary package hint: software-center
I've got the elementary theme on from a PPA (I think I did this under
lucid before upgrading to Maverick), and the Ubuntu logo on the
Applications menu obviously gets replaced. However, this seems to
replace the Ubuntu logo in other
** Attachment added: Screenshot of Software Centre
https://bugs.launchpad.net/bugs/639787/+attachment/1589710/+files/Screenshot.png
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/639787/+attachment/1589711/+files/Dependencies.txt
--
Ubuntu logo is replaced by
I seem to be getting the same problem. There are no symptoms explained
above, so let me tell you what happens to my machine:
Occasionally on suspend and resume, Network Manager won't connect to wireless
networks, and if I try to do so manually then it just says device not ready
under the
I've been seeing similar behaviour for a few days, various display
issues with the indicator-applet and notification-area-applet. I've
attached a screenshot I took yesterday where the indicator-applet was
showing some rendering issues, and also my Network Manager icon wasn't
showing in the
I haven't tried reinstalling Ground Control to replicate the bug after
removing it in my last report, if that's what you're asking.
If you or doctormo would like me to do so and test it, I can do this for
you however.
--
nautilus crashed with SIGSEGV in PyThreadState_New()
I'm getting this error too (bluetooth-applet crashing when I disable the
BT adapter) on my Toshiba Portege A600. It brings up a window explaining
that apport can't collect data about assertion crashes, but if someone
explains the steps to get some useful information I will do so as it's
100%
OK, I just tried following the Valgrind instructions I missed above.
However, this time, bluetooth-applet started OK, and I was able to turn
Bluetooth on and off via the applet with no crashes.
I've attached the log anyway in case it's useful, but please note that
this is actually a successful
I can't get it to crash with Valgrind, I've tried:
reboot - disable BT - applet crash - start with Valgrind from CLI -
disable/enable BT
and also
reboot without applet enabled - start with Valgrind from CLI -
disable/enable BT
both of these scenarios worked OK. However as soon as I put the
Here also after resuming from hibernation and on wireless (so could be
related to NetworkManager not connecting quickly enough?). I haven't
tried with a staticised eth0 configuration and a cable plugged in to see
if removing NM from the equation improves things at all.
Toshiba Portege A600, fully
I just got this error immediately after logging into my up-to-date Lucid
machine.
--
desktopcouch-service crashed with SIGSEGV in memmove()
https://bugs.launchpad.net/bugs/542295
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Just upgraded my Karmic x64 laptop to Lucid Alpha 2 and getting this
problem also. It's not signing me out of MSN, just flashing up the error
and then seems to continue as normal, has happened twice so far this
morning with no action on my part (I haven't sent any messages, added
any contacts,
I got this message with Evolution running, but not Gwibber. I was simply
reading an email while Evolution was fetching mail in the background, I
don't know what caused it to crash.
--
desktopcouch-service crashed with RuntimeError in find_pid()
https://bugs.launchpad.net/bugs/517458
You received
This appears to be related to the UPX compression used by Hamachi
(/usr/bin/hamachi is a UPX-compressed executable). A workaround
(although not really a fix, as this shouldn't be necessary) is:
1) sudo aptitude install upx-ucl
2) sudo upx -d /usr/bin/hamachi
This will restore Hamachi to its
Also affects me on a Toshiba Portege A600 running the Karmic RC (been
running and upgrading roughly since the beta release but haven't
upgraded for a day or two). Attached are my gpm.log and a list of power
related packages on my system.
** Attachment added: gnome-power-manager --verbose log
Here's the second attachment, I couldn't see a way to attach two files
to a single comment. I should also have told you I'm on the AMD64
release.
** Attachment added: Power related packages on my system
http://launchpadlibrarian.net/34312891/powerpkgs.txt
--
Computer suspends immediately
*** This bug is a duplicate of bug 425411 ***
https://bugs.launchpad.net/bugs/425411
I've recently come across another bug which I *think* this may be a
duplicate of, #425411
I don't know for certain yet because I don't tend to think about whether
I have the laptop plugged in or not but this
It now seems that this may not be an xchat problem. I happened to notice
yesterday that when I started my laptop up there was a little flicker,
almost as if gnome-panel had been killed and then restarted instantly.
If I do this manually (with killall gnome-panel gnome-panel from a
terminal) then
Public bug reported:
I don't turn off my laptop, instead I have hibernation set up on lid
close and working. However, sometimes when I resume my laptop (by
opening the lid, on my model of Toshiba this automatically powers the
laptop on) it gets as far as the Gnome screensaver unlock dialogue box,
I'm getting this too, although only occasionally, and only ever after a
successful resume from hibernation. I've never had the screen go blank
unexpectedly or the Session active... message during normal use.
--
Session active, not inhibited, screen idle notification after screen blacks
out
Public bug reported:
Binary package hint: xchat
As a constant IRC user, I set Xchat up to start automatically when I
login (using System-Preferences-Startup Applications). This was
originally done on my Jaunty install which I recently upgraded to Karmic
beta. Since the upgrade, now when I login
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33232468/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33232469/XsessionErrors.txt
--
xchat tray icon doesn't appear if xchat is in Startup Applications
Public bug reported:
Binary package hint: seahorse
I just looked for a colleagues PGP key in order to add it to my keyring
as a test. While I found his key OK, it seems to be being parsed badly
by seahorse.
His key is of the format:
Firstname Lastname (Firstname Lastname) a.n.ot...@domain.com
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24546870/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/24546871/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/24546872/ProcStatus.txt
--
misformed
[EMAIL PROTECTED]:~$ apt-cache policy traceproto
traceproto:
Installed: (none)
Candidate: 1.1.2beta1-4
Version table:
1.1.2beta1-4 0
500 http://gb.archive.ubuntu.com hardy/universe Packages
I'm a bit confused now, since apt reckons I don't have it installed but
it's definitely
** Attachment added: diff -urN between original Ubuntu traceproto script, and
working one
http://launchpadlibrarian.net/15578558/traceproto.patch
--
Traceproto looks for traceroute in the wrong location
https://bugs.launchpad.net/bugs/242918
You received this bug notification because you
Public bug reported:
When running traceproto, an error is given reading:
exec: 120: /bin/traceroute: not found
This is because traceroute on a Ubuntu system (this is Hardy with all
current packages from -updates and -proposed) is in /usr/bin/traceroute.
Editing the traceproto shell script by
Public bug reported:
I've had a Ubuntu Hardy beta system running well for a week or so, and
today I wanted to try KDE4. I did sudo aptitude install kubuntu-
kde4-desktop and got it installed fine. When I logged in, things seemed
OK, but I wanted a smaller panel. I right clicked, set the panel to
** Attachment added: Screenshot of wrapped around display.
http://launchpadlibrarian.net/13027296/wraparound.png
--
Bottom rows of display wrap around to top
https://bugs.launchpad.net/bugs/210368
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Yep, just checked my bash_history, and it looks like the steps to fix it
are just to manually run a sudo /etc/init.d/vboxdrv start afterwards
(to create the /dev/vboxdrv device with the right permissions now that
the group exists), and then add accounts to the vboxusers group
manually.
Since I
Unfortunately this is a machine in my office which I've now left for the
weekend. When I ran grep vboxusers /etc/group after getting back to
the command line, it told me the group existed with GID 119, but had no
members. I worked out that the reason /dev/vboxdrv didn't exist is due
to the module
Public bug reported:
Binary package hint: virtualbox-ose
Setting up virtualbox-ose-modules-2.6.22-14-generic (6) ...
* Starting VirtualBox kernel module vboxdrv
chown: `:vboxusers': invalid group
* Cannot change owner vboxusers for device /dev/vboxdrv.
Now seems to be fixed after I received a linux-restricted-
modules-{generic|386} upgrade on the 8th of November.
--
Atheros support isn't working in 2.6.17-10-generic
https://launchpad.net/bugs/68139
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: linux-restricted-modules-generic
I upgraded from Dapper to Edgy yesterday (I figured with the release
being imminent, it should be fairly bug free). The upgrade went well, I
was provided with -386 and -generic kernels as I hadn't got round to
removing
** Attachment added: output of modprobe ath-pci as root
http://librarian.launchpad.net/4935024/ath_pci
--
Atheros support isn't working in 2.6.17-10-generic
https://launchpad.net/bugs/68139
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: output of dmesg | grep ath_pci
http://librarian.launchpad.net/4935026/ath_pci_dmesg
** Tags added: edgy madwifi
--
Atheros support isn't working in 2.6.17-10-generic
https://launchpad.net/bugs/68139
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Since originally getting this bug, I've done a fresh install of Dapper
and have upgraded to kernel 2.6.15-25-686 (sky2 ver 1.4) and I'm still
having the same problems. Same also happens with 2.6.15-15-386 (also
sky2 1.4). Are there any other fixes for this bug in the pipeline?
--
sky2 ethernet
40 matches
Mail list logo
