Hi, I'm on Ubuntu 23.10 using Brave browser SNAP and I still face the
issue (cannot open links in evince -using Brave browser snap).
Here are the versions:
```console
❯ apt list --installed | rg 'evince|apparmor'
apparmor/mantic,now 4.0.0~alpha2-0ubuntu5 amd64 [installed,automatic]
Public bug reported:
Installation failed during upgrade from 20.04LTS to 22.04LTS
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libreoffice-common 1:7.3.7-0ubuntu0.22.04.3
ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252
Uname: Linux 5.4.0-166-generic x86_64
ApportVersion:
Public bug reported:
Installing pulseaudio/focal-updates,now 1:13.99.1-1ubuntu3.13 amd64
recommends packages
pavumeter paman paprefs ubuntu-sounds
Attempting to install paman gives error:
Package paman is not available, but is referred to by another package.
This may mean that the package is
Upstream feature request: https://github.com/canonical/lightdm/issues/95
** Bug watch added: github.com/canonical/lightdm/issues #95
https://github.com/canonical/lightdm/issues/95
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Yes, please; let's get back to the core issue. The Firefox print
function does not save functioning hyperlinks when the output is PDF. I
dislike having to switch to Chromium (I use Linux) to create a PDF with
functioning hyperlinks. Can we please get Firefox to create a PDF with
hyperlinks that
** Changed in: alsa-driver (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1720693
Title:
[10MVCTO1WW, Realtek ALC294, Black
Proposed update fixed the issue, thanks.
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
$ apt policy libgl1-mesa-dri
libgl1-mesa-dri:
Installed: 17.2.4-0ubuntu1~16.04.4
Candidate: 17.2.4-0ubuntu1~16.04.4
Version table:
*** 17.2.4-0ubuntu1~16.04.4
*** This bug is a duplicate of bug 1667085 ***
https://bugs.launchpad.net/bugs/1667085
Public bug reported:
Je suis français. Je ne comprends RIEN à ce qui est écrit.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsane 1.0.25+git20150528-1ubuntu2 [modified:
Hello.
I Still have this problem with Thunderbird on Ubuntu 16.10 :
- with 1 gmail account, Thunderbird is ok
- with 2 gmail accounts, Thunderbird crashes.
However my Thunderbird package is 1:45.5.1+build1-0ubuntu0.16.10.1.
I have the same bug on Ubuntu 14.04.
So the bug hasn't been fixed...
And still present in version 5.1.4.2, under Linux version 4.4.0-36-generic
(buildd@lcy01-01) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) )
#55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016
Very annoying, had a similar problem with jEdit, which I could solve. It is a
very annoying
I'm back to testing u-s-d started under systemd, and I found some
serious wackiness observing `sudo journalctl -f` when I use the
brigtness up/down hotkeys.
The attached "wacky-journalctl.txt" file has the output of `sudo
journalctl -f` during which I used the brightness hotkeys *twice*, and
`sudo forkstat -D 4` when u-s-d is started under systemd and I press the
brightness up hotkey.
** Attachment added: "with-systemd.txt"
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756099/+files/with-systemd.txt
--
You received this bug
Okay, an interesting hint is that this problem seems to be fixed if
u-s-d is started under the Upstart user session instead of the systemd
user session.
If anyone wants to try this, just comment out these three lines in
/etc/X11/Xsession.d/00upstart:
if [ "${1#*.target}" != "$1" ]; then
@Marco: thanks for the FYI!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1598770
Title:
Unity in low-graphics mode has animations and unneeded redraws
Status in
Here's another screenshot that shows the SegvAnalysis.
In my testing thus far, this failure (assuming it's related to this
unity/nux change) only seems to happen when trying to install under
qemu. I tried -vga qxl, -vga std, and -vga virtio... none of them yield
a working installation. Compiz
Possibly as a result of this change, unity/compiz is failing to start
when trying to install from the latest 16.04.1 daily ISO under qemu
(xenial-desktop-amd64.iso 20160713, sha1sum
c9b1ad9b1044c4e68684395daa3f85e016491c3a).
I attached a screenshot as I couldn't file a bug from within the qemu VM
Public bug reported:
I'm under Ubuntu 16.04
kernel : Linux micronet-HP 4.4.0-24-generic #43-Ubuntu SMP Wed Jun 8 19:27:37
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux.
from the very beginning I could not be connected thru wifi.
The guy in charge of this bug, bug already declared and on which we
Also just got greeted by this message. QkiZ's fix seems to work for me
as well (for the last few reboots), but given the sporadic nature of the
bug I can't be sure.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
On a whim, I just checked in on this with the 20160601 Xenial daily
amd64 ISO (sha1sum e07c8b4df1fc71a487fafb309bd318041a65774f), and
everything works great:
http://cdimages.ubuntu.com/xenial/daily-live/pending/
So seems things are on track for this not being a problem in the 16.04.1
release.
Also, the graphical Ubuntu Software Updater is likewise hanging
indefinitely.
And I've confirmed this on 3 different systems so far.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
Public bug reported:
Just ran `sudo apt-get update`, which is hanging indefinitely after the
downloads complete, the last CLI output from which is:
Fetched 733 kB in 1s (399 kB/s)
Looking at `top` suggests `appstreamcli` is the culprit as it's pegged
at near 100% CPU usage:
100 0.1 18:29.02
Okay, seems that "Download updates while installing" has no effect with
the Ubiquity version on the 16.04 ISOs.
I filed a bug against Ubiquity for this, would appreciate if someone
could confirm my findings:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232
--
You received this
@seb128... I'll try to get some better debug info soon. Interestingly,
it only seem to happen with Intel 7260 WiFi cards (and not, for example,
with Intel 8260 WiFi cards).
So I'm not sure whether what we're seeing is actually a problem with
network-manager. I'm now kinda thinking it's more
With this proposed package, System76 is seeing network-manager crash
upon the first resume from suspend. Anyone else experiencing this?
I'll be looking into this more today.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
Hmm, I just tried this on Skylake hardware, and "Download updates while
installing" isn't doing the trick.
Could be that "Download updates while installing" is broken on the 16.04
ISOs, or this could be a result of the phased updates done by the Ubuntu
Software Updater and related components that
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
Abhinav,
Sounds like you're encountering a different bug, or perhaps your ISO
file is corrupted. Have you verified the checksum of your download?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
** Description changed:
- Currently it's impossible to install from xenial-desktop-amd64.iso on a
- wide range of hardware with Nvidia GPUs.
+ [Description updated to reflect state of 16.04 release ISO]
- The problem is invalid opcode(s) when using llvmpipe (the software
- opengl fallback,
Just confirmed on Skylake hardware that llvm-toolchain-3.8 from proposed
fixes this issue on Skylake hardware using llvmpipe.
Thanks!
** Changed in: system76
Status: Triaged => Fix Committed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
After further investigating, it seems this bug doesn't effect Haswell-E
after all, sorry about the confusion.
Will continue to report back as we learn more.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
I can confirm that tjaalton's above test packages fix the problem on a
Skylake laptop with an i7-6700 CPU and an Nvidia 970m GPU when using the
nouveau driver.
I installed libllvm3.8_3.8-2ubuntu1.1_amd64.deb from a VT then rebooted,
and now I have working Unity again.
--
You received this bug
Oh, and another bit of information: our laptops all use embedded Display
Port for their connection to the internal screen, and in this case, this
bug always manifests.
So at least in our testing so far, both eDP and DP seem to be effected.
--
You received this bug notification because you are a
So there seems to be a curious pattern with this bug (which might
provide an important hint): on desktop systems with 970 GTX or 980 GTX
cards, this bug always seems to happen when connected to a monitor over
DisplayPort, but does *not* seem to happen when connected to a monitor
over HDMI.
We'll
** Changed in: xorg-server (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1561685
Title:
x-staging: 1.18.2-2ubuntu0.1 host breaks
Correction: this is fixed as of 1.18.3-1ubuntu2.
1.18.3-1ubuntu1 still had this problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1561685
Title:
x-staging:
I'm no longer having this problem as of 1.18.3-1ubuntu1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1561685
Title:
x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu
Okay, I just tried this on an Intel GPU system, and it has the same
problem.
Arrow keys are broken with 1.18.2-2ubuntu0.1, but work fine with
1.18.1-1ubuntu4.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Public bug reported:
This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow
keys on qemu guests.
Actually, I'm not sure it breaks the arrow keys on the guest in all
scenarios, but it at least breaks them in the pre-boot menu when trying
to install a qemu VM from an ISO.
For
Pointlessly aggravating to break something that long term linux users
have relied on for years. At a minimum, a comment in the default
/etc/hosts would be useful.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Likewise, I've been doing extensive testing with mesa 11 from the
x-staging PPA on Haswell, Broadwell, and Skylake hardware, haven't hit
any issues.
Timo, when do you expect mesa 11 to at least hit wily-proposed? I'll
admit it makes me a bit nervous that mesa 11 isn't in wily proper yet :D
--
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1436330
Title:
Network Manager doesn't set metric for
Fix seems solid.
`route -n` with up-to-date Vivid:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.17.76.1 0.0.0.0 UG1024 00 eth0
10.17.75.0 0.0.0.0 255.255.255.0 U 0 0
Quick question: mesa11 depends on libllvm3.7, but libllvm3.7 is still in
universe.
Is there a plan to promote libllvm3.7 to main?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Oops, never mind... I see that libllvm3.7 being in main is mentioned in
the summary, sorry for the noise!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe] Mesa 11.0.0
Karl,
FYI, network-manager should ignore any interfaces defined in
/etc/network/interfaces.
Which is not to say this bug isn't frustrating, just that you should be
able to manually configure things as you wish without removing network-
manager :D
--
You received this bug notification because
Timo,
Awesome, thanks for the quick fix! I'll test it under qemu as soon as
the builds are finished.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe] Mesa
Timo, 11.0.0~rc2-1ubuntu1~ppa2 seems shiny with Unity under qemu.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1484279
Title:
[FFe] Mesa 11.0.0
Status in mesa package in
I've started testing the mesa 11 rc2 packages here:
https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging
One issue I've hit is that with mesa 11 rc2 installed, Unity will no
longer run under qemu (note I'm testing with an amd64 VM, Wily host and
Wily guest).
Attaching the full unit7.log
I spent a lot of time beating on the proposed Trusty nvidia-346
(346.82-0ubuntu0.2) and nvidia-340 (340.76-0ubuntu0.1) packages
yesterday, and things seem solid to me.
Package upgrade/downgrade paths I tested:
331 -- 340
331 -- 346
340 -- 346
346 -- 340
I tested that things work correctly re
+1 on getting this properly fixed in the mesa Depends, but at least
fixing it in the ISO manifest is a huge step forward.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1479524
** Tags added: 14.04.3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1479524
Title:
Totem Crashes at launch from missing libwayland-egl
Status in System76:
New
Status in totem
** Also affects: system76
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1479524
Title:
Totem Crashes at launch from missing libwayland-egl
As with 14.10, this problem isn't happening with Ubuntu MATE 15.04.
Haven't tried the other flavors yet, but I'm guessing that again this is
only happening with Ubuntu/Unity.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
FYI, this bug wasn't initially present on the final 15.04 release, but
has since raised it's ugly head again on 15.04.
Not sure what has changed, but from my previous experience, my bet is
still on `unity-greeter`, even though I'm not sure how exactly it's
causing it.
--
You received this bug
For what it's worth, network-manager 0.9.10.0-4ubuntu15.2 seems to fix
the problem for me.
`route -n` with *ubuntu15.1 with both WiFi and Ethernet connections:
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse Iface
0.0.0.0 10.17.75.1
Public bug reported:
Steps to reproduce
===
1) Enable both a WiFi connection and plug into Ethernet
2) Test your network connectivity or run `route`
Expected results
=
NetworkManager should prefer the wired connection over the WiFi
connection, and `route` should return
Thanks, Chad!
Note that I'm almostready with a revised patch, so my current patch
shoudl be ignored for now.
My revised patch will incorporate your suggestion for the preinst
script.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
To hopefully make this fix easier for the nvidia driver maintainers to
integrate across all affected versions (including those in the xorg-
edgers PPA), here's a github pull request for the nvidia-331 branch:
https://github.com/tseliot/nvidia-graphics-drivers/pull/7
debdiff coming shortly.
--
Okay, on vivid, unity-greeter 15.04.2-0ubuntu1 re-introduces this bug.
I have a vivid image that was up-to-date as of Fri 5 Dec. In this
snapshot, with applying any updates, I can connect to protected WiFi
just fine.
However, today something landing from proposed re-introduced this bug,
and I
Er, I mean an ABI mismatched in policykit-1, not network-manager
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1388130
Title:
Cannot connect to WiFi with Nvidia GPU
Another possible hint: some in this set of packages currently in vivid
proposed breaks the WiFi password dialog:
Calculating upgrade... Done
The following NEW packages will be installed:
libisl13
The following packages will be upgraded:
apport apport-gtk btrfs-tools fontconfig
More variables eliminated: this bug does *not* occur on:
- Ubuntu GNOME 14.10
- Ubuntu MATE 14.10
- Kubuntu 14.10
- Xubuntu 14.10 (as mentioned above)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
To eliminate more variables, I just tried xubuntu 14.10 (with nvidia-343
from ppa:system76-dev/stable)... and I can connect to password-protected
WiFi just fine.
As Xubuntu and Ubuntu are using most of the same lower-level stack, this
kinda suggests the problem is fairly high-level, potentially
Still no solution, but I've at least (hopefully) eliminated some more
variables.
As I know this problem doesn't currently exist on Vivid, I tried back-
porting `network-manager` and `network-manager-applet` from Vivid, but
no luck... same problem still exists.
And on the off chance that this is
Hmm, after more careful investigation, I think my hunch about
differences in the DBus related process was a dead end.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1388130
Also tried back-porting `policykit-1` (which needed a back-port of
`glib2.0` and `gobject-introspection`)... still no luck.
But at this point, the delta between Utopic and Vivid is still pretty
small, so I feel this is a promising avenue, at least as far as shot-
gunning goes.
--
You received
This fix seems to be working well. I have test packages here if anyone
wants to test them:
https://launchpad.net/~jderose/+archive/ubuntu/nvidia-test
** Patch added: possible-fix.diff
You'd think it wouldn't be related to the nvidia driver... but it
definitely is.
At System76, we've frequently encountered scattered problems like this.
The nvidia proprietary effects the boot sequence enough (for example, no
kms) that it frequently exposes subtle problems in the overall
Oh, and a little more detail on why I'm certain this is related to the
nvidia proprietary driver...
Part of our QA process after we image a system (before it's shipped to
the customer) is to test WiFi. Since we started shipping Utopic, we've
had 0% failure on systems with Intel graphics.
On
Okay, think I just found a lead in /var/log/upstart/lightdm.log:
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
/etc/modprobe.d is not a file
update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Failed to get D-Bus connection
BTW, it was the Failed to get D-Bus connection bit above that seems
problematic.
Also, looking in syslog, there are some interesting tidbits:
Nov 21 13:17:45 system76-pc NetworkManager[977]: info (wlan0): device state
change: config - need-auth (reason 'none') [50 60 0]
Nov 21 13:17:45
Another update: I think I've ruled out nvidia-persistenced being started
via udev as the possible culprit.
I tried Trusty with the nvidia-343 driver from the System76 PPA (which
starts nvidia-persistenced with udev)... and I can connect to WiFi just
fine.
I also tried an up-to-date Vivid install
Public bug reported:
nvidia-graphics-drivers-331 (331.89-0ubuntu5) will fail to remove/purge
nvidia-331 when /usr/bin/nvidia-persistenced is running.
The reason is the nvidia-331.postrm script hasn't been updated to
reflect that nvidia-persistenced is now started via udev rather than
Upstart
Ah, one thing I had wrong /usr/bin/stop-nvidia-persistenced needs to
be called in nvidia-331.prerm, not nvidia-331.postrm
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu.
disabled
** Affects: system76
Importance: Critical
Assignee: Jason Gerard DeRose (jderose)
Status: Triaged
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug utopic
** Attachment added: Screenshot from 2014-10
Note I confirmed that WiFi works fine when using nouveau on the same
hardware.
Also I tried a minimal a nvidia-331 install with --no-install-
recommends, just in case the problem is related to any of the optimus
stuff, which isn't needed for System76 hardware... and still no dice.
Installing
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234549/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234550/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234543/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234546/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234544/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234556/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234551/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234545/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234547/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234553/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234555/+files/UdevLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234557/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234540/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234554/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234542/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234548/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1366351
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234541/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234552/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234558/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234561/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1366351/+attachment/4234560/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
1 - 100 of 169 matches
Mail list logo
