Public bug reported:
I've been using the refresh awareness feature:
https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736
That prevents chromium snap from updating while in use, which prevents a
bug where opening a new tab stops working and gives SIGTRAP. (Very
suboptimal, since now
Ok, but I don't think the installer should crash if a connection fails?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867436
Title:
focal installer crashed
To manage notifications about this bug
However, the resulting system appears to be functional.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867436
Title:
focal installer crashed
To manage notifications about this bug go to:
Public bug reported:
Installer crashed trying to install from the daily live image.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.6
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp
Still fully reproducible with version 5.0.0-19-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829869
Title:
screen flicker with linux 5.0 on RX 480
To manage notifications about this bug
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265282/+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/1829869
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265280/+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/1829869
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265281/+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/1829869
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265279/+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/1829869
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265277/+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/1829869
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265276/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265275/+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/1829869
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265278/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265274/+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/1829869
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265273/+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/1829869
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265272/+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/1829869
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265271/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Trying linux 5.0 from the -edge package on Ubuntu 18.04, I get screen
flicker immediately on the desktop. Booting back to 4.18 the problem
vanished, booting again to 5.0 it manifests itself.
I'm attaching logs in a moment.
---
ProblemType: Bug
ApportVersion:
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265268/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829869
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1829869/+attachment/5265270/+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/1829869
Title:
I upgraded to 18.04 in the meanwhile and am running 4.18 from linux-
generic-hwe-18.04. It has not given me these errors so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787695
Title:
:
Public bug reported:
$ ubuntu-support-status
Support status summary [...]
Your current Hardware Enablement Stack (HWE) is going out of support
on 2023-04-30. After this date security updates for critical parts (kernel
and graphics stack) of your system will no longer be available.
For more
Public bug reported:
Since upgrading to 18.04 the screen lock no longer works. The screen
will not lock automatically despite the setting and even Ctrl+Alt+L and
Super+L fail to do anything.
I've checked that
$ gsettings get org.gnome.desktop.lockdown disable-lock-screen
false
I'm not sure if
Like I said, I was unable to test 4.18. However, on mainline 4.15.18 I
also get a screen lockup, although without a similar trace. Not sure if
that counts, so feel free to correct tagging.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added:
4.18 does not boot. I got an error about missing openssl 1.1 dependency
when trying to install the headers, maybe that's why? There's no openssl
1.1 in xenial.
--
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/1787695/+attachment/5177052/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177051/+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/1787695
Title:
:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177049/+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/1787695
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177045/+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/1787695
apport information
** Tags added: apport-collected xenial
** Description changed:
Since going from 4.13 to 4.15, I'm getting crashes where the system
completely locks up and display freezes. Below is what syslog had after
my most recent.
I'm on Ubuntu 4.15.0-32.35~16.04.1-generic
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177050/+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/1787695
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177044/+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/1787695
Title:
:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177040/+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/1787695
Title:
:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177048/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177046/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177041/+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: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177042/+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/1787695
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177043/+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/1787695
Title:
:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1787695/+attachment/5177047/+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/1787695
Public bug reported:
Since going from 4.13 to 4.15, I'm getting crashes where the system
completely locks up and display freezes. Below is what syslog had after
my most recent.
I'm on Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18, the system is a
Ryzen 1600 on AsRock AB350M with latest UEFI, RX
Sure, below are the steps I did. However, I do not have an artful system
to test on so I'll leave that to someone else.
$ dpkg -l | grep ' tor '
ii tor0.2.9.14-1ubuntu1~16.04.1
amd64anonymizing overlay network
Works here on xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731698
Title:
[SRU] Tor 0.2.9.14 and
Even newer versions with security fixes have since been released:
https://blog.torproject.org/new-stable-tor-releases-security-
fixes-0319-03013-02914-02817-02516
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The newer ones seem to work fine. Either this was fixed or it was
update-grub or somesuch failing me temporarily.
** Changed in: linux-hwe-edge (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
0.2.7 is also unsupported since August 1:
https://blog.torproject.org/blog/tor-0315-alpha-released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662548
Title:
tor 0.2.7.6-1ubuntu1 has
Seems to be fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682167
Title:
location services says it is in use even though it is disabled and
nothing is using it
To manage notifications
Public bug reported:
Using the 4.10.0-26 kernel I get the following error on boot:
error: attempt to read or write outside of disk 'hd0'
This happens every time I try to boot it and stops the boot process. If
I manually choose the previous kernel I had – 4.10.0-22 – the boot goes
fine.
** Tags added: a11y
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698515
Title:
On screen keyboard does not match selected keyboard layout
To manage notifications about this bug go to:
Apparently this only lasts until the second boot. After rebooting again
from the installed system, the command starts to work...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697146
Title:
Unable
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1698515/+attachment/4897491/+files/Screenshot%20from%202017-06-17%2008-37-01.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When choosing another keyboard layout (in my case Finnish) the on screen
keyboard from accessibility settings still uses an English layout with
no umlauts.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu6
ProcVersionSignature: Ubuntu
I reproduced it again using the image from 2017-06-16. Installed from
live system, booted into installed system, immediately opened terminal
and ran `ubuntu-bug gnome-shell`.
According to dpkg -l gnome-shell I have 3.24.2-0ubuntu6
--
You received this bug notification because you are a member
I can reproduce this easily in virtualbox.
** Attachment added: "screenshot"
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1697145/+attachment/4897486/+files/Screenshot%20from%202017-06-17%2008-33-26.png
--
You received this bug notification because you are a member of Ubuntu
There would at least be room in the restart/shutdown/cancel dialog you
get after choosing the rightmost icon from that menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697143
Title:
GNOME
I used today's artful daily 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/1697146
Title:
Unable to report gnome-shell bugs from an installed system
To manage notifications about this bug
Public bug reported:
Running `ubuntu-bug gnome-shell` from within an installed artful system
claims that it is not an official ubuntu package. Running it from the
live CD session works fine.
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Public bug reported:
There is an empty menu with an icon that looks like a keyboard shown in
the login screen.
This can at least be reproduced in the live CD by selecting another
keyboard before boot. I have not tested other ways yet.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package:
Public bug reported:
The location icon is shown and looks the same regardless of whether I
disable location from the menu. As is it offers no useful indication. It
should be hidden when location is disabled.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu6
Public bug reported:
There is no suspend option in the power menu with gnome. There is
supposed to be some modifier + click combination which I forget but no
way to find it out except by accident.
Suspend is a standard feature that's been in the unity menu and should
be retained with the move to
And still in 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1452405
Title:
wmctrl cannot move windows into certain positions
To manage notifications about this bug go to:
Public bug reported:
It seems gnome-software is running in the background all the time. Not a
big deal if it was lightweight, but it seems to use hundreds of MB (from
smem output):
PID User Command Swap USS PSS RSS
2291 jan
I was getting a similar error on 16.04 by running "python -m pip", but
*not* when running "pip" directly. Upgrading CFFI per comment #3 fixed
it.
This is with a system upgraded from Trusty (and before) in case that
matters.
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1098362 ***
https://bugs.launchpad.net/bugs/1098362
See the duplicate bug: yes. You could mention your version there, if it
is newer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has since been fixed in 0.3.17 by checking that the DB is at least
as large as the backup.
** Changed in: uptimed (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is going to xenial *now*? UI freeze was weeks ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551986
Title:
HUD hotkey assignment is suboptimal
To manage notifications about this bug go
Same error here with the beta2 image. Also, the warning message about
efi/legacy things claimed I was installing debian.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521132
Title:
Failed to
Public bug reported:
After updating to the newest version of the fglrx package
(15.201-0ubuntu0.14.04.1) I can no longer log in after a reboot. When I
type a password it takes a couple of seconds to throw me back into the
log in screen. Previous versions worked fine.
Removing fglrx to switch to
Public bug reported:
I see gnome-keyring-daemon using hundreds of meabytes after just a few
days of uptime. Here's one with weeks of uptime:
$ cat /proc/`pidof gnome-keyring-daemon`/status
Name: gnome-keyring-d
State: S (sleeping)
Tgid: 2437
Ngid: 0
Pid:2437
PPid: 2243
TracerPid:
I'm in the same situation, with Ubuntu 14.04.3 and fglrx-updates.
Tried the instructions in comment #18 but did not change anything. The
log file is attached. Also tried removing and reinstalling fglrx, to no
effect.
Problems seemingly started when I booted without the GPU (using Intel
iGPU) to
Public bug reported:
I have a Huawei E392u-12 that does not work in trusty, but does work
out-of-the-box in vivid. Not sure if it is network-manager or something
lower in the stack that is to blame.
$ lsusb | grep Huawei
Bus 003 Device 006: ID 12d1:1506 Huawei Technologies Co., Ltd.
Maybe this is a stupid question, but why is a DKMS failure not
considered fatal enough to prevent the kernel upgrade from taking
place, or at least updating grub?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I ran into 1 GB memory that caused swapping (due to useful programs
using most memory) with the below version in Ubuntu 14.04. It's lasted
for several minutes so far (total CPU time 30 minutes).
The idea that this is not a bug is ludicrous. It must be able to handle
running into bad content – by
apt-get also says:
dpkg: dependency problems prevent configuration of fglrx-amdcccle-updates:
fglrx-amdcccle-updates depends on fglrx-updates; however:
Package fglrx-updates is not configured yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm seeing ibus use over 600MB after just a couple of months of uptime:
PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND
2297 0.0 4.3 693700 354628 ? Ssl Mar23 56:21 /usr/bin/ibus-daemon
--daemonize --xim
2366 0.0 0.0 276700 1152 ?Sl Mar23 0:00
Contrarily, if you already have fglrx installed, you can install the
14.04.2 LTS enablement stack without complaints... but it will not work
(very well). I got constant crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems to say Ubuntu 14.10 now, but the mascot is the old one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1332836
Title:
installation ISO Ubuntu Desktop Utopic Daily - 'Welcome to Ubuntu'
Resolution in the live session is fine, it is only after booting to the
installed system that it degrades to 640x480.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1368784
Title:
Utopic Virtualbox
Public bug reported:
With VirtualBox I get a weird-sized screen with corruption when booting
the utopic RC. Switching to Ctrl+Alt+F1 and back to Ctrl+Alt+F7 fixes
the issue. With trusty (and IIRC early utopic alphas) there is no such
issue.
I'm running VirtualBox 4.3.10 with Ubuntu Trusty as the
I mean this: (see attached)
** Attachment added: screenshot
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1332955/+attachment/4138525/+files/boincmgr.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
There is no exit option in the file menu (just close window), and ctrl+q
doesn't do anything. Right-clicking launcher - Quit also only closes
the window according to bug 926891.
The only way to kill it is via the terminal.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
I no longer have this computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310305
Title:
[Asus M3N78-EM] Mouse/keyboard stop working with 3.11 -lts-saucy
kernel
To manage notifications about
$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
V1.9
09/30/2013
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244079
Title:
[MSI MS-7798] suspend/resume failure
To manage
I'm now on Trusty and latest BIOS and it still doesn't work, so I'm
setting this back to confirmed.
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing hud-service taking hundreds of MB in 14.04, but I don't use
Firefox (I use Chromium). Is this only for the Firefox issue, should I
file another bug, or is there some master bug about current HUD memory
leaks I can subscribe to?
--
You received this bug notification because you are a
Public bug reported:
From an open file dialog I can open browse network from the list and
see computers on my network. However, trying to open a network share
doesn't work: there's a message about the file not being a directory.
Expected: Either the network shares are listed and can be opened
** 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/1006145
Title:
046d:c043 Logitech Mouse not recognised on boot in 12.04 later
To
Public bug reported:
My USB mouse and keyboard work fine with the 3.2 kernels, but after
installing the -lts-saucy kernel + xorg only one of mouse/keyboard work
at boot (despite working in grub) and after unplugging/replugging
neither works.
The light doesn't even come on in the device in
I no longer have the same hardware. Haven't seen this with new hardware
+ Ubuntu 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013980
Title:
Windows stopped responding to mouse
To manage
Public bug reported:
The Ctrl+Alt+Num shortcuts were fixed in saucy (bug #878820), but the
Ctrl+Alt+Numpad 5 one behaves inconsistently.
What happens:
Pressing it once makes the window take the full screen, pressing it a
second time maximizes it, and a third time restores it to full-screen
*** This bug is a duplicate of bug 1080514 ***
https://bugs.launchpad.net/bugs/1080514
** This bug has been marked a duplicate of bug 1080514
Click-and-drag in eye of gnome crashes X
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is still reproducible with the latest fglrx in saucy –
2:13.101-0ubuntu3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1080514
Title:
Click-and-drag in eye of gnome crashes X
To manage
Public bug reported:
When trying to select a file for which I don't have read permissions,
Startup Disk Creator fails to select it, but gives no information on
why. Only by launching from the terminal do I see the reason:
isoinfo: Permission denied. Cannot open 'snip'. Cannot open SCSI driver.
Not sure when this was fixed, but file-roller in saucy correctly creates
the temporary file inside the target folder.
** Changed in: file-roller (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm not going to risk a BIOS update, when the motherboard used to work
fine. Whether a BIOS update would fix the issue or not, this is a
regression in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of
I'm not going to fight over your decision to mark this as incomplete,
but a regression is a regression and there's no evidence a BIOS update
would even fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Resuming from suspend doesn't work in saucy. I'm fairly sure it used to
work in quantal and/or raring on this system.
ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic
Public bug reported:
After a single failed resume from suspend, apport opened ten dialogs for
reporting the same problem.
They were also poorly positioned: in the top-left corner so the controls
were under launcher and top panel.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: apport
Suspend works fine with the latest mainline PPA kernel:
$ uname -a
Linux freyja 3.12.0-031200rc6-generic #201310191635 SMP Sat Oct 19 20:36:43 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
Restarting unity or logging out did not fix this, but a couple of
reboots later it's gone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242007
Title:
Dash finds no applications
To manage
*** This bug is a duplicate of bug 1221041 ***
https://bugs.launchpad.net/bugs/1221041
** This bug has been marked a duplicate of bug 1221041
Xorg crashed with SIGABRT in _mesa_GenTextures()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 351 matches
Mail list logo
