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
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
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
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
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
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
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:
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
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
*** 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
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
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
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
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
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
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
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
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:
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 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
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
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:
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
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
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
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
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 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
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
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
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
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
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
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
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:
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
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
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
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
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
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!
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
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:
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
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
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.
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
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
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
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
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.
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
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
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
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 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
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
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
:)
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/
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
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
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
Well I guess no one is going to fix the it87_wdt module any time soon :(
As a work-around, my own version of the watchdog daemon (update #117 or
later) now detects if it is reported as "IT87 WDT" when queried and re-
sets the time-out on each refresh, rather then writing '\0' to the
device. It app
Looking through the code in it87_wdt.c it appears that the open/close of
the timer is performed by writing to the configuration registers that
Cinquero identified, however, that is not how the refresh is performed!
Looking at this part of the code:
/* watchdog timer handling */
static void wdt_k
What is odd is that I can set the time-out OK, and I can stop the
watchdog OK and it no longer reboots, but it is the simple "refresh"
that appears not to work!
NOTE: Stopping using "pkill watchdog" as that closes the device, where
as "service watchdog stop" swaps to the wd_keepalive daemon that
p
This problem is also showing up with our new PCs using the IT8728
(motherboard is Gigabyte Z87-D3HP). The watchdog is armed and the time-
out can be set, but the "refresh" is not working so the machine reboots
after the chip's time-out period.
Jul 2 16:57:04 kernel: [ 346.256483] it87_wdt: Chip
I agree with Jean-Daniel, this is something that must be adressed. While
you now see any graphical log-in using 'who' and it lists users both at
"tty7" etc, for graphical log-in, and as "pts/2" etc for terminal log-
in, only the termianl sessions are seen with the "last" command.
That worked corre
So is anyone addressing the issue of power button function at the log-in
screen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/915382
Title:
ACPI events to shutdown/reboot don't generate a popup lik
Same problem here with 64-bit 12.04.
It seems to be a rather basic flaw in the underlying design that the
'hwmon0' sort of name used is load-order-dependent for the modules.
Can't that ordering be made alphabetical or similar so without a
hardware/configuration change it is fixed?
My solution was
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.
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
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
@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
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
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
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
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
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
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
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
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/
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
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
Just to add to this bug discussion my observation in bug #627648 that
the about:support setting for user-modified parameters do not appear to
change in any when you alter the global paper size, which may be related
to why this is continually reset on version 'upgrades'. This trait makes
the lack of
*** This bug is a duplicate of bug 10910 ***
https://bugs.launchpad.net/bugs/10910
In fact, if I use the 'Copy all to clipboard' option to save a text file with
the paper size as A4 and as US Letter, diff finds no differences. So basically
the user's preference for this is not being saved in
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
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
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
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
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
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
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
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
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
1 - 100 of 310 matches
Mail list logo
