Having read the page on phased updates I can see the rational behind that.
However, it is still a broken GUI in my view because it is not telling you the
whole story. You are told one thing by the GUI and another if you look at the
package status vit apt-get or similar.
Would it not be better to
Thanks Brian, will look out for that!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1421044
Title:
Too easy to accidentally restart computer when 'restart to complete
update' box pop up
To manage
My suggestion is to (ideally) have the later version back-ported to
10.04 so this problem is not an issue for the remaining 1.5 years or so
of "long term support" for such servers, or to make sure Oracle uses the
older style of compression so the package is usable.
--
You received this bug notifi
Public bug reported:
Running a 10.04 LTS machine (32-bit) and it seem that the oracle-
java8-installer now uses the more recent compression option that is not
supported by the version of dpkg that is currently used by 10.04
Indirectly this is a security risk as java is well known for
vulnerabilit
Public bug reported:
I have a system with two main HDD configured as several md RAID-1 devices and I
installed the 32-bit version of 12.04.2 on to one of these partitions (using
the "alternate installer" ISO), with most of the others being user data (e.g.
one for /home, another for virtual mach
Why might it be a mdadm problem?
All of the md devices are up and accessible from the 64-bit OS, and the
/etc/mdadm/mdadm.conf file appears to match the output of the command ' mdadm
--detail --scan' suggesting it is correct. Even if I mount the previous 32-bit
systems root partition (that just
Ah - my apologies for not having this logged under 'grub2' as I had just
accepted the launchpad suggestion which, I'm guessing, was based on the
bug title.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
:)
For the record:
$ apt-cache policy grub2
grub2:
Installed: (none)
Candidate: 1.99-21ubuntu3.10
Version table:
1.99-21ubuntu3.10 0
500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64
Packages
1.99-21ubuntu3 0
500 http://gb.archive.ubuntu.com/
Noticed that syslog has various messages about the os-prober generated
during update-grub but tellingly NO reference to and md device, just the
constituent partitions.
** Attachment added: "syslong during update-grub"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1217933/+attachment/379
See also my question #234837 for the os-prober, as it appears to only
know about dmarid and not about mdadm RAID.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217933
Title:
update-grub fails to de
I think I have a patch that fixes this, basically adding another step to
generate the 'partitions' that include the md arrays, and to drop the md
arrays themselves as being part of any array obtained from /proc/mdstat
If this is OK, can it be made available for 12.04 support?
** Patch added: "Upd
This appears related to Bug #1217933 and I have a basic patch that
enables it for mdadm RAID.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/20915
Title:
os-prober doesn't support software RA
I think this applies to the following versions since I first tested the 1.61
version of os-prober to see if it was already fixed (was not) and my patach
should work for all of them, though I have only tested on 1.51 & 1.61:
Saucy (1.61ubuntu1)
Raring (1.57ubuntu1)
Quantal (1.56ubuntu1)
Precise (1
Thanks Thomas, that is a much better work-around method!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/576602
Title:
Fancontrol relies on the module load order
To manage notifications about this bu
We also run critical software that depends on the vm86 for performance
reasons, and we are already using dosemu with root privileges to gain
direct hardware access, so we see the potential security risks of this
are trivial. The suggestion above to have the patch back-ported to
enable vm86 only whe
Public bug reported:
When trying to look up the on-line documentation using the 'man' command
it fails on 12.04 with lseek error. For example:
$ man resolvconf
gdbm fatal: lseek error
This lseek error applies to other requests as well (e.g. ls, fdisk,
etc). System information is:
$ lsb_release
Yes, it looks very much like the DNS system is broken here, but when I
tried to look things up I get Bug #1001189 so overall not impressed with
12.04 so far :(
Still, adding some "dns-nameservers" lines to /etc/network/interfaces is
the next obvious thing to try.
--
You received this bug notific
Thanks for the package identification, result is:
$ apt-cache policy man-db
man-db:
Installed: 2.6.1-2
Candidate: 2.6.1-2
Version table:
*** 2.6.1-2 0
500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
100 /var/lib/dpkg/status
It seems to be a permissions i
Just to add that 'man' works fine on 10.04 LTS using NIS user accounts,
so I am guessing it is something that has changed with 12.04 file
locations/permissions, and/or the NIS package for 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I think this bug should concentrate on the key issue: that ntp (and
maybe others?) is being brought up on the wrong event, that is it comes
up with the interface, and not with the chosen type of name server.
In our case NIS provides user and name server resolution, and ntp comes
up before it with
The id command shows:
$ id
uid=xxx05(opr) gid=xxx00(local)
groups=xxx00(local),4(adm),20(dialout),109(lpadmin),501(operadores),502(vboxuser),xxx03(hrpt),xxx04(dosgroup),xxx07(vboxsf)
(with xxx replacing various numeric values that our sysadmin don't want
on a public forum)
The copy works withou
Yes, you are right in that our NIS servers are solaris boxes, and they
do support behind-the-scenes DNS lookups as it turns out. It is also
true that NIS is depreciated, though a lot of older installations like
ours still use it, and for most machines DNS is available and will
probably fix our spec
It is probably true that this has not been seen much as a bug due to DNS
normally being available, hence NIS dependency (if present) being a
secondary issue. However, we found that ntp did not recover by itself,
so possibly it only tries to find the nameservers once, but will re-try
for the time se
Given those files are readable, could it be some file format change
between the working-on-NIS version with 10.04 (2.5.7-2ubuntu1) and the
problem version of 12.04 (2.6.1-2), say if it is seeing extra man files
via the NIS/automount environment?
--
You received this bug notification because you a
Running it with strace produced this near the end:
open("/packages/local/share/man/index.db", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=3208201, ...}) = 0
fcntl64(3, F_SETLK, {type=F_RDLCK, whence=SEEK_SET, start=0, len=0}) = 0
read(3,
"\316\232W\23\0\0\20\0\0\0\20\0\0\0\0\0\0\0\20\
There is no $HOME/.manpath file in any of the NIS accounts I have tried, or for
the local user accounts on my 10.04 box either.
Actually it is slightly more bizarre, that NIS account (opr) is braking 'man'
but another NIS account on the 12.04 machine is OK, while opr (and others)
accounts are al
The original problem, though sadly I did not post the exact messages,
was saying it could not run fsck.cifs (which of course is non-existent).
The bug in this case was that with pass=0 it should not even have tried
to run a check on boot-up.
The bug now is the same underlying problem, that during
> As far as the first question: Does "/packages/local/share/man/" get opened
> and/or stat-ed in the strace when you run "man" on the Lucid box and from
> other accounts on the Precise box?
It seems not.
> Is $MANPATH set differently in the different accounts?
There is no $MANPATH variable set o
One thing I noticed that is different is $PATH but I expected that to be
the search order for programs, not for mand pages and/or index.db files!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001189
The current (64-bit 10.04) boot.log file has messages such as these
appearing:
error -1 (Unknown error 18446744073709551615) opening credential file
/home/paul/.smbcredentials
mountall: mount /media/swdev [1087] terminated with status 1
mount error: could not resolve address for smb: Temporary fa
The $PATH variables are different, with the 12.04 (32-bit) system having
/packages/local/bin included in the list. If I remove that from the
12.04 system it then avoids the /packages/local/share/man/index.db file
and it works.
However, if I add /packages/local/bin to the 10.04 system (64-bit, in
c
If I run the accessdb command on the 32-bit 12.04 machine it core dumps:
$ /usr/sbin/accessdb /packages/local/share/man/index.db
Segmentation fault (core dumped)
Doing the same on the 64-bit 10.04 machine produces something intelligible:
$ /usr/sbin/accessdb /packages/local/share/man/index.db
$
It seems this dumbness has been recognised since 2005 according to this
bug report, but not taken seriously:
https://bugzilla.redhat.com/show_bug.cgi?id=162416
Apparently "gdbm-1.9.1 (already in Rawhide) provides different magic
values for 32 and 64 bits, so we can discover what system the file w
Trying to be positive, we have a possible work-around for our own system (drop
/packages/local/bin from $PATH) but it is not really a decent fix. The
underlying problem is difficult in that all current 32-bit and 64-bit DB files
look similar, so work on an improved libgdbm3 is going to be diffic
In the long run, migrating all of the DB files to newer ones that
identify the size/swap nature is the right approach, however, I wonder
if a simpler fix for 'man' which would be useful for current systems
would be to keep everything in the in local DB (say the
/var/cache/man/index.db file or simil
Public bug reported:
Running Ubuntu 10.04 LTS 32-bit and today I got the upgrade from
Thunderbird 3.6.X to 11.0.1 and noticed it is using a stupid amount of
CPU time when apparently idle. On my quad-core AMD machine it is taking
typically 30-50% CPU when doing nothing, and this is much the same wh
Maybe it is indexing or something? The old version told you that (bottom
- left status bar?) but this one is just saying "No messages to
download" although there seems to be a lot of disk activity.
However, that is still no excuse for polling the time at sub-millisecond
intervals!
--
You receive
Looks like it was probably indexing, as reported here:
https://getsatisfaction.com/mozilla_messaging/topics/thunderbird_indexing_hogs_the_cpu
CPU load is now normal, and remaind so after re-start, but seems the
"Activity Manager" window is volatile so there is no log of what it was
originally doi
This appears to be broken again, the 10.04 default profile has:
# vim:syntax=apparmor
# Last Modified: Tue Aug 11 16:14:21 CDT 2009
# Updated for Ubuntu by: Jamie Strandboge
@{NTPD_DEVICE} r,
So it only allows read-access to the devices. Also broken/reverted is
the tunables which has:
# La
Public bug reported:
I tried the daily build of 16.04 32-bit to test out the watchdog daemon
code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
/etc/modules so it is loaded at boot-time, as watchdog timer modules are
not normally auto-loaded due to the risk of an unexpected reboot.
H
This is still present in the development branch for 16.04
Jan 19 17:53:23 ubuntu rsyslogd-2039: Could not open output pipe
'/dev/xconsole':: No such file or directory [v8.14.0 try
http://www.rsyslog.com/e/2039 ]
System information:
$ lsb_release -rd
Description:Ubuntu Xenial Xerus (developme
Public bug reported:
I was testing the watchdog daemon code on the development version of
16.04 today and found the associated systemd service files for this has
some bugs.
The first of these was a typo in /lib/systemd/system/watchdog.service
where there was a missing ['] character. This lead to
Just to add this is only a problem on shut down / reboot, you can
manually stop and start the daemon without problems using:
service watchdog start
service watchdog stop
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
This has been fixed from at least 2011 onwards so can be closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/378696
Title:
--version not supported (error in manpage ?)
To manage notifications abo
Some updates added this month (Jan 2016) add a timer so you get a less
"trigger happy" behaviour if the interface is slow in coming up.
Currently in the GIT version, but hopefully this will be in a release
version 5.15 some time soon.
--
You received this bug notification because you are a member
Note the "watchdog/0" thread you see is not the system monitoring
daemon. Rather it has a similar task for kernel scheduling:
http://linux-tips.org/t/what-is-kernel-soft-lockup/78
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
This has been added to the current GIT version:
http://sourceforge.net/p/watchdog/code/ci/77e777e2fb4cc0723fb51ad5556a427cf345385b/
Hopefully there will soon be a version 5.15 release with this feature
included.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
This is probably the same problem as bug #1535854 thought there could be
a number of related factors, for example bug #1535840 for module
loading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Doh! I meant bug #1448924 (above is this bug)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535854
Title:
watchdog daemon going in to failed state on reboot
To manage notifications about this bug
This may be a duplicate of bug #1535854
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1535854
Title:
watchdog daemon going in to failed state on reboot
To manage notifications about this bug go to:
I just tested the proposed fix from
https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/comments/7
and while it includes the fix for the "unbalanced quoting" it does not
fix the system going in to a failed state.
--
You received this bug notification because you are a member of Ubuntu
I tested the proposed fix from comment #7 on bug #1535854 but it did not
work for that system (16.04) :(
--
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 start on boot
Usually the wd_keepalive daemon would be started early for this reason,
to keep the hardware from timing out. Once the machine is up it would
hand over to the watchdog daemon that runs system tests.
I am guessing that the at-boot fsck is run before loading anything
(daemons, etc) so all the file s
Note the work-around for this bug is not in the GIT repository for the
watchdog package as:
http://sourceforge.net/p/watchdog/code/ci/0d156df287656d1031389cac99caa9fa94c2d204/
Hopefully a release of version 5.15 soon will make that more widely
available.
--
You received this bug notification be
I think this problem is down to the IPMI style of watchdog being
configured when the machine boots, but the Linux system not starting the
refresh action until much later. For example if I try a test on my home
PC (Ubuntu 12.04 64-bit desktop) after installing the watchdog and using
"touch /forcefsc
Seeing this with a fresh 12.04.4 64-bit installation using ATI graphics.
Seems to be triggered by "changing user" and it frequently breaks VM
operations. Typical syslog entry looks like this:
Apr 29 14:26:59 john-desktop rtkit-daemon[2183]: Successfully made thread 23506
of process 23506 (n/a) ow
This bug, the ability to get the kernel back on to a supported stream,
is still broken a month on, even though there was some update to the
update manager today (which still caused a crash report, though that was
supposed to be fixed).
--
You received this bug notification because you are a membe
Running from the command line reports:
$ /usr/bin/update-manager
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/defer/__init__.py", line 473, in
_inline_callbacks
result = gen.throw(result.type, result.value, result.traceback)
File
"/usr/lib/python2.7/dist-pack
Public bug reported:
In spite of apparent fixes for [bug #1342424] I find that the update-
manager is still crashing and failing to perform the HWE upgrade to move
my 12.04.4 LTS installation.
If I run the update-manager from the command line I get the same
behaviour as the normal alert when upda
Sorry, should have been related to [bug #1341324].
Not sure if this counts a "distribution upgrade" since it is about continued
kernel support for 12.04 LTS and not about moving to 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just to say a recent update has fixed this. There are still problems
with Nvidia driver post-update, but that is another bug...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350310
Title:
update-ma
A recent update to the update-manager seems to have fixed this for me.
Still problems with the Nvidia driver post-update, but that is not the
same bug/dependency issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
No, the underlying problem is with dpkg not recognising the .xz compression
type used in Oracle's .deb file.
This is ALREADY fixed in the 12.04 version, so for from there being "nothing
the Ubuntu developers can do", there is - backport the later version of dpkg
that supports the .xz file type!
I would also like to have shutdown messages logged. Could it be
configured to stop on reaching the last of the init-style of run-levels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192037
Title:
Attached are my term.log files from before the bug report and afterwards when
it seems to have succeded (mostly).
I say mostly, as there are missing firmware warnings, and it screwed up the
graphics (removed the nvidia driver but did not un-blacklist the nouveau
driver, so 640x480 VGA graphics o
Seems this bug still is present with the latest grub update, as had to
patch /usr/bin/os-prober again to allow dual-boot from MD array.
$ apt-cache policy grub2
grub2:
Installed: (none)
Candidate: 1.99-21ubuntu3.14
Version table:
1.99-21ubuntu3.14 0
500 http://gb.archive.ubuntu.
Updated a 12.04 LTS box today with the kernel "3.13.0-39-generic
#66~precise1-Ubuntu SMP Wed Oct 29 09:56:49 UTC 2014 x86_64 x86_64
x86_64 GNU/Linux" and problem still there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
We are seeing the same a dozen or so timers per day, and it happened
after we updated from the -36 to the -37 kernel build.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376245
Title:
remove_proc_e
Happens for me with one DVD, seems to be a fault situation that also segfaults
k9copy, though K3b and VLC can both read the DVD OK-ish.
My suspicion is either a read error or copy protection trick that is causing
the error, and these packages are not doing some sensibility check on what is
read.
It is now almost a month after "status: Unknown → Fix Released" was
reported for this bug.
This still has not been fixed in the 10.04 LTS version.
Can anyone tell me when it will be fixed?
Can anyone tell me what the "support" in "Long Term Support" version is
supposed to mean? Does anyone car
Tried the same test on my work PC and it seems to work just fine. Will
have to try rebooting home PC to see if it is still playing up...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/864846
Title:
i
Nope, rebooted home PC and ran test again, still showing absurd
transfers:
$ ifconfig eth1; dd if=/dev/zero of=/nfs/thecus/data/temp.dat bs=1M count=100;
sync; ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:1b:21:2f:ae:37
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.
Looks like it is NFS-related, as a test with the same NAS mounted using
CIFS shows sensible values:
$ ifconfig eth1; dd if=/dev/zero of=/mnt/z/data/temp.dat bs=1M count=100; sync;
ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:1b:21:2f:ae:37
inet addr:192.168.1.100 Bcast:192.
I booted my home PC with the older kernels, and found that 2.6.32-33
also shows this fault, but 2.6.32-32 reported the correct value.
As it seems not to affect my work PC with the same 10.04 LTS
installation (tested both 32 and 64 bit versions) I guess it must be
something specific to the kernel d
Really, no logging or blocking of failed log-in attempts? Did no one
learn from computing history?
Also another failing of lightdm is it fails to respond to the power
button, even if you have set it under Gnome, etc, to do an orderly shut-
down. There have been times when a keyboard/mouse problem
There is still an underlying issue of "discover-ability" here and it
fails, in my view, to be acceptable for a disabled user:
(1) Why does the tab key not cycle to the shutdown menu? Where exactly
will a user, faced with the log-in screen, find out that the 'F10' key
opens that menu?
(2) The ta
OK, I just discovered that the up & down arrow keys cycle the user
accounts, but they do not cycle the log-in method! For that you need to
use the tab key!
How do you get access to the accessibility drop-down menu on the to bar?
Same for the keyboard/language selection?
Also why no 'F1' for help
Public bug reported:
Following on from the issue of bug #986289 to more general issue about
the design of the unity greeter and how a person, in particular a newer
user, with only keyboard-like access can make proper use of the
computer.
There is an underlying issue of poor "discoverability" here
Realised this is separate issue so opening new bug for it as #1071728
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986289
Title:
lightdm shutdown opens a window without focus
To manage notificatio
@Sebastien Apologies for the apparent hijacking of this bug, opening a
new report for that subject.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027805
Title:
logins are not recorded in wtmp
To m
There should be no requirement to log-in in order to shut the machine
down if you have physical access, the power button should initiate this
in an orderly manner (warning/prompting as required).
Basically, if the person at the power button wants to, they can hold the
button in for 5 sec and power
Found the power button issue is already open as bug #915382
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1027805
Title:
logins are not recorded in wtmp
To manage notifications about this bug go to
Public bug reported:
On Ubuntu 12.04 the utility 'who' fails to report the presence of a user
logged in using the Unity or Gnome fallback GUI.
For example, if I log in as "psz" to the 10.04 machine in use by "arz"
and I run 'who' in the ssh terminal I get something like this:
$ who
arz tty7
Of course, this bug might really be down to Gnome/Unity failing to
declare the user as logged in, but the fault _appears_ to be the core
utilities simply not seeing anyone logged in using the main
keyboard/mouse/display.
--
You received this bug notification because you are a member of Ubuntu
Bug
I am not sure this bug should be considered a low priority, given that
it breaks core utilities such as 'who', 'users', 'top', and similar by
fooling them in to saying there is no one else logged in (which might
result in a remote reboot being initiated while a user is on the normal
keyboard/video/
Happened again today, presumably nothing has been done to fix anything?
LTS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/507062
Title:
synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _X
Sorry about that.
I am still seeing the problem with an up-to-date 12.04 system and my bug
#1029048 was marked as a duplicate of this one, so I presumed it was still a
significant unresolved issue. I guess it is a case of the previous bug-fix not
being released yet.
--
You received this bug no
Public bug reported:
When I installed rpcbind on Ubuntu 12.04 (32-bit) version (by means of
old 'potrtmap' package) I found that it broke the settings in
/etc/network/interfaces by commenting out the last line that configured
eth0 for DHCP, etc.
Original file had this as the last 3 lines:
# The
Actually this is not quite true. It turns out on the next machine that
this change was done earlier (Friday 13th, with interfaces.bak-0 file
having the uncommented line), but it results in the system breaking once
rpcbind, nis, etc has been added.
So before rpcbind & nis is installed, I can reboot
It is strange. I have a script to install NIS and autofs, it installs
the following packages:
portmap
nis
tcsh
nscd
autofs
rsh-client
rsh-server
nfs-kernel-server
Then it creates/updates some of the file (auto.master and so on) to suit
out use.
If I install each package in turn and reboot, it co
The odd thing is I ran the script after installing the packages one-by-one and
it worked OK. Obviously it realised the packages were already installed so
skipped doing anything there, then it set up the various files. However, it was
still a bit slower to come up after reboot than when the comme
This bug also causes me problems with machines I support. The default
should *always* be the system-wide settings that Ubuntu honour, and at
the very least it should not reset during an 'upgrade'. This 'reset to
US paper size' arrogance is a major irritation and causes problems for
users who print
This is still a problem for me.
$ lsb_release -rd
Description:Ubuntu 10.04.4 LTS
Release:10.04
$ apt-cache policy thunderbird
thunderbird:
Installed: 14.0+build1-0ubuntu0.10.04.1
Candidate: 14.0+build1-0ubuntu0.10.04.1
Version table:
*** 14.0+build1-0ubuntu0.10.04.1 0
5
Unfortunately (1) moving some machines to 12.04 is not an acceptable option due
to the vast differences in user interface, and (2) it is still not right (as
far as I can tell) with 12.04 as a recently installed test system when set up
for UK preferences with an OKI network printer set for A4, bo
Do you know where they store the page size setting?
Also is there any (easy) way to force apt-get or similar to 'upgrade' a package
to see what is happening?
I wonder if the package comes with a default config file that is clobbering the
user-configured file?
--
You received this bug notificati
I also looked at the Windows version in a VM and it has no page size
preference option, I presume as it is written to always take the
selected printer's choice. So this is probably a Linux-only bug (though
I can't rule out MacOS since I don't have a Mac to try)/
--
You received this bug notificat
This bug is STILL not fixed in 10.04 with Firefox 14.0.1
Is this related to bug #627648 that applies to both Firefox and Thunderbird and
why, after 8 YEARS is this still an issue for the majority of the world that
use A4 paper and not US Letter?
Seriously, what is happening here?
--
You receive
Looks like this has been known about, but nothing useful done to really
fix it, for 10 YEARS now:
https://bugzilla.mozilla.org/show_bug.cgi?id=147419
** Bug watch added: Mozilla Bugzilla #147419
https://bugzilla.mozilla.org/show_bug.cgi?id=147419
--
You received this bug notification becaus
Incidentally my setting is LANG="en_GB.utf8" so it is still an issue and
not fixed, as per comment 73 in the above link.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/627648
Title:
firefox/thunderbi
Looking at the modified preferences shown by about:support I don't see anything
that appears to be the global page size.
There are various printer-specific settings, but as this problem occurs with
all printers it is clearly a program-wide problem and not a printer-specific
one.
--
You receive
101 - 200 of 310 matches
Mail list logo
