I should add that I experienced this on an AArch64 platform.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839317
Title:
Grub fails to chainload the Windows Boot Manager
To manage notifications
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Tags added: eoan
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697122
Title:
Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel
scrolling with
** Changed in: linux-hwe (Ubuntu)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839693
Title:
p54usb module in
Tested with latest mainline kernel and gnome is failing to start with
similar issue.
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled
seq=1, emitted seq=3
kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process
gnome-shell pid 2210 thread
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837788
Title:
bcache kernel warning when attaching device
To manage
[Expired for samba (Ubuntu) because there has been no activity for 60
days.]
** Changed in: samba (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1279226
[Expired for lvm2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: lvm2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831232
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831232
[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813463
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823725
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832041
[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832609
Title:
i don't
Just an [off-topic] support note, but I would check your sources for
issues with your two architectures (ie. is something missing that has
held back your x86_64 and led to this?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839758
Title:
[amdgpu] System locks up with VMC page
** Tags removed: wily
** Tags added: xenial
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559391
Title:
bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7: bcmwl kernel module
*** This bug is a duplicate of bug 1559391 ***
https://bugs.launchpad.net/bugs/1559391
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1559391, so it is being marked as such. Please
I'm not sure any crash file ending in "122.crash" would be related
because 122 means it was probably the login screen, not your actual
session. Also that crash report seems to be unusable:
https://errors.ubuntu.com/oops/406f2e9c-bc5b-11e9-a5ca-fa163e6cac46
Please:
1. Run:
lspci -k >
** Tags added: nvidia
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-430 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Low
** Changed in: mutter (Ubuntu)
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc4/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839758
Title:
[amdgpu] System locks up with VMC page
** Summary changed:
- System locks up with VMC page fault on Ryzen 2400G and HWE kernel 5.0.
+ [amdgpu] System locks up with VMC page fault on Ryzen 2400G and HWE kernel
5.0.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: regression-update
** Tags added: amdgpu
--
You
Maybe related to bug 1740792.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839759
Title:
Gdm3 asks password randomly when automatic login is enabled
To manage notifications about this bug go to:
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/snapdragon/4.4.0-1122.128/snapdragon-4.4-proposed-published.html
** Tags added: certification-testing-passed
** Changed
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you
This sounds like a regression of bug 1727356. And it appears the patch
for that bug was dropped in mutter version:
3.28.3+git20190124-0ubuntu18.04.1
because it was upstreamed and is in mutter version 3.28.4. And still is.
--
You received this bug notification because you are a member of
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1837596
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1839259
Please:
1. Switch out of recovery mode and boot normally so as to reproduce the
bug.
2. Reboot again into recovery mode and then run:
journalctl -b-1 > preboot.txt
and then attach the file 'prevboot.txt' here.
--
You received this bug notification because you are a member of Ubuntu
Yes, that's the commit. V0.11.1 will be released soon. Apart from this
change, it contains a few minor fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833118
Title:
featherpad does not syntax
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1839257
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.4.0-1118.127/raspi2-4.4-proposed-published.html
** Tags added: certification-testing-passed
** Changed in:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1837592
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/raspi2/4.15.0-1043.46/raspi2-4.15-proposed-published.html
** Tags added: certification-testing-passed
** Changed in:
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
Can you please attach a photo or other evidence explaining how the
display driver is "missing"?
It's meant to be missing in recovery mode, so ignore that part.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
Oh, it's not a bug. Your machine is just stuck in recovery mode:
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
** Summary changed:
- [Intel Conroe] (EE) modeset(0): drmSetMaster failed: Permission
It appears you have an Intel CPU/GPU (Core 2 Duo E4500) and the Xorg
modesetting driver is failing to talk to the kernel driver properly:
[63.574] (EE) modeset(0): drmSetMaster failed: Permission denied
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Summary changed:
-
** Changed in: mesa (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815172
Title:
[bionic] drm/i915: softpin broken, needs to be fixed for
If nothing gets added to the output when the flickering happens then
that answers my question, thanks.
This still feels like a kernel bug if not a hardware problem.
Do you notice any change if you wiggle the laptop screen? Try moving it
forward and backward. We next need to check if it's related
..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839798
Title:
package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to
install/upgrade: package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1
Public bug reported:
..
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture:
Also, did you verify that kernel 5.3 was running successfully?
uname -a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839253
Title:
Excessive screen tearing and flickering
To manage
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839798
Title:
package libdrm-radeon1:i386 2.4.97-1ubuntu1~18.04.1 failed to
install/upgrade: package
** Summary changed:
- Bluetooth mouse sleeps after 5 seconds of inactivity
+ Bluetooth mouse sleeps after 5 seconds of inactivity, but
btusb.enable_autosuspend=0 fixes it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It's difficult because it seems only certain laptop models will be
affected very often. And while no developers are affected by the bug
then it's unlikely to get fixed. Because nobody with the ability to fix
the bug has the hardware to reproduce the bug.
--
You received this bug notification
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839376
Title:
Bionic update: upstream stable patchset 2019-08-07
To
** Tags removed: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501049
Title:
totem crashed with assertion failure [Totem:ERROR:totem-
grilo.c:729:browse_cb: code should not be reached]
To
Can you state which current Ubuntu versions are still affected by this
bug?
** Changed in: totem (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076499
** Summary changed:
- gnome-shell crashed with assertion failure
../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband:
Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed.
+ gnome-shell/cinnamon crashed with assertion failure
** Changed in: linux-azure (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837661
Title:
[linux-azure] CRI-RDOS | Live migration only takes
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579205
Title:
CONFIG_NR_CPUS=256 is too low
To manage notifications about
For those who would like to benefit from this fix, please:
1. For fonts in early boot stage:
Add "fbcon=font:TER16x32" to the GRUB_CMDLINE_LINUX in
/etc/default/grub and run "sudo update-grub" and reboot
2. For fonts after boot (not related to this fix, but you might
need this as well):
Run
And in Ubuntu 19.04. This is getting old. Maybe wayland should relent from
their purist stance (after all Unix always allowed root to do absolutely
anything to the file system, and that's the keys to the kingdom). Maybe Ubuntu
should accept the workaround GParted implements.
But neither
That's a good news, thank you for your patience.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820760
Title:
Teclast F6 Pro touchpad not recognized Ubuntu 18.04.2
To manage notifications about
To check, please upload the output of the command as below:
ls /lib/modules/`uname -r`/updates/dkms
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1523100
Title:
Alsa not detecting internal
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cinnamon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837087
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837087
Title:
** Tags added: xenial2bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839786
Title:
upgrade from 16.04 LTS to 18.04 Bionic Beaver fails - report says it
is impossible to install a required
Public bug reported:
I was installing Ubuntu Mate 19.04 on a Dell XPS17 which has 16 GB RAM
and 2 1TB SHDD drives.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion:
Public bug reported:
Simply Virtualbox stopped working
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: virtualbox-ext-pack 5.1.38-0ubuntu1.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181
Uname: Linux 4.4.0-157-generic i686
ApportVersion: 2.20.1-0ubuntu2.19
*** This bug is a duplicate of bug 1832701 ***
https://bugs.launchpad.net/bugs/1832701
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1832701, so is being marked as such.
With amdgpu.dc=0 I get random mouse lag after moving my mouse quickly.
The cursor will just stop moving. I turned amdgpu.dc=1 and it went away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790861
If you're running on Wayland it might be related to this:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1510
It looks like a busy gnome-shell (or -extension) can eat mouse movement
events, so it might eat keystrokes as well. Second way to reproduce the
issue (for testing whether you
just note the default alphabet for pinyin is latin, not anything else.
We want it just work right out of the box, correct? Well, in 99.9% of
usecases. So user (any user, nub, advanced, etc) installs it and uses
it. With currently used 'default' approach, switching to the method does
not yields
For what it's worth I'm getting a very similar issue on Linux Mint
Cinnamon after the update from 19.1 to 19.2. The error is:
cinnamon: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239:
si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 &&
bottom >= 1' failed.
I've found
*** This bug is a duplicate of bug 1501049 ***
https://bugs.launchpad.net/bugs/1501049
** Description changed:
$ LANGUAGE=C totem
Click 'Channels'
- Click 'MyCloudEX2Ultra'
+ Click 'ServerDLNA'
Click 'Photos'
Click 'All Photos'
In console:
**
Just to clarify: When saying that there is no "right" or "wrong" I meant
the configuration of respective input method, i.e. "default" vs. some
specific layout. We are of course agreed on the fact that e.g. a Russian
layout is not compatible with an input method, which - as you say -
expects latin
Public bug reported:
upgrade from 16.04 LTS to 18.04 Bionic Beaver fails - report says it is
impossible to install a required package.
Currently installed: 16.04 LTS
Tried to upgrade to: 18.04 Bionic Beaver
Upgrade message said to report this problem as a bug.
ProblemType: Bug
@gunnarhj
you are right, this is upstream issue.
And you are wrong about "right" and "wrong" layouts for this input
method. Pinyin implies latin letters input only. So, for example,
neither of languages of ex-USSR is suited for pinyin. Maybe some/many
others as well. When we switching to pinyin
Trying to use the fix in arch wiki does not work:
```
sudo rtcwake -m freeze -s 1
rtcwake: wakeup from "freeze" using /dev/rtc0 at Sun Aug 11 22:42:06 2019
rtcwake: write error
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also using this machine and tried the fix on the arch wiki.
I am using bios 1.35 and fedora 30:
uname -a
Linux x1-yoga 5.2.6-200.fc30.x86_64 #1 SMP Mon Aug 5 13:20:47 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
Can we do something to get better debugging information?
--
You received this bug
When I log in to my (regular user) account early morning, the Switch
User menu item is not present.
When I log out late in the evening, the Switch User menu item is
present.
This is reproducible day in, day out.
This is the case even on days when there are no system updates or
upgrades at all.
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501049
Title:
totem crashed with assertion failure [Totem:ERROR:totem-
grilo.c:729:browse_cb: code should not be reached]
To
*** This bug is a duplicate of bug 1501049 ***
https://bugs.launchpad.net/bugs/1501049
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1501049, so is being marked as such.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your log files attached to this bug report it
seems that there is a problem with your installation media (CD/DVD).
You can verify the integrity of the Ubuntu ISO files you downloaded by
following the
Following up to my remarks from yesterday: when I logged out of my
primary account, I DID see a Switch User menu option from my secondary
account. When I returned to the primary account, Switch User was not
present. But that was yesterday. On reboot today, Switch User has
reappeared in my
Thanks for the response and the explanation Matthew,
the new design is a big improvement, good to know that it's already in the
works!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839756
Title:
** Description changed:
When I am in any program, mostly happen in Blender since I spend most time in
it, PC freezes and becomes unresponsive and I need to hold down Power button to
shut it down.
- After booting I get send report pop up but it doesn't work. Anyway I found
Public bug reported:
When I am in any program, mostly happen in Blender since I spend most time in
it, PC freezes and becomes unresponsive and I need to hold down Power button to
shut it down.
After booting I get send report pop up but it doesn't work it doesn't give me
additional dialog
Unfortunately, i removed the file before reporting the turnaround to
check the theory was good. I forgot to make a backup. But you can see in
the strace into the "read" line that the content of the file si not a
content of a .remmina file compared to other files that start with
Please ensure the installer media image is not corrupt. In this case
UbiquitySyslog.txt reports:
Aug 11 16:12:44 ubuntu kernel: [ 3438.661203] SQUASHFS error: zlib
decompression failed, data probably corrupt
Aug 11 16:12:44 ubuntu kernel: [ 3438.661208] SQUASHFS error:
squashfs_read_data failed
Hi mark, thanks for your report. We plan to improve this interface for
Ubuntu 19.10, as part of the inclusion of Nvidia drivers in the official
Ubuntu repositories.
I think the issue you are seeing, with a newer driver showing as
“tested” while an older one is not, is that the older one is what
The reason your "dyndbg=module e1000" does not work is because
dyndbg=... is only processed at boot time and therefore only affects
*built-in* modules. e1000 is a dynamically loaded module not a built-in.
What you need is the module.dyndbg=... form as in:
"e1000.dyndbg=+p"
See especially line
Looks like that fix is here:
https://github.com/tsujan/FeatherPad/commit/510d740aa556358555dc2ebccd84b8876ef908ba
** Changed in: featherpad (Ubuntu)
Status: New => Triaged
** Changed in: featherpad (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839773
Title:
MicroSD not mounted when inserted, used to
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI
Express Card Reader [10ec:5287] (rev 01)
Subsystem: ASUSTeK Computer Inc. RTL8411B PCI Express Card Reader
[1043:202f]
Flags: bus master, fast devsel, latency 0, IRQ 31
Memory at f7815000
This is correct. The essential thing to understand is the kernel's
command-line uses space as the separator between options so:
option1=1 option2=2 option3=3
option1=1 option2="2" option3="3 or 4"
option1=1 "option2=2" "option3=3 or 4"
are all identical.
What you are seeing in /proc/cmdline is
I could now make it work, reinserting it again after removing it..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839773
Title:
MicroSD not mounted when inserted, used to work correctly
To manage
Public bug reported:
Using Ubuntu+1 (19.10 Eoan), I inserted my Sandisk 32GB microSD with an
adaptor in my laptop's SD slot, but it was not mounted nor apparently
detected. I'm certain that until few weeks ago it was working correctly,
so I suppose the cause to be an update regression.
I tested
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779]
Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5
230 OEM] [1043:03da]
Kernel driver in use: radeon
Kernel
I have recovered my system by going into recovery mode from grub.
I then reset the graphics to generic. It took a few attempts to do the
same thing before the graphics held up on the monitor as per normal
usage. I then booted into Ubuntu Desktop, shut down, restarted and all
was well.
--
You
I can confirm that adding
/etc/ssl/openssl.cnf r,
to /etc/apparmor.d/usr.bin.freshclam and /etc/apparmor.d/usr.sbin.clamd
then run:
apparmor_parser -r /etc/apparmor.d/usr.bin.freshclam
apparmor_parser -r /etc/apparmor.d/usr.sbin.clamd
Makes the apparmor="DENIED" go away.
Also gets rid of
Public bug reported:
Pls see log sent
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Date: Sun Aug 11
Public bug reported:
Crash after disks partitioning.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion:
Hello.
Sorry for writing post by post, but there still are problems with
Mousepad and 'connecting to accessibility bus' during editing any file.
Here is an example:
,[ $ mousepad /usr/bin/example ]
| ** (mousepad:14099): WARNING **: Couldn't connect to accessibility bus:
| Failed to connect
1 - 100 of 152 matches
Mail list logo
