I should add, that running pg_upgradecluster after "sudo su - postgres" did one
thing that a simpler
"sudo pg_upgradecluster" didn't - it changed the port numbers, so that the new
v.16 cluster is running on port 5432, and the old v.14 cluster is now on port
5433.
So there is some use in runnin
I tried today, after running "sudo pg_dropcluster 16 main", by running as
postgres:
sudo su - postgres
pg_upgradecluster 14 main
More seemed to be done, but the end result was the same as before.
Templates were set up; but sadly still the users were not copied from v.14, nor
the databases.
So
Thank you, Andreas.
I've had a checkered history with pg_upgradecluster; the last upgrade (to
22.04LTS, PG14) worked fine, if I remember correctly, but all other post-LTS
upgrades failed for me.
Is it possible that setting a non-default password for user postgres might
cause a problem? - the on
1)
The LTS upgrade creates an empty cluster for the new postgresql version:
pg_lsclusters
This empty cluster first needs to be removed:
pg_dropcluster 16 main --stop
Then:
pg_upgradecluster 14 main
On my main pc, that last command collapsed with error - see bug #2078494
On the standby pc (an older
Yes, on my stand-by pc I can still re-run the upgrade process - I didn't get
round to installing the databases manually!
Currently, pg_lsclusters shows
14 main 5432 down ...
16 main 5433 online
and psql -p 5433 shows no role for me ... as noted above.
So yes, I'll be happy to provide any i
Please ignore comment 121 above. I don't now think it's related to this issue.
I found the touchpad/mouse problem reported on linuxmint bug 10675 in Feb.2022,
and I've added a comment there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
The kernel upgrade to 6.8.0-47 made a noticeable improvement to the
mouse/pointer problems on my Dell Inspiron, and 6.8.0-48 has now fixed
most of them - thank you!
BUT I still have one problem left: for years I've had the touchpad
disabled, and used a USB mouse, as being easier to control proper
Having got tired of repeated invitations to upgrade, I removed xdiagnose
*completely*, then tried to install. Synaptic gives the same error:
E: /var/cache/apt/archives/xdiagnose_3.8.10ubuntu0.1_all.deb: unable to open
'/usr/lib/systemd/system/failsafe-x.service.dpkg-new': No such file or directo
I can't remember ever asking to install xdiagnose; and the update to
24.04.1 worked fine.
But the current proposed upgrade fails for me too, with Synaptic giving the
following error:
E: /var/cache/apt/archives/xdiagnose_3.8.10ubuntu0.1_all.deb: unable to open
'/usr/lib/systemd/system/failsafe-x
Or the greater detail from Synaptic:
Unpacking xdiagnose (3.8.10ubuntu0.1) over (3.8.10) ...
dpkg: error processing archive
/var/cache/apt/archives/xdiagnose_3.8.10ubuntu0.1_all.deb (--unpack):
unable to open '/usr/lib/systemd/system/failsafe-x.service.dpkg-new': No such
file or directory
No app
Sorry - after a lot more searching, I retract comment #8.
Most advice on upgrading PG versions refers to 'sudo pg_ctl {stop|start}'
Some advices refer to 'sudo service postgresql {stop|start}'
Very few refer to the *systemd* command 'sudo systemctl {status|start|stop}
postgresql',
and equally v
It might be relevant that pg_ctl is not in any PATH (not mine, nor sudo, nor
postgres), on either of my PCs.
The command is found only in /usr/lib/postgresql/*/bin/pg_ctl
Attempts to run [sudo] pg_ctl status result in
Command 'pg_ctl' not found, did you mean:
command 'dg_ctl' from deb drogon (1
1
Yes, the databases I expected to be transferred are in the MAIN cluster, so
*should* have been set up in the new 'postgresql-16' main cluster; and
pg_upgradecluster *should* have changed the ports set for the '14' and '16'
instances. Neither happened.
2
pg_upgradecluster gave me problems af
(1) Those two fatal errors result from an attempt to verify the (apparently
not unsuccessful) pg_upgradecluster by psql access to the database 'simas'.
They originate after pg_upgradecluster had terminated.
(2) There are no known customised config files for postgresql on the
system.
(3) I can'
** Attachment added: "upgradeclusterINFO.gz contains (a) the screen output
pasted into pg_upgradecluster.OUT, (b) apt/term.log, (c) apt/history.log,
(d) postgresql/postgresql-14-main.log.1, and (e) postgresql-16-main.log"
https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/208199
** Attachment added: "Generated on standby pc using apport-cli --save
APPORT.info"
https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/2081996/+attachment/5821830/+files/APPORT.info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
New bug report filed: #2081996
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078494
Title:
After upgrade to 24.04.1 LTS pg_upgradecluster fails
To manage notifications about this bug go to:
https:
Public bug reported:
As reported against "#2078494 After upgrade to 24.04.1 LTS
pg_upgradecluster fails":
On my standby pc, I upgraded today from 22.04 to 24.04.1
After the upgrade /usr/lib/postgresql/14/bin/postgres and the named libraries
were all still in place.
pg_lsclusters showed the old (
** Attachment added: "screen output for failed pg_clusterupgrade"
https://bugs.launchpad.net/ubuntu/+source/postgresql-16/+bug/2078494/+attachment/5820288/+files/pg_upgradecluster.OUT
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On my standby pc, I upgraded today from 22.04 to 24.04.1
After the upgrade /usr/lib/postgresql/14/bin/postgres and the named libraries
were all still in place.
pg_lsclusters showed the old (v.14) and the new (v.16) clusters, as expected.
So I dropped the new v.16 cluster with "--stop", and ran pg_
Installed unity-greeter from -proposed, 24.04.1-0ubuntu1
re-started pc; correct display "Ubuntu 24.04 LTS" on login screen.
Logged out, correct display "Ubuntu 24.04 LTS" on login screen again.
Works for me, thank you.
** Tags removed: noble verification-needed verification-needed-noble
** Tags a
Perhaps I can be a bit more helpful - I have a standby pc on 22.04 LTS.
It has /usr/lib/postgresql/14/bin/postgres
I'll upgrade that box to 24.04 as soon as I can, though probably not before
next weekend (other jobs needing even more urgent attention!). And when I do,
I'll track what happens whe
I'm afraid I can't add much to the original report - it's too long ago, and I
can't backtrack to try to repeat the exercise.
The Noble upgrade installed PG16 and created the new cluster with a new port
number above the normal, and all looked ok until I ran "sudo pg_upgradecluster
14 main", at wh
That fix is in the package for 24.10 - I hope it will get back-ported to
24.04 !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063557
Title:
After upgrading to Ubuntu 24.04, login screen shows "Ubu
But on my system, the installed /usr/share/unity-greeter/logo.png shows
"ubuntu 23.10", set against a gray chequered background ...
The Package version shows in Synaptic as 23.10.1-0ubuntu4, like
accountsservice, as noted above (#10).
The version number (unity-greeter -v) shows as 17.04.1 (did ma
I note that accountsservice is installed, with version 23.13.9-2ubuntu6
The version number looks odd?
For jammy it was 22.07.5-2ubuntu1.5
and for mantic 23.13.9-2ubuntu1.5
May be a red herring, but the documentation for LightDM refers to
accountsservice ...
--
You received this bug notificatio
The photo of the login screen shows the computer-name at the top left,
though that doesn't show well in the photo. The vital bits are clear,
however!
FWIW, I think Cinnamon DE only starts *after* login ... ?
** Attachment added: "loginscreenphoto.jpg"
https://bugs.launchpad.net/ubuntu/+bug/2
** Attachment added: "Entered before, but I think only 1 attachment at a time ?"
https://bugs.launchpad.net/ubuntu/+bug/2078959/+attachment/5813645/+files/packages.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Synaptic says for base-files: 13ubuntu10.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2078959
Title:
Since upgrade to 24.04.1 LTS login screen shows "23.10"
To manage notifications about this b
Public bug reported:
Since the LTS upgrade from 22.04 to 24.04.1 LTS the login screen
(plymouth?) shows the version as "Ubuntu 23.10", which has never been
installed on the system.
The image on the login screen shows the "Noble" coronet, which seems
correct.
All the other queries I have tried to
Public bug reported:
sudo pg_upgradecluster 14 main
Restarting old cluster with restricted connections...
Notice: extra pg_ctl/postgres options given, bypassing systemctl for start
operation
Error: /usr/lib/postgresql/14/bin/pg_ctl /usr/lib/postgresql/14/bin/pg_ctl
start -D /var/lib/postgresql/
Public bug reported:
When claws-mail is set s the default email client, calling
xdg-email --subject HELLO --body "Body text" --attach FILENAME EMAILADDRESS
causes claws-mail to terminate.
No errors are reported to the terminal
Any call without "--attach FILE" works fine.
This bug also affects
Until communication between xdg-email and claws-mail is fixed in Ubuntu LTS,
I've resolved the problem by (a) adding a claws-mail line in the apparmor
profile for senddoc and reloading the policy. and (b) setting
Tools/Options/Internet/Email to specify /usr/bin/claws-mail.
I don't like messing w
Until communication between xdg-email and claws-mail is fixed in Ubuntu LTS,
I've resolved the problem by (a) adding a claws-mail line in the apparmor
profile for senddoc and reloading the policy. and (b) setting
Tools/Options/Internet/Email to specify /usr/bin/claws-mail.
I don't like messing w
I believe there is a bug in xdg-email affecting --attach
(https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941?comments=all)
(sorry, the last attempt closed on me before I'd finished)
The fix for that wor3ks in Claws-mail 3.17.8, but not in 3.17.5 which is
the latest version for Ubuntu
I believe there is a bug in xdg-email affecting --attach
(https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941?comments=all)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748895
Title:
In the current version of LO, 7.1.2.2 (Ubuntu build, on Ubuntu 20.04 LTS),
there has been no change to senddoc since the last installed version (7.0.1.2),
but the behaviour is significantly different.
1
Using the supplied senddoc (7.1.2.2), and trying to send a PDF attachment,
(a)
if Tools/Option
I believe there is a bug in xdg-email affecting --attach
(https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941?comments=all)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803604
Title:
I believe there is a bug in xdg-email affecting --attach
(https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941?comments=all)
(sorry, the last attempt closed on me before I'd finished)
The fix for that wor3ks in Claws-mail 3.17.8, but not in 3.17.5 which is
the latest version for Ubuntu
In the current version of LO, 7.1.2.2 (Ubuntu build, on Ubuntu 20.04 LTS),
there has been no change to senddoc since the last installed version (7.0.1.2),
but the behaviour is significantly different.
1
Using the supplied senddoc (7.1.2.2), and trying to send a PDF attachment,
(a)
if Tools/Option
I have the same problem on 20.04 LTS (fully updated).
xdg-email --subject SUBJ --attach HAR.pdf
gives:
/home/mbm/.claws-mail/mimetmp/.comments: unlink: Is a directory
** (claws-mail:10611): WARNING **: 15:50:25.346: failed to convert
encoding of file name: Invalid byte sequence in conversion input
Public bug reported:
This problem has occurred before
https://www.spinics.net/linux/fedora/fedora-users/msg439365.html
proposed "In Adobe Reader 9:
Choose File > Print.
Click on Advanced.
Under Font and Resource Policy, select Send for Each Page."
but this does not solve the problem,
And further to my last comment, the point is proved.
Claws[-mail] is set in senddoc to use
ATTACH="${ATTACH:-}${ATTACH:+ }$2"
without any reference to encoding.
In Tools.Options, I set email to /usr/bin/claws-mail
and all is well, the document is attached to a draft email in a Compose window.
Th
Just to clarify my remarks yesterday,
the error window in Claws-mail showed a filename that looked very much as
though it had been encoded.
There may be some upgrade to the system that caused the change in behaviour -
simplescan has taken to ignoring the ADG and scanning from the glass,
Acroread
Just to clarify my remarks yesterday,
the error window in Claws-mail showed a filename that looked very much as
though it had been encoded.
There may be some upgrade to the system that caused the change in behaviour -
simplescan has taken to ignoring the ADG and scanning from the glass,
Acroread
And further to my last comment, the point is proved.
Claws[-mail] is set in senddoc to use
ATTACH="${ATTACH:-}${ATTACH:+ }$2"
without any reference to encoding.
In Tools.Options, I set email to /usr/bin/claws-mail
and all is well, the document is attached to a draft email in a Compose window.
Th
There is a new twist to this saga.
With LO 7.0.1.2 today I get an error message
/home/mbm/.claws-mail/mimetmp/.comments: unlink: Is a directory
** (claws-mail:12915): WARNING **: 10:04:23.190: failed to convert encoding of
file name: Invalid byte sequence in conversion input
malloc_consolidate():
There is a new twist to this saga.
With LO 7.0.1.2 today I get an error message
/home/mbm/.claws-mail/mimetmp/.comments: unlink: Is a directory
** (claws-mail:12915): WARNING **: 10:04:23.190: failed to convert encoding of
file name: Invalid byte sequence in conversion input
malloc_consolidate():
Public bug reported:
A new Epson WF-7710 installed yesterday.
Various files missing in /usr/share/sane/xsane/doc and elsewhere - linked them
in succesfully.
Xsane now detects 2 devices with closely-similar names (the name note displayed
fully, however)
Scan appears to start whichever device has
Worked for me too - but then I found more problems (Failed to start scanner:
invalid argument), and then
file:///usr.share/sane/xsane/doc/sane-problems-doc.html : not found
which is in /usr/share/doc/xsane-common/html/sane-problems-doc.html
together with lots of other stuff which is also presumab
u8_totitle accepts most of the non-alphanumeric ascii codes as word-
separators, but besides the 'dot', it fails to recognize the colon (:)
and the underscore (_) as separators (can't see why), and also fails the
recognize the apostrophe.
I can see reason for this last - one wouldn't want "Adam'S
Public bug reported:
u8_totitle() fails to handle "." as a word separator, though the dot is
commonly used without any space-character where initials precede a surname.
for example, the street address "Largo A.Gemelli"is rendered "Largo A.gemelli"
I find it necessary to include the dot (.), comm
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424973/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Ti
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424974/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424969/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424971/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
li
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424965/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424968/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/190
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424972/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
li
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424963/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424959/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424958/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424966/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424964/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424970/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Titl
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424960/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
libn
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424967/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424962/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
libn
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424961/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
apport information
** Tags added: apport-collected focal
** Description changed:
This was first raised as a Question,
https://answers.launchpad.net/ubuntu/+source/ncurses/+question/693490
Since upgrading from 18.04 LTS to 20.04 LTS I have 2 problems in the
screen display using AUBIT4G
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1900816/+attachment/5424957/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900816
Title:
libncu
Public bug reported:
This was first raised as a Question,
https://answers.launchpad.net/ubuntu/+source/ncurses/+question/693490
Since upgrading from 18.04 LTS to 20.04 LTS I have 2 problems in the
screen display using AUBIT4GL
(1)
in displaying data to a screen array where the first field is sho
I think the problem is in ibus-preferences, which had "English (US)" selected
as its keyboard.
On the "Advanced" tab, I checked "Use system keyboard layout" (was unchecked
beforehand).
That alteration has survived 2 reboots, with the keyboard setting now correctly
reflecting the physical keyboar
https://wiki.archlinux.org/index.php/Linux_console/Keyboard_configuration
(any yes, I know archlinux is not ubuntu!) says:
--
A persistent keymap can be set in /etc/vconsole.conf, which is read by systemd
on start-up. The KEYMAP variable is used for specifyi
After every reboot, 'setxkbmap -query' shows "layout: us"
As a temporary fix, I've now set 'setxkbmap gb' in an executable file,
so it can be run with a minimal number of keystrokes.
LOCALE is unchanged from before the LTS upgrade, as is the keyboard itself, and
/etc/default/keyboard
Somewh
The problem persists. Every bootup leaves the default keyboard labelled as
English(UK), but performing like US(?).
I note that the problem has been known before,
https://askubuntu.com/questions/282283/keyboard-layout-reverts-at-every-boot
though I have never experienced it until now.
None of the
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416954/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416957/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/189
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416962/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Ti
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416959/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Titl
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416963/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416958/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416955/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416960/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
ke
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416956/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416961/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
ke
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416947/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416951/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
keyb
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416948/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416950/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416952/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416949/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
keyb
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416946/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
keyboa
apport information
** Tags added: apport-collected focal
** Description changed:
After the upgrade the keyboard, set as 'English (UK)' appeared to be using a
US layout, with double-quote(") and 'at' sign(@) transposed, and key left of
'z' giving "<"/">" instead of "\"/"|" - and pound sign (
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1898338/+attachment/5416953/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898338
Title:
Public bug reported:
After the upgrade the keyboard, set as 'English (UK)' appeared to be using a
US layout, with double-quote(") and 'at' sign(@) transposed, and key left of
'z' giving "<"/">" instead of "\"/"|" - and pound sign (GBP: £) not (yet) found.
Corrected by adding Estonian layout, th
The system has been updated several times since, with no further problem.
I note that this was the only time that two kernels have been downloaded
together, and I guess that may be the cause of the problem?
I held on to the previous kernel, and used that until a fresh kernel appeared,
and did not
Public bug reported:
TWO kernels appeared to have been downloaded yesterday
4-15-0-106 failed to load, both normally and in recovery mode
4/15.0.101 failed to load when selected
The PREVIOUS kerenal 4.15.0-99 (still installed) loaded ok
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux
6.3.0.4 includes most of the changes I suggested, but still fails to
operate properly - it switches the focus to the email client, but fails
to create a new email.
I thnk the problem may be at senddoc line 293,
MAILTO="${MAILTO:-}${MAILTO:+&}attach="$(echo "file://$2" | "${URI_ENCODE}")
My email
6.3.0.4 includes most of the changes I suggested, but still fails to
operate properly - it switches the focus to the email client, but fails
to create a new email.
I thnk the problem may be at senddoc line 293,
MAILTO="${MAILTO:-}${MAILTO:+&}attach="$(echo "file://$2" | "${URI_ENCODE}")
My email
1 - 100 of 119 matches
Mail list logo
