5.13.0-25 fixed for me amdgpu graphics init issue on AMD Ryzen 5 3400G.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956401
Title:
amdgpu hangs for 90 seconds at a time in 5.13.0-23, but
Enabled proposed, kernel updated to 5.13.0-24-generic. Works fine!
Thanks a lot for the quick fix.
System:Host: alrock Kernel: 5.13.0-24-generic x86_64 bits: 64 Desktop:
GNOME 40.5 Distro: Ubuntu 21.10 (Impish Indri)
CPU: Info: Quad Core model: AMD Ryzen 5 3400G with Radeon Vega
Another "slow" kernel on AMD CPU, see also bug 1956408 and bug 1956396
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956532
Title:
Linux Kernel 5.13.0-23 Slows everything
To manage notifications
Observe the same, confirmed that it is an issue with amdgpu failing to
init graphics, see bug 1956399
Not sure how dupes are supposed to be handled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This one and bug 1956396 look like duplicates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956408
Title:
Ubuntu 21.10 very slow after kernel update to 5.13.0-23-generic
To manage notifications
There is a bunch of AMD graphics related bugs associated with the latest
kernel update on 21.10. I wonder whether they could have common root
cause. Personally, I observe the same behavior as described in comment
#4 above, I've submitted bug 1956399.
--
You received this bug notification because
Confirmed that graphics init fails: when system is restarted with broken
kernel, it is accessible via ssh.
Grepping for amdgpu in kern.log results in:
Jan 5 18:50:53 alrock kernel: [3.910928] [drm] amdgpu kernel modesetting
enabled.
Jan 5 18:50:53 alrock kernel: [3.911042] amdgpu:
Public bug reported:
After latest upgrade of linux-image to 5.13.0.23.34 system seem to boot,
but it looks like graphics does not initialize correctly. After showing
initial init logging, at the moment when X should init and graphics
login should appear, monitor just goes to sleep and provides
Something in the updates made it work for me.
On the latest series of updates I've noticed kernel update to
4.18.0.9.10 and gave it a try. I still observe in dmesg diagnostics dump
about "Bad or missing usercopy whitelist? Kernel memory exposure
attempt..." but I am able to start session with
@NiBu what do you mean by: "Booting in recovery mode and resuming normal
start works."?
On Tue, 9 Oct 2018, 22:15 NiBu, <1796...@bugs.launchpad.net> wrote:
> Booting in recovery mode and resuming normal start works.
>
> --
> You received this bug notification because you are subscribed to the
Also seen it. It was first thing I did. Forgot to mention it.
See comment #4 above: it was done with libelf-dev installed.
On Tue, Oct 9, 2018 at 1:10 PM Cristian Aravena Romero
wrote:
> Hello,
>
> In 'make.log':
>
> 'Makefile:958: "Cannot use CONFIG_STACK_VALIDATION=y, please install
>
Found patch [0] fixing module build. Observe the same behavior.
[0]
https://www.hlmjr.com/index.php/2018/08/21/nvidia-drivers-390-77-vs-linux-kernel-4-18
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes it is started right after the upgrade from 18.04. 18.04 with the
latest SW was running just fine (on kernel 4.15.0-36-generic). Have not
seen it working on 18.10.
Tried 4.19-rc7.
Observations:
* Update manager "enables" driver, but it is not loaded
* Manual install of nvidia-driver-390
*** This bug is a duplicate of bug 1796726 ***
https://bugs.launchpad.net/bugs/1796726
Data collected by "ubuntu-bug linux", while system was using proprietary
nvidia driver can be found in bug 1796730
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Extra info for bug 1796433
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
Public bug reported:
Extra info for bug 1796433
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
Submitted bug 1796726
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796433
Title:
Ubuntu 18.10 regression: nvidia driver does not work
To manage notifications about this bug go to:
Public bug reported:
Problems started after upgrade to 18.10 and first reboot.
Symptoms:
* Login screen appears
* After providing credentials desktop does not start
Part of dmesg:
-
...
[ 10.482929] resource sanity check: requesting [mem
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796433/+attachment/5197786/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry for late reply. Fixed in 4.15.0.24.26. Just checked changelog,
indeed #1752772 fixed in this kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Title:
[18.04] Regression:
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759644
Title:
[18.04] Regression: wired network does not work upon resume from
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095257/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095254/+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/1759644
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095248/+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/1759644
Title:
apport information
** Tags added: apport-collected
** Description changed:
After upgrade to 18.04 (bionic) I've encountered the following
regression: wired network connection does not work, when system is
resumed from suspend.
Reloading the kernel driver module seems to help:
sudo
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095250/+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/1759644
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095251/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095261/+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/1759644
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095259/+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/1759644
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095258/+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/1759644
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095260/+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/1759644
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095253/+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/1759644
Title:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095256/+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/1759644
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095249/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095255/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1759644/+attachment/5095252/+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/1759644
Title:
Public bug reported:
After upgrade to 18.04 (bionic) I've encountered the following
regression: wired network connection does not work, when system is
resumed from suspend.
Reloading the kernel driver module seems to help:
sudo modprobe -r r8169
sudo modprobe r8169
Could this be fixed
Public bug reported:
After latest set of updates to the system it could not boot from SSD anymore
displaying the message:
--
Reboot and select proper Boot device
or Insert Boot Media in Selected Boot device and press a key
-
$ env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug
/var/crash/_usr_bin_gnome-shell.1000.crash
*** Send problem report to the developers?
After the problem report has been sent, please fill out the form in the
automatically opened web browser.
What would you like
@Daniel
Even
env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug
/var/crash/_usr_bin_gnome-shell.1000.crash
does not provide needed link.
Are there any system settings that can affect this behavior?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1741886/+attachment/5034292/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1741886/+attachment/5034294/+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/1741886
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1741886/+attachment/5034293/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Upon physical disconnect/connect of a monitor (connected via HDMI) shell
crashes with signal 11.
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
$ apt-cache policy gnome-shell
Well, I have done what you suggested. Invoking ubuntu-bug on a crash
file creates corresponding upload* files but does not print any links.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741886
@Daniel
The above commands do bring me to a web-page, but there are no uploaded
relevant error reports, although I see them in /var/crash
** Attachment added: "/var/crash screenshot"
Public bug reported:
Upon physical disconnect/connect of a monitor (connected via HDMI) shell
crashes with signal 11.
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.26.2-0ubuntu0.1
Expected is that physical
Another possible duplicate:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676547
Title:
No network connectivity after upgrade from
Looks like duplicate of https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1676547
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687262
Title:
16.10, 17.04, 17.10 Wired connection
@Joseph: no point, as indicated multiple times, network card works with
current kernel 4.12.0-13, when configured in /etc/network/interfaces
When similar was observed after upgrading of another system with completely
different hardware:
*-network DISABLED
description: Ethernet interface
** Tags removed: kernel-request-4.10.0-22.24
** Tags added: regression-release
** Description changed:
+ == Regression details ==
+ Discovered in version: yakkety
+ Last known good version: xenial
+
This is a regression.
Upon upgrading 16.04 -> 16.10. Wired connection provided by
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** Summary changed:
- 16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411
+ 16.10, 17.04, 17.10 Wired connection stopped working RTL 8111/8168/8411
** Tags added: artful
--
You received this bug notification
Upgraded to artful beta - the issue persists.
$ lsb_release -a
LSB Version:
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
** Changed in: linux (Ubuntu Zesty)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687262
Title:
16.10, 17.04 Wired connection stopped working RTL 8111/8168/8411
Bug is still relevant.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename: zesty
uname -a
Linux hosty 4.10.0-26-generic #30-Ubuntu SMP Tue Jun 27 09:30:12 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ apt-cache
Live Ubuntu 17.04 session is running OK (mentioned in original report) and it
is using:
-
$ apt-cache-policy linux-image-generic
linux-image-generic:
Installed: 4.10.0.19.21
Candidate: 4.10.0.19.21
Version table:
*** 4.10.0.19.21 500
500
Public bug reported:
This is a regression.
Upon upgrading 16.04 -> 16.10. Wired connection provided by
"RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" has stopped
working.
Quickly looked around for possible solution, and decided to go on with
upgrade to 17.04, since it was my
** Attachment added: "bug_2017-03-24_22-22-32.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+attachment/4845050/+files/bug_2017-03-24_22-22-32.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Upon resuming system from suspend I observe graphical artefacts.
This is a regression, since I've noticed this behaviour only after
latest updates.
Rebooting system resolves the issue.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Yes. After re-install of grub kernel boots fine.
On Fri, Dec 2, 2016 at 5:19 PM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:
> Are you no longer having issues booting 4.4.0-51.72 after re-installing
> grub?
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => High
>
> **
Public bug reported:
After kernel upgrade system could not detect boot device anymore.
Right after BIOS the following was prompted:
Reboot and select proper Boot device
or Insert Boot Media in Selected Boot device and press a key
Problem was resolved (thanks to Eric^^ support at #ubuntu irc) by
+1
On Fri, Jun 3, 2016 at 3:26 AM, Anupam <1546...@bugs.launchpad.net>
wrote:
> just experienced once again, even after updating to OTA-11
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1546733
>
> Title:
> Update
Public bug reported:
Ubuntu Touch OTA 10.1 on BQ Aquaris M10 FHD
Currently, there is no way (or I could not find one) to switch keyboard
layout, when external keyboard is connected to the device. Tried
possible "default" combinations like: Alt+Shift, Ctrl+Shift, Ctrl+Space,
without luck.
With
Public bug reported:
In dual-SIM configurations, when phone receives a call, SIM-card in use
is being indicated. The list of calls does not show this information,
however. It is only available in the call details.
Providing this information in a list of calls will help user to phone
back using
By advice 'k1l' on #ubuntu+1 moved away .config folder. It solved the
issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567591
Title:
[xenial] unity session does not start
To manage
I seem to be bitten by the same or similar issue on Xenial (16.04), see
bug 1567591
This is also a regression. Happen to me just recently (after SW update
some days ago).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
$ lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
$ apt-cache policy unity
unity:
Installed: 7.4.0+16.04.20160401.1-0ubuntu1
Candidate: 7.4.0+16.04.20160401.1-0ubuntu1
Version table:
*** 7.4.0+16.04.20160401.1-0ubuntu1
Puzzled...
Was this instruction for me to do something???
On Wed, Mar 2, 2016 at 12:51 AM, Raymond <1551...@bugs.launchpad.net>
wrote:
> ports: analog-input-front-mic: Front Microphone (priority 8500, latency
> offset 0 usec, available: no) properties: device.icon_name = "audio-
>
Public bug reported:
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
Expected behavior:
Sound is played-back via headphones, when they are plugged-in.
Observed behavior:
Unplugging/plugging-in headphones disables headphones sound.
To restore sound, user needs to
Interesting...
Pawel: Could you please provide a couple of words, why change of status to
invalid?
P.S. Maybe a good idea to always provide a short rationale for change of
status?
On Thu, Feb 18, 2016 at 1:06 PM, Pawel Stolowski <1546...@bugs.launchpad.net
> wrote:
> ** Changed in:
Albert: No, after reboot refresh works OK.
On Thursday, February 18, 2016, Albert Astals Cid <
albert.ast...@canonical.com> wrote:
> Alexey: If you reboot can you get
> https://launchpadlibrarian.net/240240439/step01.png just by pulling down
> the today scope to refresh?
>
> --
> You received
Nope, no sign of .crash files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546733
Title:
Update of today screen messes up scopes layout.
To manage notifications about this bug go to:
** Attachment added: "scope-registry.log"
https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573922/+files/scope-registry.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546733
** Attachment added: "unity8.log"
https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573921/+files/unity8.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546733
Title:
Update
** Attachment added: "unity8-dash.log"
https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573920/+files/unity8-dash.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546733
Title:
Wanted to apply patches from #12 and #13, but files are read-only. Looks
like I miss some knowledge. Any pointers are welcome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491566
Title:
Shell not
Actually, I tried buttons, there was no visible reaction on the presses:
* volume buttons (even attempted to get a screenshot, but it is not present
on the phone, so it did not work)
* power button. could not even reboot the phone (or maybe have not waited
long enough? pressed on it for about a
Attaching unity8.log as advised by Pat McGowan.
** Attachment added: "unity8.log.1.gz"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1491566/+attachment/4456964/+files/unity8.log.1.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Observed similar issue on BQ E4.5., r25 (after OTA6 update).
Dialer locked UI.
Happened after dialing back via activation of dialer from missed call
notification (without unlocking the phone). Dialer remains on the
foreground and phone UI seems to be stuck. At the same time, icons in
the
Once device unlocked, all functionality seems to be OK: yes, I can switch
between apps/start apps using launcher, also can switch between apps/kill
apps using swipe from right.
On Mon, Jun 15, 2015 at 10:25 AM, Michael Zanetti
michael.zane...@canonical.com wrote:
Once the device is unlocked,
Public bug reported:
Can't get to unlock: when I try to swipe away lock screen nothing
happens.
Can get beyond the screen using active icons in the notification area,
e.g. if I select battery indicator and then options, input secret code
screen gets activated and I can access the device.
Since update to r21: Bluetooth crash issue is gone. Device connects OK.
Can start/finish calls. Nice!
Have not check other functionality though (like address book sync).
Extended functionality like:
* indication of mobile signal strengths on the car dashboard/phone screen
* synchronization of
Since update to r21: Bluetooth crash issue is gone. Device connects OK.
Can start/finish calls. Nice!
Have not check other functionality though (like address book sync).
Extended functionality like:
* indication of mobile signal strengths on the car dashboard/phone screen
* synchronization of
Since update to r21 few weeks back: Bluetooth crash issue is gone. Device
connects OK. Can start/finish calls. Nice!
Have not checked other functionality though (like address book sync).
Extended functionality like:
* indication of mobile signal strengths on the car dashboard/phone screen
*
Since update to r21: Bluetooth crash issue is gone. Device connects OK.
Can start/finish calls. Nice!
Have not check other functionality though (like address book sync).
Extended functionality like:
* indication of mobile signal strengths on the car dashboard/phone screen
* synchronization of
** Description changed:
Ubuntu 14.10 (r20, 24.03.15) on BQ Aquaris 4.5 UE
Not sure what exactly triggers it, but symptoms are:
* When trying to disable BT from notification area - indicator switches to
on again.
* In the settings - BT only on/off control is active and no other info
Public bug reported:
Ubuntu 14.10 (r20, 24.03.15) on BQ Aquaris 4.5 UE
Not sure what exactly triggers it, but symptoms are:
* When trying to disable BT from notification area - indicator switches to on
again.
* In the settings - BT only on/off control is active and no other info
The following
** Description changed:
Ubuntu 14.10 (r20, 24.03.15) on BQ Aquaris 4.5 UE
Not sure what exactly triggers it, but symptoms are:
* When trying to disable BT from notification area - indicator switches to
on again.
* In the settings - BT only on/off control is active and no other info
** Description changed:
Ubuntu 14.10 (r20, 24.03.15) on BQ Aquaris 4.5 UE
Not sure what exactly triggers it, but symptoms are:
* When trying to disable BT from notification area - indicator switches to
on again.
* In the settings - BT only on/off control is active and no other info
The same as in comment #101 for nvidia-331-updates on 14.10 (utopic)
nvidia-331-updates 331.113-0ubuntu0.1: nvidia-331-updates kernel module
failed to build
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
\todayrussian command returns date string in ancient Russian instead
of plain Russian, which is visible in certain names. For example, for
the 1st of June 2014 one expects to see 1 июня 2014 г. whereas 1 iюня
2014 г. is printed.
The bug is in russianb.ldf of CTAN
Hi Michael,
Thank you for looking into this. Yes, I think it is a duplicate of Bug
#891586
After reading it through, I do not get why resolution list is not
computed correctly: on my unit it should be intersection of
x/y-resolution lists, there are no other units attached, i.e. there
should be
Public bug reported:
Scanner ID: Bus 001 Device 004: ID 04b8:0852 Seiko Epson Corp.
I have a good faith belief that this is a bug in Simple Scan and not in
sane-backends because I actually tried with xsane and it worked there.
Essence of problem: I do not see difference in files saved after
Looks like there was a similar crash in FreeCAD (Package: freecad; Version:
0.12.5284-dfsg-5ubuntu1; Architecture: amd64):
Just select Menu Help - About FreeCAD and then press OK.
With new package out of proposed it is fixed. Thanks.
--
You received this bug notification because you are a
Here we go...
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/949682/+attachment/2837588/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949682
Usual procedure:
- Downloaded image and checked it against MD5SUMS file
- Burned it to CD
- Booted from the CD and ran integrity test, which detected no errors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
With respect to comment #4: fails for me on 32-bit here when I try to
install from precise beta1 Live CD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/841807
Title:
ubiquity crashed with
Public bug reported:
Wanted to report issue with ubiquity on precise beta 1 live cd.
Ran:
apport-bug ubiquity
Got dialog:
The system log from your installation contains an error. The specific error
commonly occurs when there is an issue with the media from which you were
installing. Please
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949682
Title:
Can not create bug report - no way to go around faulty apport decision
To manage notifications about this bug go to:
Despite suggestion above that it may work with 10.10... Well, it does
not, I just faced this issue. If I read it correctly, the problem is in
libmusicbrainz4c2a and it looks like the same version is used in 10.10
and 11.04, i.e. the functionality is broken through the whole range of
Ubuntu
1 - 100 of 300 matches
Mail list logo
