Going back to low resolution 1080p 100dpi, it actually looks decent
there, notice the spacing actually looks sane and there aren't huge
areas of wasted space like at 4K.
So it looks like they only really considered 1080p 100dpi and just
blissfully ignored all other use cases.
** Attachment added:
I'm using my monitor in portrait mode, but it still looks silly even in
normal landscape mode due to it being limited to only 8x3.
** Attachment added: "Gnome 40 - 8x3 grid - landscape"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+attachment/5477349/+files/Gnome%2040%20-
It also doesn't look any better on Gnome 40, which Ubuntu doesn't use
yet.
** Attachment added: "Gnome 40 - 4x6 grid"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+attachment/5477348/+files/Gnome%2040.png
--
You received this bug notification because you are a member of
** Attachment added: "Gnome 3.36 - 6x12 grid"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+attachment/5477346/+files/Ubuntu%2020.04.png
** Description changed:
For some reason after Ubuntu 20.04 (Gnome 3.36) the app grid was limited
to a maximum of 4x6.
This mi
Public bug reported:
For some reason after Ubuntu 20.04 (Gnome 3.36) the app grid was limited
to a maximum of 4x6.
This might be acceptable on an iPhone, which is where they actually got
the limit from, but it is not at all acceptable for an actual large
computer screen. It looks farcical.
Even
The last time I got it to hang long enough to produce a backtrace it
showed:
[1560556.660010] INFO: task vgs:3103183 blocked for more than 1105 seconds.
[1560556.660012] Tainted: G U OE 5.4.0-40-lowlatency
#44-Ubuntu
[1560556.660013] "echo 0 > /proc/sys/kernel/hung_task_timeout_
Actually looking at the patch (shrink_dcache_for_umount) this might not
be the whole problem but may be just related. The problem I am having is
while the system is still running, and cache growing huge, not while
umounting.
--
You received this bug notification because you are a member of Ubuntu
It appears Red Hat fixed this problem with a kernel patch in RHEL 7.5
that was not upstreamed.
https://access.redhat.com/errata/RHSA-2018:1062
BZ - 1471875 - soft lockups during unmount when dentry cache is very
large
https://bugzilla.redhat.com/show_bug.cgi?id=1471875
** Bug watch added: Red H
I haven't verified if this actually fixes the problem but it seems to
make a huge difference in 'free' memory as shown by 'free'.
I had already closed my VMs by the time I tried this so haven't verified
if it stops the long freezes yet.
totalusedfree shared buf
I have this problem as well on Cinnamon, so it doesn't appear to be
specific to KDE. It stalls often and frequently over 15-30 seconds at a
time for no apparent reason. But the swapping to disk may be a clue.
I see this on 5.4.0-40 and have also tried with the lowlatency version
of the kernel and
Has there been any progress on getting rid of initrd or adding stats in
the past 2 years?
Ubuntu 20.04 still uses initrd and a huge one at that, so the plan to
get rid of it seemed to have failed, but without systemd so there are
still no timings like with other dists. Having separate stats breakd
Public bug reported:
Ubuntu 18.04 with HWE
bumblebee 3.2.1-17
This makes laptops with hybrid graphics not work well.
===
bumblebee depends on a versioned xserver-xorg-core package
Depends: bbswitch-dkms | bbswitch-source, lsb-base (>= 3.0-6), xserver-
xorg-core (>= 2:1.18), libbsd0 (>= 0.2.0),
wrt #91 which snaps might those be?
If its the regular 'chromium' snap it certainly doesn't make any mention
of the fact it supports hardware video acceleration or includes the
vaapi patch.
# snap info chromium
name: chromium
summary: Chromium web browser, open-source version of Chrome
pu
Fedora started enabling video acceleration in this build late last year:
* Tue Nov 27 2018 Tom Callaway - 70.0.3538.110-2
- enable vaapi support (thanks to Akarshan Biswas for doing the hard work here)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
As neither Chrome/Chromium or Firefox has any real interest in Linux
support can we get Ubuntu to apply the patch? The patch has existed for
5 years already.
Even a partial solution where its built in but you still have to enable
it in config would be fine. Having to hunt down a ppa to get working
Thanks for the information Dimitri, I didn't realize that was the reason
the times sometimes shows up on some distributions and doesn't on
others.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615685
Its also not clear why Ubuntu's systemd-analyze doesn't report more than
just kernel + userspace times even on Ubuntu 18.04. Both CentOS 7 and
Fedora 27 report times properly, which are using older versions of
systemd.
---
CentOS 7 - systemd-219-42.el7_4.7.x86_64
$ systemd-analyze time
Startup f
Note firmware and loader times only show up when using UEFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615685
Title:
systemd-analyze stats for kernel startup time looks suspect
To manage notif
reply #48
Yes packaged version in main archive, using Ubuntu Mate 17.10 now and
its still not showing the photos mount in Caja (like nautilus). I can
see the Documents mount though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
I should note that the above is while using the regular packaged
versions of idevicepair / ifuse.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1623666
Title:
iOS device contents not displayed in Ub
For whatever reason while trying to backup an iPhone 6s+ 10.3.3 before
upgrading to 11.0 I can't see the photo mount in mate fuse at all but if
I use idevicepair and ifuse from the command line it lets me copy the
files. I'm not sure if this is related to the issue others have reported
above.
--
Here are some further bug reports related to this:
https://github.com/vmware/open-vm-tools/issues/22
https://bugzilla.redhat.com/show_bug.cgi?id=1292234
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872779
Fedora was fixed on Apr 2, and OpenSUSE was fixed a few days ago. Its
not clear why ope
This issue combined with lp#1703499 makes VMWare only able to display
800x600 by default since there is no obvious way to launch Ubuntu using
Xorg and the Wayland patch still hasn't been applied for open-vm-tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Public bug reported:
At login time you can select between "Ubuntu" and "Ubuntu on Wayland" on
Ubuntu 17.10. However both options actually end up running Ubuntu on
Wayland and there appears to be no way to actually run Ubuntu on Xorg.
I'm not certain if this is actually the right package to file t
Update:
Looking at the processes while running it appears both 'Ubuntu' and
'Ubuntu on Wayland' modes _both_ run Ubuntu on Wayland in reality. There
appears to be no regular X mode in Ubuntu 17.10...
Which makes this patch even more important.
gdm 843 0.0 1.2 271332 48588 tty1 S+
Somewhat interestingly Debian 9.1.0 Gnome works in both regular and
Wayland modes with open-vm-tools-desktop 2:10.1.5-5055683-4, but Ubuntu
does not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17034
Correction:
Debian 9.1.0 Gnome with Wayland does not work after reboot (as I
expected without the patch), it appears setting the resolution while in
Xorg mode seems to have fixed it for Wayland temporarily.
Ubuntu 17.10 even when not in 'Wayland' mode does not work though.
Running "vmware-user-su
Just wondering why open-vm-tools was updated without this patch as its
mostly unusable on 17.10 without it, certainly if you are running
regular Ubuntu with a desktop interface anyway.
open-vm-tools (2:10.1.5-5055683-5ubuntu1) artful; urgency=low
* Merge from Debian unstable. Remaining changes
Public bug reported:
open-vm-tools no longer works for Ubuntu 17.10 now that it uses Wayland.
There is a patch to fix this issue in Fedora 26, which I have attached
to this report.
* Sun Apr 02 2017 Ravindra Kumar - 10.1.5-4
- ResolutionKMS patch for Wayland (RHBZ#1292234).
* Thu Mar 16 2017 R
This also affects Spotify and likely Netflix.
Is this going 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/1652110
Title:
Chromium 55+ doesn't support Widevine library
To manage notifi
Alex, you should probably file a new upstream bug about the issue if you
can reproduce it on the upstream 4.11 version. I no longer have a Cherry
Trail system so can't do it myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Kai-Heng,
Yes, but with ASPM disabled unfortunately even ASPT doesn't help enough.
:-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682711
Title:
PCIe ASPM disabled even when enabled in FADT and
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Bug watch added: GNOME Bug Tracker #780078
https://bugzilla.gnome.org/show_bug.cgi?id=780078
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=780078
Importance: Unknown
Status: Unknow
I sent a follow up email to Lenovo but don't expect to hear back from
them until sometime after next Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682711
Title:
PCIe ASPM disabled even when
Talking to Matthew Garrett on irc he said that he thinks this may only
be fixable via an UEFI change.
04:33 < ccheney> anyone know if it is possible to change a setting in LnkCap on
a pci device? My pcie ports apparently have 'ASPM not supported' set and I need
to turn it on somehow
04:33 < cche
The setpci commands I used modified the LnkCtl option but not the LnkCap
values. I'm not sure but suspect that the LnkCap values are what are
causing the problem.
--
LnkCap: Port #17, Speed 8GT/s, Width x4, ASPM not supported, Exit Latency L0s
<1us, L1 <16us
ClockPM- Surprise- LLActRep+
Public bug reported:
This is somewhat similar in issue to lp#1377596.
I have a "Lenovo ThinkCentre m900 Tiny" with an "Intel 600p" NVMe drive
in it.
As far as I can tell from dissembling the FADT PCIe ASPM is not set to
disabled but the ports are not enabled in UEFI during boot.
I also notice t
Public bug reported:
This issue will effectively be a regression in desktop usage once Ubuntu
switches from Unity to Gnome Shell. Gnome Shell does not work well with
multiple monitors unlike every other desktop environment except Budgie,
which is switching away from GTK/Gnome to Qt with Budgie 11
I'm closing this bug as after rebooting onto current linux
4.4.0-43-generic the problem went away.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
blockdev also reports the wrong value:
# blockdev --getsz /dev/sdd1
32787056
strace shows that fstat() reports the wrong value.
9175 02:20:07.714355 open("/dev/sdd1", O_RDONLY) = 3
9175 02:20:07.714387 uname({sysname="Linux", nodename="desktop-clc",
release="4.4.0-38-generic", version="#57-Ub
Taking the first sector output and decoding it shows:
00 - 00 01 01 - 0c - 3f a0 00 - 00 08 00 00 - 00 00 10 00
00 - 00 81 01 - 83 - 3f 20 00 - 00 08 10 00 - 00 00 10 00
00 - 00 01 01 - 83 - 3f 20 00 - 00 08 20 00 - 00 00 20 00
00 - 00 01 01 - 83 - 3f e0 3f - 00 08 40 00 - 00 f8 79 03
Which looks
Public bug reported:
For some reason Linux (dd/mkfs.vfat/mkfs.ext4) treats the first
partition of my sdcard as 16GB regardless of what fdisk says it should
be. dd sees the other partitions as the correct size.
Also if I run mkfs.vfat on the first partition it is treated as a fuse
filesystem when
As noted at the link the code is known wrong for CHT but may have
further bugs:
https://bugzilla.kernel.org/show_bug.cgi?id=150481#c1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625440
Title:
i2
I dug around and found upstream kernel bzs related to this issue:
https://bugzilla.kernel.org/show_bug.cgi?id=150481
https://bugzilla.kernel.org/show_bug.cgi?id=155241
** Bug watch added: Linux Kernel Bug Tracker #150481
http://bugzilla.kernel.org/show_bug.cgi?id=150481
** Bug watch added: L
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744498/+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/1625440
Title:
WARN
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744501/+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/1625440
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744500/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/162
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744496/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16254
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744503/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744502/+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/1625440
Title:
WA
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744499/+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/1625440
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744497/+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/1625440
Title:
WARN
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744495/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625440
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1625440/+attachment/4744494/+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/1625440
Title:
WARNIN
apport information
** Tags added: apport-collected yakkety
** Description changed:
kernel crash on boot rendering sdio wifi and bluetooth from operating on
Nexbox T9 (Intel x5-z8300), works fine under Windows 10. It happens on
both 16.04 and 16.10 with kernel 4.4.0 and on kernel 4.8.0-rc4
Fedora 25 alpha kernel (4.8-rc4) output looks effectively the same:
[ 20.811692] i2c_designware 808622C1:06: I2C bus managed by PUNIT
[ 20.912602] i2c_designware 808622C1:06: punit semaphore timed out, resetting
[ 20.912723] i2c_designware 808622C1:06: PUNIT SEM: 2
[ 20.912803] ---
Public bug reported:
kernel crash on boot rendering sdio wifi and bluetooth from operating on
Nexbox T9 (Intel x5-z8300), works fine under Windows 10. It happens on
both 16.04 and 16.10 with kernel 4.4.0 and on kernel 4.8.0-rc4 on Fedora
25 alpha. The acpi errors don't show up in the 4.8.0 kernel
It was after I entered the username and password. If you look closely
at the picture you can see where it shows my login but won't let me
click through since the window is too small.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
This was on today's version of 16.10.
** Attachment added: "Screenshot from 2016-08-11 23-06-22.png"
https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1612488/+attachment/4719412/+files/Screenshot%20from%202016-08-11%2023-06-22.png
--
You received this bug notification because y
Public bug reported:
When trying to add a Facebook account under System Settings -> Online
Accounts it says the following after trying to login to Facebook.
"Your popup is too small to display this page. Please enlarge it to
proceed."
This is a gray overlay blocking the ability to accept Ubuntu
This is still happening on 16.10 as expected due to the previous setting
of 'Opinion' the only way to work around this issue on VMWare
Workstation is to change the setting under Edit->Preferences->Input
Optimize mouse for games: Always. Disabling "Automatically grab and
ungrab the mouse cursor." do
After rereading the original bug description my issue is slightly
different. I could not see my keyboard or mouse until I applied the
patch in #8. The patch only made the keyboard show up for me though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I have the same problem as the original submitter. The patch appears to
correct the problem for the logitech keyboard but not the mouse. I have
a MK700 keyboard and M705 mouse both of which used to show up via upower
-d.
$ upower -d
Device: /org/freedesktop/UPower/devices/keyboard_0003o046Do2008x0
I'm seeing what appears to be the same bug on linux 3.17.0-031700rc6
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc6-utopic/
Plugging the same devices (HD / wacom tablet) into the on chipset Intel
USB2 controller works fine.
--
[ 156.603076] usb 10-2: new high-speed USB device nu
So I dug around in fdo intel BZ area and found that adding the following
to the kernel may produce better logs:
"drm.debug=0xe log_buf_len=4M"
I have attached the resulting log. It looks a lot like the other bugs
for ThinkPad that have been around for a long time now.
https://bugs.launchpad.net/
I forgot to mention in #2 that the reason I tested and uploaded a new
dmesg was due to multiple entries in the 3.13.0-35.62 Ubuntu changelog
relating to i915 dp support. The changes didn't appear to fix my issue
though.
--
You received this bug notification because you are a member of Ubuntu
Bugs
Still happens on linux-image-3.13.0-35-generic 3.13.0-35.62
Attached updated dmesg output
** Attachment added: "dmesg.3.13.0-35-generic.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360545/+attachment/4195842/+files/dmesg.3.13.0-35-generic.log
--
You received
Any chance of getting this updated in 14.10?
If it wasn't for the Ubuntu specific changes it would have already been
automatically updated as its been in Debian testing since April.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
There is a much newer, by a year, release of exfat-utils 1.1.0 available
in Debian now, along with matching updated fuse-exfat.
It has numerous bug fixes and hopefully will be updated since its needed
for interoperability.
** Affects: exfat-utils (Ubuntu)
Importance: Un
Public bug reported:
There is a much newer, by a year, release of fuse-exfat 1.1.0 available
in Debian now, along with matching updated exfat-utils.
It has numerous bug fixes and hopefully will be updated since its needed
for interoperability.
** Affects: fuse-exfat (Ubuntu)
Importance: Und
** Tags added: utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291827
Title:
STABLE Version 2014.2.15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/n
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)
** Changed in: xserver-xorg-video-intel (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/13
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New => Confirmed
** Description changed:
I have a haswell motherboard with 3 1080p monitors connected, 2 directly
via HDMI and a 3rd HDMI connected to an active displayport dongle. The
monitor on the displayport connection had
** Summary changed:
- [drm] HPD interrupt storm detected on connector DP-1: switching from hotplug
detection to polling
+ [trusty] [drm] HPD interrupt storm detected on connector DP-1: switching from
hotplug detection to polling
--
You received this bug notification because you are a member of
Public bug reported:
This is essentially the same issue as bug #1360545 but on utopic. On
utopic there are also some kernel backtraces as shown below. The system
was completely unresponsive and I had to actually unplug the displayport
dongle to be able to file this bug report.
In addition to the
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1360545
Title:
[drm] HPD interrupt storm detected on connector DP-1: switching fr
Public bug reported:
I have a haswell motherboard with 3 1080p monitors connected, 2 directly
via HDMI and a 3rd HDMI connected to an active displayport dongle. The
monitor on the displayport connection had been working fairly reliably
until I decided to finally upgrade my bios to fix some other i
After watching a few more days most of the time compiz apparently just
doesn't come back at all from suspend, all that is seen is a black
screen with a mouse cursor. That is what happens probably 95% of the
time.
Unfortunately due to Ubuntu dropping the previous 18mo support cycle I
will probably
So I found a temporary workaround that seems to work, whenever it hangs
I can send HUP to compiz and that seems to fix the problem.
eg:
kill -HUP $(pidof compiz)
However this appears to expose yet another bug that minimized windows at
the time of compiz restart essentially disappear permanently,
** Attachment added: "Example of problem"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1313436/+attachment/4098712/+files/image.jpg
** Package changed: xorg (Ubuntu) => unity (Ubuntu)
** Changed in: unity (Ubuntu)
Status: New => Confirmed
** Description changed:
After suspen
Public bug reported:
After suspending and then resuming the system unity/compiz often but not
always becomes extremely slow to respond, so much so that you can see
the transistion from lockscreen to desktop for many minutes (if it ever
finishes). I will attach a picture of what it looks like. I di
Sorry I was out of town for a conference so was unable to respond
quickly.
I just reproduced this bug again with final 14.04, and on top of that it
appears to have passed my password through to the application with focus
behind the screensaver which happened to be IRC (ugh).
** Changed in: unity
I saw it happen this morning but that session was logged in on April 9.
I just logged out and back in after verifying the system is fully up to
date and will monitor to see if the problem occurs again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066481/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302835
Title:
un
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066478/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066480/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302835
Ti
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066479/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302835
Title:
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066482/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302835
Title:
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066469/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302835
Ti
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066468/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066471/+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/1302835
Title:
unit
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066474/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/130
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066465/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302835
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066476/+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/1302835
Title:
un
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066470/+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/1302835
Title:
unit
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066475/+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/1302835
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066477/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302835
Title:
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066460/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302835
Titl
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066473/+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/1302835
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1302835/+attachment/4066472/+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/1302835
1 - 100 of 12419 matches
Mail list logo
