Public bug reported:
If I boot my laptop with an SD card (actually SDXC) in the MMC slot the
system sees it and I can mount and use it.
If I then unmount it, remove it then re-insert it I get this in the
system ,og:
[ 194.673108] mmc0: card e624 removed
[ 205.462065] mmc0: cannot verify signal
Further information:
Booting the same laptop into MSWindows lets me insert SD cards whilst the
system is running and it all works as expected. (So not a hardware problem).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I've tested plugging in an SD card to an older laptop (also on hirsute).
That is OK.
I've also noticed that the:
mmc0: error -84 whilst initialising SD card
message appears at boot time if the mmc card slot is empty.
(the "mmc0: cannot verify signal voltage switch" message also appears on
my old
Here's the debug data from card insertion/removal.
** Attachment added: "rtsx debug info"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+attachment/5500291/+files/rtsx.info
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Further info
I've just rebooted the laptop using the kernel that was left over from the
upgrade from groovy.
The mmc card reader works OK there.
A reboot back to the latest hirsute kernel has it failing again.
So:
5.8.0-53-generic - mmc reader works
5.11.0-17-generic - mmc reader fails
-
I can confirm that that 5.11.0-18-generic kernel fixes the problem,
The SD card is now visible and mountable on insertion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929444
Title:
SD card initia
I don't have Secure Boot enabled anyway, so that bit's easy.
As for the v2 kernel - it FAILS (with the -84 error).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929444
Title:
SD card initializatio
The v3 kernel WORKS.
The SD card insertion is detected correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929444
Title:
SD card initialization on insertion fails
To manage notifications abo
Sorry for the delay - the notification mail seems to have gone missing.
Good job I decided to look anyway.
The result is that final WORKS:
==
root@gmllaptop:~# uname -a
Linux gmllaptop 5.11.0-19-generic #20 SMP Wed Jun 2 11:33:21 CST 2021 x86_64
x86_64 x86_64 GNU/Linux
root@gmllaptop:~#
I can confirm that the "author" kernel fixes the problem on my laptop.
(And for good measure I've also tested it on my old laptop, which didn't
show the problem, and it still works there too).
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I've updated to 5.11.0-25-generic and can confirm that my laptop now
sees SDH/XC cards OK.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929444
Title:
SD card initialization on insertion f
This seems to have been fixed.
Probably (?) by today's update to the Android ap (-> 1.15.1).
I can now see my SMS messages on my laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899111
Title:
Public bug reported:
If I run "df" it starts with an error message:
[parent]: df
df: /run/user/4410/doc: Operation not permitted
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs1630320 1604 1628716 1% /run
.
The /run/user/4410/doc (mode r-x--) has bee
>> Thanks, that's being discussed upstream on https://github.com/flatpak
/xdg-desktop-portal/issues/512
No, it's not, as that issue has been closed.
Note that I'm seeing this WITHOUT having flatpak installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
>> You can silence this with "df -x fuse.portal"
I can, but that's not the point.
Whatever is putting the mountpoint there (it's not my choice) should be
putting it there in such a way that this does not happen. I *own* the
mountpoint directory and file-system. Why should I get an EPERM error
th
> If you don't want to this fuse fs to be created
I probably don't, but have no idea want it actually does.
> then either remove xdg-desktop-portal package or mask xdg-document-
portal.service with:
Thanks. The masking worked fine.
--
You received this bug notification because you are a member
Bug #1760095 (mine) reports it for two 17.10 systems (Intel graphics only) both
on 4.13.0-37-generic.
An 18.04beta system 4.15.0-13-generic with the "same" microcode version is OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
> Could someone test out the 4.13.0-38-generic kernel from artful-proposed
> to see if you experience any lock ups with the 3.20180312.0 microcode?
Any simple install instructions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
For me, on my laptop (Intel(R) Core(TM) i5-4330M CPU @ 2.80GHz) with Kubuntu
17.10, the 4.13.0-38-generic kernel (signed image) has the same problem.
In fact it was slightly worse, a it seems to have wiped out my Ubuntu UEFI
booting (boots straight to Windows - I can get to the Ubuntu menu from t
FYI: These are the signatures for my three systems.
Failing for these on 17.10 (4.13.0-37-generic):
signature 0x000306c3 (and for 4.13.0-38-generic)
signature 0x000206a7
OK for this on 18.04beta (4.15.0-13-generic):
signature 0x000306d4
--
You received this bug notification be
>> Installing or removing intel-microcode only runs update-initramfs for
the latest kernel
I eventually noticed that too.
So it means that the problem follows the microcode - nothing to do with the
kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
>> Well, 4.13.0-32 seems to be unaffected...
Only because it isn't the latest kernel you have, so it has never had
the latest microcode added into it - it will still be loading the
previous (working) version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is a similar thread on Arch Linux:
https://bugs.archlinux.org/task/57511
Includes the comment:
"Wasn't the 20180108 microcode update retracted because of issues? Maybe we
should downgrade back to 20171117."
There is no 20180108 download available at Intel now:
https://downloadce
> By any chance, do all of you have sssd installed?
No. I don't have it installed on any of my systems, two of which are
affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759920
Title:
intel
>> And adding 'noibpb' kernel boot parameter helps, at least in my case.
However, according to:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown/MitigationControls
doing that,
"Disabling these features removes mitigations for CVE-2017-5715 (aka Spectre /
Variant 2).", wh
Ignore the attached modified conffile - I'm reporting this from a
different system to the one I've fixed this on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1760855
Title:
logrotate rules do not
Public bug reported:
The logrotate rules for log.smbd and log.nmbd assume that if
/usr/bin/smbcontrol can be run then samba can be restarted.
This ignores the fact that it is possible to have samba installed, but to have
it disabled (you may wish to only enable it for running tests, then disable
A modified postrotate rules that works is:
postrotate
if systemctl -q is-enabled smbd && [ -x /usr/bin/smbcontrol ];
then
/usr/bin/smbcontrol smbd reload-config
else
/bin/true
fi
endscr
Actually
systemctl -q is-enabled anacron 2>/dev/null
works to, and is shorter (and more intuitive).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759846
Title:
Incorrect test used for anacron b
> A lot of the time, people's login name gets renamed from a central
authority...
Another solution would be to get that policy changed, as it's not a good one.
Such a policy would be a nightmare in any industry that has to track who does
what for regulatory purposes, where user ids should be cons
> if someone affected wanted to boot with the apparmor=0 kernel command
line option (with the latest artful kernel, without the noibpb kernel
command line option, and with the latest intel-microcode package), I'd
really appreciate it.
Just done this:
Downloaded latest microcode (3.20180312).
Repl
I've since left the 4.13.0-38-generic kernel + 3.20180312 microcode +
apparmor=0 option running for >30 mins (top constantly running plus a
short compilation using all 4 cores in parallel, make -j4, of a github
download).
It still looked OK.
--
You received this bug notification because you are
>> Also ran:
>>
>> https://raw.githubusercontent.com/speed47/spectre-meltdown-checker/master/spectre-meltdown-checker.sh
FWIW: I just ran that on my system with the *old* microcode, and it
reports "NOT VULNERABLE" for all three variants too.
--
You received this bug notification because you ar
> Define *old* microcode
The microcode from 3.20180108.0+really20170707ubuntu17.10.1:
[parent]: dmesg -t | grep -i microcode
microcode: microcode updated early to revision 0x29, date = 2013-06-12
microcode: sig=0x206a7, pf=0x2, revision=0x29
microcode: Microcode Update Driver: v2.2.
If Intel
Well, I have a problem testing that kernel.
I've downloaded the linux-image and linux-image extra debs and installed
them with dpkg -i.
Rebooting (with the new microcode) hangs.
But on rebooting and checking /proc/version_signature I see:
Ubuntu 4.13.0-38.43-generic 4.13.16
which makes no sense
These are the packages I have installed:
root@gmllaptop:/local/configs/packages# dpkg-query -l '*4.13.0-38*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
My other system (no UEFI) does seem to be OK on this new kernel - and it
is actually running it:
[parent]: cat /proc/version_signature
Ubuntu 4.13.0-38.43+lp1759920.1-generic 4.13.16
[parent]: cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.13.0-38-generic
root=UUID=ca819911-be41-4822-8720-4536f278aa56 r
Well, I *think* I can answer my own question about the signed image.
The signed image was *not* generated by my installing the lp1759920 kernel.
In fact it is the identical file to the one from:
https://launchpad.net/ubuntu/+archive/primary/+files/kernel-signed-image-4.13.0-38-generic-di_4.13.
Public bug reported:
It's trivial to get Dolphin to show a Removable Device as mounted (a
green icon) after Dolphin has actually unmounted the drive.
Steps to reproduce:
1. Plugin a removable device. This will show up in Dolphin under "Removable
Devices"
2. Click on it to mount it.
3. Open a Te
Part of this (the "It is left marked as unmounted and nothing shows in
the listing display. But the device is actually mounted..." part) is
still an issue, and reported separately at:
https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1806154
--
You received this bug notification because you
Public bug reported:
Dolphin is using physical device names to identify locally-attached
devices.
The result of this is that if I boot a system with an external drive
(USB) attached and that happens to be detected first (which happens
every time on my laptop) then the local partitions, which are
Public bug reported:
I have my Desktop Folder settings as:
Layout: Folder View
Location: Show the Desktop folder
The icons are arranged how I want them and locked in place (a 3x8
array).
When I login the icons can be wrongly arranged. This does not happen
every time, but does seem more likely t
>> I don't think there is a solution for this problem.
So why has it only started to happen recently?
What about treating it like a kernel update - don't restart the process
but schedule/request a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
Start plasma-discover because there are pending updates.
Click on "Update all".
When the authentication box pops up Cancel it (I've decided I now want to look
at some information before continuing).
The box goes away.
Click on "Update all" again. It greys-out all buttons, pre
Has it been fixed in/checked for 18.10 (Cosmic)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790613
Title:
Regression: packagekit crashes updating itself to a new version
To manage notifications
Public bug reported:
I run a BOINC project which uses opencl_intel on my Kubunut system
On bioinc the tasks ran in 12,000 +/- 200 seconds.
They've been doing that for ~6 months.
I've now updated the system to cosmic, and the task are not taking
19,000 +/- 200s.
I have another system (which is s
I've no updated the affected systems to Cosmic and the issue has gone
away. Disks now mount "properly" in dolphin.
I'd close the report, but there is no suitable option - if anyone has a
suggestion for that then please go ahead with it.
--
You received this bug notification because you are a mem
** Description changed:
Started an install an selected manual partitioning.
Added sda1 as /boot
Added sda5 as /
- Then realized I'd forgotten to mark sda1 as "Format" so clicked on it's box.
+ Then realized I'd forgotten to mark sda1 as "Format" so clicked on its box.
Crash
===
...although it is, of course, still a bug in bionic, which is an LTS, so
probably closing this report would not be a good idea?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768676
Title:
Incorrect
Good.
I've tested that patch in 4.18.0 and can confirm it works.
https://bugs.freedesktop.org/show_bug.cgi?id=108712#c14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
[regression] Wr
>> Was this report sent from the affected system?
No - sorry. I forgot about that
This is clinfo from the affected system:
Welcome to Ubuntu 18.10 (GNU/Linux 4.18.0-10-generic x86_64)
* Documentation: https://help.ubuntu.com
* Management: https://landscape.canonical.com
* Support:
If it's any help here is the info from the last BOINC startup log under
Bionic and the first under Cosmic.
Bionic:
28-Oct-2018 11:12:30 [---] Starting BOINC client version 7.7.0 for
x86_64-pc-linux-gnu
28-Oct-2018 11:12:30 [---] This a development version of BOINC and may not
function properly
2
Just noticed that the logs in #4 show a difference in the reported GFLOPS peak.
Bioinc says 384, while Cosmic says 192.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
Performance degra
Public bug reported:
If I close thunderbird using File->Quit (or ctrl+Q) the window maximizes
to the screen width just before it closes and retains that max-width on
the next restart.
This does not happen if I close thunderbird with the window-manager's
Close button in the titlebar.
(I don't nor
Looks like there's a bug in dpkg-buildpackage!?!
There's a update_metainfo_xml.py which, from line1, expects to be run by
python3. but
a) it isn't marked as executable.
b) it produces an error when run by dpkg-buildpackage. A complaint about the
encoding= parameter, so it looks like it's being r
The dh_auto_configure reports this:
-- Found PythonInterp: /usr/bin/python (found version "2.7.15")
I've added a python symlink (to python3) in /usr/local/bin to get the
build to run.
but there's a bug in the build logic somewhere.
--
You received this bug notification because you are a membe
Built and installed beignet-opencl-icd_1.3.2-4_amd64.deb with the patch.
clinfo now reports (4 times):
kernel says 24 compute units, hardcoded says 48
Peak GFLOPS reported by BOINC now back at 384.
BOINC running - haven't had sufficient time to check relative processing
speed yet.
System has
>> BOINC running - haven't had sufficient time to check relative
processing speed yet.
I can confirm that it is back to "full speed". Jobs are taking ~12,000s
again.
I've rebooted to the previous Bioinc kernel (still there from the upgrade) and
when I run clinfo there I see:
kernel says 48 com
And, just for confirmation, with the older Bionic 4.15.0-38-generic
kernel I get:
>> root@nuc:/local/users/gml4410/homework# ./gmltest
>> Got value: 48
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
FYI: Boiled it down to a simple ioctl() call.
= Start code =
/* Read an ioctl value */
#include
#include
#include
#include
#include
#include
#include
#include
int main(void) {
int eu_total;
drm_i915_getparam_t gp;
gp.value = &eu_total;
gp.param = I915_PARAM
Just guessing, but a possible candidate...
https://github.com/torvalds/linux/commit/8cc7669355136f8952779e6f60053c1284d59c4d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
Performance
apport-collect 1800752
produced:
>> ERROR: The python3-launchpadlib package is not installed. This functionality
>> is not available.
which might explain why the info wasn't there...
I've installed it - it might now be collecting data...
--
You received this bug notification because you are a
Here's the Bionic kernel info (couldn't seem to be able to attach two
files to one comment?).
** Attachment added: "4.15.0-38-generic (Bionic) dri info"
https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+attachment/5209781/+files/dri-info.4.15.0-38-generic.log
--
You received t
>> Further information may be available in the files (readable only by root,
>> the 0 may be different if you have more than one graphics device):
Info attached (only 0 has those files) for both Cosmic
(4.18.0-10-generic) and Bionic (4.15.0-38-generic) kernels. (The change
mentioned in #14 seems t
>> I've installed it - it might now be collecting data...
No, it's not. It fired up the OAuth authorization page, which I
authorized (and got the mail confirmation). Now it just sits there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
apport information
** Tags added: apport-collected
** Description changed:
I run a BOINC project which uses opencl_intel on my Kubunut system
On bioinc the tasks ran in 12,000 +/- 200 seconds.
They've been doing that for ~6 months.
I've now updated the system to cosmic, and the tas
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1800752/+attachment/5209800/+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/
OK. So I have to run as root *while logged in to desktop of the system*.
Just being logged in as root (on a system where I "never" user the
console...) over the network isn't good enough.
Now done. It claims to have submitted data. I'll change the state to
Confirmed.
** Changed in: linux (Ubuntu)
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1800752/+attachment/5209801/+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/1800752
Only affect Cosmic. Bionic is OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800752
Title:
[regression] Wrong EU count for i5-5250U, reducing OpenCL performance
To manage notifications about th
I've been looking (briefly) for some docs on the Intel GPU hardware
layout.
Came across this:
https://01.org/linuxgraphics/documentation/hardware-specification-prms
leading to:
https://01.org/sites/default/files/documentation/intel-gfx-prm-osrc-bdw-vol04-configurations_3.pdf
which says that a
Or I could post a comment to the commit mentioned in #14 - see what the
author (from Intel) thinks?
Not sure how much printk()s would tell me - the debugfs already shows it
ends up with only 4 EUs pre sub-slice instead of 8. I'll give it a go,
though. But I (might) need signed kernels...I assume i
Thanks.
I'll add relevant links (both ways) if I can as I report it on that site.
If the code hasn't changed in the graphics development branch I may submit a
report now anyway...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
I've opened:
https://bugs.freedesktop.org/show_bug.cgi?id=108712
** Bug watch added: freedesktop.org Bugzilla #108712
https://bugs.freedesktop.org/show_bug.cgi?id=108712
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
They've found the bug!!
https://bugs.freedesktop.org/attachment.cgi?id=142443
Is there a mechanism for getting this patched into the current Cosmic
kernels (and, presumably, Disco)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
Updated to Kubuntu 19.10, which updates Thunderbird to 68 (new add-on
API).
The enigmail (Thunderbird) extension now show up in Firefox Add-ons
labelled as "Enigmail is incompatible with Firefox 69.0.3."
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: enigmail 2:2.1.2-
>>> no longer affects: plasma-workspace (Ubuntu Eoan)
This is incorrect, as I've just had it happen to me (again) and I;m
using Eoan.
Here is my print queue:
[gmllaptop]: lpstat -R
0 MFCJ6930DW-111gml4410 1024 Fri 24 Jan 2020 17:14:13 GMT
1 MFCJ6930DW-111gml4410
>>> This is incorrect, as I've just had it happen to me (again) and I'm
using Eoan.
Although if that actually meant the problem wasn't with plasma-workspace but
rather with print-manager then I disagree.
Clearly plasma-workspace has the ability to crash when presented with incorrect
data. That i
Public bug reported:
The packagekit package has just been updated by discover (Kubuntu) from 1.1.7-1
to 1.1.7-1ubuntu0.1.
Discover reported that the packagekit daemon had crashed.
The resulting dpkg status is:
[parent]: dpkg-query -l 'packagekit*'
Desired=Unknown/Install/Remove/Purge/Hold
| Sta
I've tested the artful kernel on a UEFI system (and tracked own how the
signed kernel is produced from the unsigned on in the debs at he same
time - see #76).
It fixes the issue (tag already changed).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
> I may have experienced this issue also on bionic (18.04) with the
current kernel version as of today (4.15.0-13.14).
I have a system running bionic and it's fine (see #34). Always has been. It's
never run anything else (just over 2 weeks old...). It's always had the "new"
(3.20180312.0~ubuntu1
Public bug reported:
There have been two sets of updates in the last week that are security ones, so
the taskbar icon has a red dot.
After clicking on this and installing the updates Discover reports there are
none. However, the taskbar icon continues to say that there are updates (now
with a b
I've had to reinstall 18.04 on this system to make it usable.
It now works - with (essentially) the same configuration and with no change to
my $HOME files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
/etc/crontab uses
test -x /usr/sbin/anacron
for whether anacron is handling the daily/weekly/monthly cron jobs on a system.
This means that if anacron is installed it is assumed to be running.
However, this is a service, and can be disabled and since the package is
insta
This is still a bug in 18.04 (and was in 17.10 as well).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688148
Title:
Unexpected behaviour when choosing "Other problem"
To manage notifications about
Public bug reported:
This is new at 18.04 (I've just upgraded from 17.10, which was fine).
I open up dolphin and click on an entry under Devices (a mixture of non-auto
mounted local devices and external USB ones).
What I now see happening most times is that the device mounts but I also get an
e
Another set of (related?) issues with this dolphin.
If I right-click on an entry under Devices and select "Open in New Window":
if there is no mount error I get a new window, but it is displaying my Home.
if there is a mount error I get no new window (which may be correct...)
If I right-cl
Well, it's probably not dolphin per se· If I use the dolphin binary form
17.10 exactly the same thing happens, so it's more likely the underlying
mechanisms.
And there is another, probably related, issue.
If I plug in an external USB drive the Device Notifier pops up in the bottom
right of the s
Public bug reported:
System was running fine then the desktop background went black. I continued to
work for a while to tidy things up (open window were OK) and rebooted.
Any attempt to login will produce a black screen shortly after the desktop is
displayed.
The problem is related to this:
[
I've found the two attached crash files for this issue in /var/crash/
** Attachment added: "crashes.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+attachment/5136461/+files/crashes.tar.gz
--
You received this bug notification because you are a member of Ubu
A few other things.
The affect system has these cups processes running:
root@parent:/local/configs/packages# ps -ef | grep cups
root 3421 1 0 01:49 ?00:00:00 /usr/sbin/cupsd -l
lp3423 3421 0 01:49 ?00:00:00 /usr/lib/cups/notifier/dbus
dbus://
lp3424 3
Public bug reported:
Started an install an selected manual partitioning.
Added sda1 as /boot
Added sda5 as /
Then realized I'd forgotten to mark sda1 as "Format" so clicked on it's box.
Crash
=
Traceback (most recnt call last).
File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/Par
PS: The attached system info refers to the system after I'd run a
successful install and configuration. It's not from the installation
screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770402
Tit
FWIW.
That comment about that multiple jobs with the same id shouldn't exist.
I just decided to use the taskbar print-queue viewer (kde-print-queue) and
selected "All Jobs".
At that point it crashed (but only it - plasma was OK).
But "lpstat -W completed" shows this - several multiple entries...
I want 80x24.
So a current workaround is to set 80x22.
But that is not "correct".
I'm still seeing this on 19.04 (Disco Dingo).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755314
Title:
When t
I see the same.
It can access the internal storage OK, but not the SD card.
That may well be because KDE Connect hasn't asked (and obtained) access
to it, either directly (if possible) or using the Storage Access
Framework.
For me, the phone is on Android 10.
--
You received this bug notificati
Public bug reported:
If I try the SMS Message option in KDE Connect the "KDE Connect SMS" window
opens up, but it just contains a spinning "busy" cursor, and stays this way
forever (or at least for as long as I leave it...).
I'd expect to be able to send an SMS message and/or view current ones.
Public bug reported:
If you are writing a message and have only the Composition window open (not the
main reading pane) then when this tries to save the current state of the reply
in the Drafts folder (you've taken a short break whilst writing it) the save
will fail.
The reason is that there is
Public bug reported:
The ExtPack.xml for the VNX ExtensionPack in VirtualBox 6.1.14 (Groovy)
contains:
@VBOX_VERSION_STRING_RAW@
That @VBOX_VERSION_STRING_RAW@ should have been replaced by 6.1.14, but
hasn't been.
Editing the file so that this *is* 6.1.14 allows the extension to load.
NOTE
Still a problem in Groovy (20.10)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806155
Title:
Dolhpin is (still) using physical device names - and these can change
To manage notifications about th
1 - 100 of 322 matches
Mail list logo
