I was suffering from what I think is the same problem with interpid
8.10, but followed the advice here to get the latest version of
Transmission:
http://forum.transmissionbt.com/viewtopic.php?f=13&t=5604
First edit the config file with a command like this:
gksudo gedit /etc/apt/sources.list
The
OK I agree it is low priority (given you have to try and run the
resulting download afterwards) but given it is a very simple fix that
also would work on the Ubuntu patched version of 0.132, then why not?
--
Pan saves some files as executable
https://bugs.launchpad.net/bugs/374097
You received th
*** This bug is a security vulnerability ***
Public security bug reported:
This is a report of a serious security problem I found with pan 0.132,
it affects all releases Ubuntu including 9.04 (and also with Pan 0.133
as shipped with Fedora-10).
The problem is that Pan obeys the original yEnc sta
Changed visibility back to private, as maybe less trouble all round if
Ubuntu fixes it as an package update, rather than lots of folk trying
this themselves.
** Visibility changed to: Private
--
Pan saves some files as executable
https://bugs.launchpad.net/bugs/374097
You received this bug notif
I have exactly the same problem as described by swulf wrote on
2009-01-17. How to fix it, with no gconf key present?
And just who thought you could compse and send an email in 30 seconds!?
Please step foward and explain...
--
F-Spot deletes temporary image files too early when sending mails
http
Just found all of you have the same problem as I have just seen on my
8.10 system (32-bit OS, but 64-bit AMD CPU). No crash report, but
/var/log/auth.log has this:
paul-ubuntu sudo: pam_unix(sudo:auth): authentication failure; logname=
uid=0 euid=0 tty= ruser= rhost= user=paul
So clearly lacking
Public bug reported:
Binary package hint: usplash
When booting 9.10 there are times when fsck runs, either following an
unclean shut down or periodically. With 8.10 the results were logged to
/var/logs/fsck/checkfs (or checkroot) and you could view them
afterwards. With 9.10 these files are not u
** Attachment added: "report.tar.gz"
http://launchpadlibrarian.net/39031186/report.tar.gz
--
fsck not logged
https://bugs.launchpad.net/bugs/520120
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Seeing the same thing on my PC with fresh 10.04 install on an ext4
partition on Areca HW RAID card.
$ sudo hwinfo --bios | grep Socket
Socket: "J3E1"
Socket Type: 0x01 (Other)
Socket Status: Populated
Location: 0x00 (Internal, Not Socketed)
Location: 0x00 (Internal, Not Sockete
Getting time outs as well. Come on, who is in charge of the key server?
Why is there not a system of falling back to a 2nd server when the
primary is down?
--
keyserver.ubuntu.com down all time - (110) Connection timed out
https://bugs.launchpad.net/bugs/435193
You received this bug notification
OK worked now, but why the problems?
--
keyserver.ubuntu.com down all time - (110) Connection timed out
https://bugs.launchpad.net/bugs/435193
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
Seeing it as well with fresh 10.04. I also have the problem (twice
today) of the display not coming up when booting, it changes (I assume)
to graphics mode shortly after the grub2 menu and my monitor goes in to
power saving. Trying Ctrl-Alt-F1 to go to text log-in had no effect, but
Ctrl-Alt-Del re
Two points I would like to add:
(1) Why should the art theme be able to override any (possibly
important) messages from other packages that need to communicate at
boot/shutdown? That seems to be a dumb option.
(2) I have a similar problem with plymouth where it normally shows the
progress of my b
Public bug reported:
Binary package hint: mountall
When testing the automated check of file systems with 10.04 LTS release
version, it seems that mountall 2.14 is going through all entries in
fstab and trying to check all of my CIFS mounts with and
set to zero, generated warnings in boot.log ab
Appears fixed in 10.04 release, now you get prompted for your (sudo)
password.
--
System Monitor crashes when lowering nice value of process
https://bugs.launchpad.net/bugs/206583
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
I have tried the patch from Arand's "unstable" PPA and it seems to work
fine, went quickly to 100% on my ext4 partition after forcing a test
with 'sudo touch /forcefsck'
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notif
Tested again with updates from Arand's unstable PPA for plymouth and
mountall (though mountall --version still says 2.14!?) and it still
complains about CIFS mounts when I forced a check of file systems:
sudo touch /forcefsck
boot.log shows:
fsck from util-linux-ng 2.17.2
/dev/sda7: 169050/32
This seems to be something to do with mountall, not usplash, as it is
still there in 10.04 which uses plymouth for bot splash screens. See
also my Bug #575293 and comments to Bug #571707
--
fsck not logged
https://bugs.launchpad.net/bugs/520120
You received this bug notification because you are
Another reminder that this should be patched! We are now on 10.04 LTS
release, have gone from 0.132 to 0.133, so it seems daft to *still*
allow malware to be saved with execute permissions!
--
Pan saves some files as executable
https://bugs.launchpad.net/bugs/374097
You received this bug notifica
Public bug reported:
Binary package hint: plymouth
Testing 10.04 release i386 on my machine and I found that adding
radeon.modeset=0 to the /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT
parameter was needed to stop the occasional 'blank screen of death'
where on booting the ATI card is put in to a
Recently I found that my D300s "just worked". I assume this is due to
some kernel patch for the USB stack, has anyone else have this
experience?
--
Fspot reports error for importing Nikon D80
https://bugs.launchpad.net/bugs/191316
You received this bug notification because you are a member of Ubu
Recently my D300s "just worked" with F-spot. Maybe due to some kernel
patch, anyone else seen an improvement in the last month or two?
--
error importing photos in ptp mode
https://bugs.launchpad.net/bugs/74279
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
To add to this, the recent kernel update (I assume?) for 9.10 broke it
again for my D300. It is seen as present as an MTP device, but now it
only works if I connect with the XP VM first, then F-spot is OK. I am
not sure if the camera appears on the desktop (i.e. mounted) but will do
some more tests
Nope, I was wrong, it is still there :( It might relate to the D300s
configuration, going back from two memory cards to just the CF one
prompted similar error messages, but re-trying the camera switch made it
operate.
--
Fspot reports error for importing Nikon D80
https://bugs.launchpad.net/bugs/
I also want to know if this can be applied to 9.10?
I have an automatic back-up script that depends on /tmp being cleared at
booting to cope with the machine being switched off mid-backup, so it is
more important to me than just avoiding the build up of general
detritus.
--
/tmp is not cleaned w
It seems my system has been updated to 2.15 but there are still the odd
warnings about CIFS mounts in fstab
Also the stage 2 of 3 pass had no text on the plymouth screen, but it came back
for stage 3 of 3.
--
mountall trying to check mounts with pass=0
https://bugs.launchpad.net/bugs/575293
You
Well, after installing VMware the message came back, but then went
again! It comes and goes randomly as far as I can tell, not sure if that
points to an uninitialised flag or something.
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this b
Trie3d a fresh 10.04 installation on another machine, with ext4 for /
and /home but no problems on the motherboard SATA connected HDD.
I am now wondering if it is related to the ARC-1200 2-Port PCI-Express
to SATA II RAID Controller (appears as SCSI disk device), unfortunately
I don't currently ha
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: plymouth
Testing 10.04 release i386 on my machine and I found that adding
radeon.modeset=0 to the /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT
parameter was needed to stop the occasional 'b
apport information
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/48594743/CurrentDmesg.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
apport information
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/48594744/Dependencies.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
apport information
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/48594745/Lspci.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
apport information
** Attachment added: "Lsusb.txt"
http://launchpadlibrarian.net/48594747/Lsusb.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
apport information
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/48594789/ProcCpuinfo.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
apport information
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/48594791/ProcModules.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
apport information
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/48594790/ProcInterrupts.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/48594792/UdevDb.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/48594793/UdevLog.txt
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Unrelated, but out of curiosity, does anyone know what is the message
"This is not a genuine Ubuntu package" is due to?
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It looks like this is not a F-spot error, but a libgphoto2 one. I tried
installing gthumb and it can't read the D300s camera either. It reports "An
error occurred in the io-library ('Unspecified error'): No error description
available".
What is also interesting is that the trick of having both C
I believe this could be related to bug #74279 that I have been complaining
about for some time. I tried the above commands with my Nikon D300s with just
the CF card installed (causes F-spot to fail) and the first time I ran the
command I got this:
Is this problem, like bug #74279, in fact due to bug #301731 in the
libgphoto2 library?
--
Fspot reports error for importing Nikon D80
https://bugs.launchpad.net/bugs/191316
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I added http://ppa.launchpad.net/arand/unstable/ubuntu to get the fix
for plymouth/mountall running fsck and taking ages when run at boot
time, not sure if it is now fixed mainstream though.
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received t
Is it worth reverting to the official packages? How would I do that, as
simply un-ticking the unstable repository and then checking for updates
has not resulted in any proposed changes, etc.
--
plymouth text messages fail with radeon.modeset=0
https://bugs.launchpad.net/bugs/575808
You received t
Trying to install a 'lower' version of plymouth did not work, I got this
message:
>The following packages have unmet dependencies.
> plymouth: Depends: libplymouth2 (= 0.8.2-2ubuntu2) but 0.8.2-2ubuntu3~ppa1
> is to be installed
And an attempt to update (downgrade) libplymouth2 resulted in a se
OK, that last command worked (with libplymouth2=0.8.2-2ubuntu2) and it
has changed some things!
First, the test is back to 'normal size' not the VGA bulked-up manner,
which is good.
Second, the text from my back-up script is going to the expected place
on the screen, which is also good.
But...th
OK, the problem is due to the unmount failing on /net (due to an autofs
entry?) and when trying it segments and I guess failed to unmount the
next files system which was /home
Of course, I can't find any log messages about this, and only a bug in
plymouth revealed it unexpectedly!
So no problem i
WTF? Yes, I did not use the movie player's screenshot, but assumed that
Alt+PrintScreen would capture the screen. How naive was that, it worked
until I closed the player and then the picture went!
Attached is (hopefully) a usable picture.
** Attachment added: "Screen shot of shutdown"
http://l
OK, failed to appreciate that Alt+PrintScreen did not actually capture
the screen! Hopefully this image shows it properly.
** Attachment added: "Screenshot taken from video of reboot"
http://launchpadlibrarian.net/48674720/Screenshot-MVI_1720.AVI-1.png
--
file system not clean after reboot
ht
OK, I installed the plymouth-theme-ubuntu-logo package and it is now
without any text at all. Not even the intended messages!
At boot-up there is a brief flash of something odd, but nothing now at
reboot. Attached is the single frame out of the camera's video clip
showing the boot-up oddity.
If y
I posted a bug report for gphoto2 here
https://sourceforge.net/tracker/?func=detail&atid=108874&aid=3004614&group_id=8874
and get the reply that the underlying reason is the gnome gvfs-gphoto2
-volume-monitor.
Sure enough, if I attach the D300s I can't open it with F-spot, but on
killing gvfs-gpho
Public bug reported:
I have a new 10.04 LTS install placed in a fresh ext4 partition
(root-10.04 label) with an older /home partition mounted in fstab from
my 8.10 installation (ext3), but each time I reboot I see the following
sort of message in boot.log:
root-10.04: clean, 169160/3227648 files,
It also happens after a shutdown and boot-up, so it is doubly serious.
--
file system not clean after reboot
https://bugs.launchpad.net/bugs/580059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
No this is STILL BROKEN with 10.04!
Connect a D300s with single CF card and no auto-launch, manually launch F-spot
and the camera is listed from the import options, but you get "Unspecified
error" dialogue box if you try.
Connect a D300s with both CF and SD cards and it auto-launched F-spot, and
This seems to be the same problem as
https://bugs.launchpad.net/debian/+source/f-spot/+bug/74279
What is more, it is not fixed in 10.04 and has been open for 3.5 YEARS now!
--
Fspot reports error for importing Nikon D80
https://bugs.launchpad.net/bugs/191316
You received this bug notification be
Apologies for the discussion, will keep them in future to the forums.
The issue about photo persisting is a question of magnitude, as they are
open already for a short time, so this is not a new break in
security/privacy, but making it a little less. Those needing the patch
(e.g. Thunderbird) woul
Just checked, and find that the /tmp directory is 755 permissions as I
mentioned, but the enclosed files are 600 permissions, so on my Ubuntu
10.04 box another user cannot actually read my F-spot created files.
This is better than the default 755/644 permissions on directories/files
normally used!
Will this fix be included in the 10.04 version? It looks like a simple
thing to back-port and some folks on 10.04 as "LTS" could be facing it
for some years...
--
F-Spot deletes temporary image files too early when sending mails
https://bugs.launchpad.net/bugs/112684
You received this bug notific
Reading this post:
http://mail.gnome.org/archives/gvfs-list/2009-May/msg1.html
It suggests the reason for this problem is that F-spot should be using the
gvfs-gphoto2-volume-monitor as its import path, not going to the libgphoto2
directly. Can anyone in the F-spot team comment?
--
Fspot rep
>From this bug report:
https://sourceforge.net/tracker/?func=detail&atid=108874&aid=3004614&group_id=8874
It appears the problem I am seeing is a basic compatibility issue between
applications using libgphoto2 for camera access (such as F-spot), and the
gvfs-gphoto2-volume-monitor daemon. See als
Sounds a bit like bug #301731 and/or bug #74279 that I have been ranting on
about, and also here:
https://sourceforge.net/tracker/?func=detail&atid=108874&aid=3004614&group_id=8874
and here:
https://bugzilla.gnome.org/show_bug.cgi?id=619538
** Bug watch added: SourceForge.net Tracker #3004614
Brian, what was in the reject log file?
Martin/Sebastian, just to add that, while wanting this ported to 10.04,
think it might be best not to port it to 9.10 partly due to bug #478392
but also that it is not a LTS version.
--
F-Spot deletes temporary image files too early when sending mails
http
Brian, if you delete the first 14 lines of the patch it applies in 9.10
(my home PC just now), but my attempt at building the unpatched f-spot
resulted in a program that did not quite work.
** Attachment added: "Building then failed attempt to run F-spot on 9.10"
http://launchpadlibrarian.net/4
Nope, deleting lines stops error message, but did not actually patch.
--
F-Spot deletes temporary image files too early when sending mails
https://bugs.launchpad.net/bugs/112684
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
I got mine working by using these steps:
mkdir /tmp/f-spot
./configure --prefix=/tmp/f-spot --disable-scrollkeeper
make
make install
I then tried to make the 9.10 version by manually applying the changes and then
creating the debdiff file. It seems to work, but not quite as anticipated. In
part
Looking back to the original complaint, this has not been fixed. The "change of
perspective" acts like opening a 2nd email and removes the temp files. I
suspect this is some automatic clean-up associated with the temp file name
creation, but as I just mentioned, I don't known much about .net/mon
Nope, I am talking nonsense! What I was seeing was a file such as
/tmp/tmp1b005b6b.tmp..jpg that was being removed, but of course the attached
files are in directories such as /tmp/tmp15e7b6a9.tmp/dcp_1144.jpg which are
now left to the OS to clean up.
So it works, panic over :)
--
F-Spot delet
No, it is the same changes, but made on a 9.10 system's files and
recreated as a patch. To build a version to test, you need to do
something like this (assuming you have not got this far already):
mkdir /tmp/f-spot
mkdir ~/f-spot-build
cd ~/f-spot-build
sudo apt-get build-dep f-spot
apt-get sourc
I have the same problem with a new Nikon D300s camera, both on my main
desktop machine (Intrepid 8.10 with F-sport 0.5.0.3) and with my new
laptop (Dell Latitude 2100 with Jaunty 9.04). Attached is the --debug
log from my desktop case, just for info.
** Attachment added: "f-spot debug output"
h
Same problem of PTP "unspecified error" on a new Nikon D300s camera with
8.10 and 9.04 Ubuntu. Some other cameras (Olympus compact) just work,
but not this one or, it seems from the above, quite a few SLR models :(
Why has this bug not been fixed for 3 years now!?
--
error importing photos in ptp
Just to add that gThumb has the same sort of problem with the D300s,
giving the error message "An error occurred in the io-library
('Unspecified error'): The supplied vendor or product id (0x0,0x0) is
not valid."
--
Fspot reports error for importing Nikon D80
https://bugs.launchpad.net/bugs/19131
OK, to further add to the confusion, I tried to connect my D300s to to a
XP VMware machine, that resulted in it attempting to read the camera
(after a few Gnome messages about being unable to lock it) and then the
XP VM did the BSOD and rebooted! After that XP seemed uninterested in
the camera, but
Forgot the attachment...
** Attachment added: "f-spot debug log after XP attempt"
http://launchpadlibrarian.net/33904875/f-spot-2.txt
--
Fspot reports error for importing Nikon D80
https://bugs.launchpad.net/bugs/191316
You received this bug notification because you are a member of Ubuntu
Bug
Dear Arijit,
Many thanks for reporting this issue and providing a fix. I have applied your
patch to the GIT repository on Sourceforge but I don't know how long it will
take (if ever) to get included in the version distributed with 14.04
Regards, Paul
--
You received this bug notification becaus
I am seeing the same sort of bug on my machine.
msi X470 motherboard (just tried latest firmware - no change)
AMD Ryzen 5 2400G and Ubuntu 18.04
Linux paul-ubuntu 4.18.0-25-generic #26~18.04.1-Ubuntu SMP Thu Jun 27 07:28:31
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Sometimes it happens overnight whe
Public bug reported:
Trying to install 18.04.2 on to existing assembled RAID system. Got to
the grub installation phase and it then generated an error dialogue
window saing it could not install to /dev/sda /dev/sdb (the usual for
RAID) but none of the alternatives in the radio button choice actual
I am seeing this with 64-bit 14.04.5 (even though 'grheard' did not have
this problem with 14.04) using OpenVPN via the network manager. Seems to
happen independently of DHCP renewals as several were logged before this
last bit:
Feb 23 19:31:03 paul-ubuntu dhclient: DHCPREQUEST of 192.168.1.100 on
Generally me work-around so far has been to avoid systemd!
However, where that is not an option you might be able to edit
/etc/default/watchdog so the module is loaded on watchdog start-up. It is not
ideal as you might have some other reasons for wanting the /dev/watchdog
virtual file to be test
Public bug reported:
I noticed that Firefox is keeping site-specific information even after
using the 'Clear Recent History' option. For example, with a new firefox
profile (e.g. start a guest session) go to www.youtube.com and view some
video, then look in the location:
~/.mozilla/firefox//stora
Forgot to add the system details:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename: trusty
$ apt-cache policy openvpn
openvpn:
Installed: 2.3.2-7ubuntu3.1
Candidate: 2.3.2-7ubuntu3.1
Version table:
Forgot to add the system details:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename: trusty
$ apt-cache policy openvpn
openvpn:
Installed: 2.3.2-7ubuntu3.1
Candidate: 2.3.2-7ubuntu3.1
Version table:
I am seeing this occasionally, today when disconnecting from a hung VPN
session. I was seeing message such as:
nm-openvpn[1832]: RESOLVE: Cannot resolve host address: :
Temporary failure in name resolution
In syslog which may, or may not, be related to the resulting crash.
It might also be relat
It might be appearing now as Bug #1577433 due to some change in malloc()
reporting text. I also see this and would like it fixed as memory
allocation bugs in OpenVPN are potential security vulnerabilities.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
If it was fixed in 8.12.0-1ubuntu3 why am I still seeing this on a
16.04.2 system with:
apt-cache policy rsyslog
rsyslog:
Installed: 8.16.0-1ubuntu3
Candidate: 8.16.0-1ubuntu3
Version table:
*** 8.16.0-1ubuntu3 500
500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
*** This bug is a duplicate of bug 1575572 ***
https://bugs.launchpad.net/bugs/1575572
I don't think this is a duplicate of bug #1575572
I am seeing this problem on an Ubuntu 16.04 machine that has the update "This
bug was fixed in the package init-system-helpers - 1.29ubuntu2" mentioned as
As for the previous case (my comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499089/comments/4)
this is an important application for us, and having the VM86 option
possible is pretty much essential for the machine to be usable in out
real-time case.
--
You received this bug notifica
We were seeing this on a fresh Ubuntu 16.04 64-bit installation using
fixed IP addresses and automounter for NFS drives. The suggestion #7
seems to fix it for use, but it would be useful to know just what is
happening with the script. Is it trawling through some user's home
directory when expanding
I will try to look tomorrow or so at the proposed fix.
Have you checked if it is still loaded OK following a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't st
Same problem as Ferdinand, scanner not recognised by xsane when on USB 3
port (but seen by lsusb) but worked when put on USB 2.
One USB3:
$ lsusb
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6
Thanks Robie for the quick reply, but I though 10.04.4 LTS would have
such bug-fixes included?
After all the ISO used to install is from after the date of the fix, and
the major package numbers are the same (comment #1 mentions 1:4.2.4p8
+dfsg-1ubuntu4 and my machine is reporting 1:4.2.4p8+dfsg-
In my case crash was gnome-panel but same message "gnome-panel assert
failure: gnome-panel: ../../src/xcb_io.c:385: _XAllocID: Assertion `ret
!= inval_id' failed." so I guess its the same bug.
Running 10.04 LTS 32-bit on AMD CPU.
--
You received this bug notification because you are a member of
I built a version of pptp with debug enabled, and caught the
segmentation fault again. This time I get the following in the syslog
file:
{{{
Nov 16 23:07:33 paul-ubuntu pptp[5592]: nm-pptp-service-5464
log[decaps_gre:pptp_gre.c:414]: buffering packet 1323 (expecting 1322, lost or
reordered)
Nov
Still broken on 12.04.5 recently updated:
$ apt-cache policy ureadahead
ureadahead:
Installed: 0.100.0-12
Candidate: 0.100.0-12
Version table:
*** 0.100.0-12 0
500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
100 /var/lib/dpkg/status
$ uname -a
Linux psc
Similar problem with 12.04 x64 system, shows it with "Error: The status
of this extension is unknown"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309985
Title:
nlpsolver doesnt work with libre of
This is also happening with the latest supported kernel on 14.04 LTS. We
are seeing various repeated messages of "Request for unknown module key
'Magrathea: Glacier signing key:
6fca287c2573d09ca32c1980c0d763777a63d4f5' err -11" on some, but not all,
machines running this. I guess it relates to the
Exactly! This is not Windows - we should not be pestered incessantly by
something like this because we might have done some update as part of a larger
number that needs a reboot, but we have a good reason for not doing so for some
time (running jobs, remote users also logged in, etc).
At most, i
Public bug reported:
In Ubuntu 14.04 the update manager will pop up telling you a restart is
required for certain types of update (kernel, etc). However, it defaults to
"restart now" which is unsafe, as an accidental with that pop-up in
focus will try to reboot your machine, and that might be
This is still broken with 14.04 and the same patch seems to work:
$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
$ apt-cache policy grub2
grub2:
Installed: (none)
Candidate: 2.02~beta2-9ubuntu1
Version table:
2.02~beta2-9ubuntu1 0
500 http://gb.archi
Public bug reported:
Today I found the update manager pestering me once again to restart the
system (stupid, since I already know about certain past updates and do
not want to do that just now). However, when I checked for anything new
using "apt-get upgrade" it was telling me about 7 more package
I agree with Daniel, having a machine randomly reboot on you because of
a fault in GUI design is pretty serious, same as if the kernel
occasionally panicked when you happened to be typing. Any ideas of time-
scale to the patch being pushed out?
--
You received this bug notification because you ar
1 - 100 of 310 matches
Mail list logo
