Mind if I bump this ticket?
FWIW, the fact that this is still there is testament to the inefficacy
of the warning. In my opinion, intrusive but ineffective warnings are a
misfeature that should be fixed in the code.
If you can't make time, would it help if I send a pull request?
--
You
@John, thanks for replying. I just double-checked and I stand corrected.
I can only reproduce with snap itself, not any more with apt. (The rest
of my comment still stands.)
Thanks for looking into this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
These warnings are still happening on the current Disco release.
Please take my remarks (see above) to heart. I'd imagine a "proper fix",
whatever that ends up being, has moderate/low priority, but meanwhile,
this is in my (and other Dutch users') faces multiple times per day. It
prints whatever
Thanks for finding the source of this puzzling message! I noticed John
and Daniel made translation suggestions for both of the offending
messages; what needs to happen to merge them?
Moreover, if you'll allow me an additional comment on this:
I really like that you care so much about UX and copy
Public bug reported:
Trying to unmount a block device I just mounted, I get the following
error (sorry for not resetting the locale. It says Device is busy):
:~$ sudo umount /media/tkluck/tjk-backup
umount2: Apparaat of hulpbron is bezig
umount: /media/tkluck/tjk-backup: apparaat is bezig
I can corfirm that your latest test packages work. You rock, Joseph!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195483
Title:
Installation, Live and Check disc do not start on Asus ZenBook
Hi Joseph,
Thanks for taking the lead on this! I tested your kernel packages, but
unfortunately they didn't solve this for me. The behaviour is slightly
different: instead of booting into a black screen, your packages boot
into a black screen with three white pixels at rather random locations.
This bug was introduced in 657445fe8660100ad174600ebfa61536392b7624
---
Author: Daniel Vetter daniel.vet...@ffwll.ch
Date: Sat May 4 10:09:18 2013 +0200
Revert drm/i915: revert eDP bpp clamping code changes
This reverts commit 57c219633275c7e7413f8bc7be250dc092887458.
It's
My very brief investigation shows that this piece of code has been
applied and reverted a few times already, apparently because some
hardware works with it and other hardware works without it.
I'll install the raring kernel on my own machine and use that for now; I
guess it's up to the ubuntu
** Changed in: linux (Ubuntu Saucy)
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/1195483
Title:
Installation, Live and Check disc do not start on Asus ZenBook
@Christopher: will do.
I'm in the process of bisecting. The problem has been introduced somewhere
between v3.10-rc1 and v3.10-rc2. More precisely, it has been introduced between
v3.10-rc1 and commit fea0f9f. Looking at the logs, the latter is a likely
candidate:
---
Pull drm fixes from Dave
I can confirm this issue. I can get to my desktop by attaching an
external monitor -- it is apparently only the internal display which
doesn't work. This is on a raring - saucy upgrade.
I also tried mainline kernel 3.11.1-031101-generic and it has the same
issue.
I will gladly help getting this
thanks for testing, Joseph! Can you also confirm that autosave works?
You can simulate a crash by hitting Ctrl C in the console.
I'm interested to hear whether the necessary auto save database upgrade
has gone well.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1132720 ***
https://bugs.launchpad.net/bugs/1132720
Public bug reported:
On Ubuntu Raring, the package gtk2-engines-pixbuf fails to upgrade from
version 2.24.14-0ubuntu1 to version 2.24.16-1ubuntu1. The error I'm
getting is the following:
$ LANG=C sudo
My theory is as follows. It appears that the two packages gtk2-engines-
pixbuf:i386 and gtk2-engines-pixbuf:amd64 offer those same documentation
files. Apparently, APT is okay with that as long as those files are
identical, and therefore they can be installed along side eachother. But
during
Public bug reported:
Both the package hadoop and the package libqt4-dev-bin contain an
executable called rcc. Hadoop's one is in /usr/sbin so it takes priority
over qt4's. This breaks compilation of some qt4 programs, like LyX, if
hadoop is installed.
I didn't need Hadoop anymore so I just
The #31 does work for me on a HP tm2 laptop. Anton, perhaps you could
use uname -r and dpkg -s linux-image-3.5.0-16-generic to verify
that you are running the right kernel with package version
3.5.0-16.25~lp1033783v1 ?
--
You received this bug notification because you are a member of Ubuntu
I'm trying Anton's suggestion of installing 3.6 now. I will report back
to confirm whether this solves the issue.
Anton, do you have a source for your statement? That may help people
identify the right changeset and maybe backport it to 3.5.
--
You received this bug notification because you are
I can confirm that installing the 3.6rc5 mainline kernel solves this
issue. I'm marking this bug as affecting the kernel and I'm marking it
invalid for the other packages.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xf86-input-wacom
Status:
Mathieu: How do you feel about the upstream suggestion to drop gnome-
shell/f65826b3ba2cf03a859819e6706046fff376c65c and get native network
messages?
By the way, I've got a patch for nm-applet too (I wrote that earlier).
However, that might also affect the Unity experience, so my guess was
that
Upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=672636.
** Bug watch added: GNOME Bug Tracker #672636
https://bugzilla.gnome.org/show_bug.cgi?id=672636
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch linked: lp:~tkluck/ubuntu/precise/gnome-shell/lp883443
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883443
Title:
GNOME Shell 3.2.0 falsely states: Network Disconnected - you are now
Hi Chase,
This works now. I think it was already fixed in Oneiric. Sorry for not
having closed it earlier. I'm marking it fix released.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
** No longer affects: linux
--
You received this bug notification because you are a
I'm attaching what is probably the required patch. I'm currently setting
up a cross-compile environment to verify. Then I'll make a debdiff.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941617
** Patch added: 03_build_on_armel.patch
https://bugs.launchpad.net/ubuntu/+source/clutter-1.0/+bug/941617/+attachment/2868666/+files/03_build_on_armel.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I didn't manage to create the pbuilder-dist environment because of some
missing public keys. I'll just attach the debdiff and hope that it is a
helpful starting point for someone who knows how arm things work.
Hope this gets fixed. It would be great if gnome-shell 3.4 could make it
into precise.
At least part of this is ubuntu specific. The distribution patch
lp341684_device_sensitive_disconnect_notify.patch
in the package network-manager-applet sets this notification importance
to NOTIFY_URGENCY_CRITICAL. I can confirm that if you change this to
NOTIFY_URGENCY_NORMAL, the notification
Off the top of my head: I think that the changes to utouch-grail and
utouch-frame have been committed to trunk, so they are probably in
precise too. I don't think the patch to xserver-xorg-input-evdev (taking
advantage of it) ever got applied.
--
You received this bug notification because you
I can confirm that the new gnome-shell packages in oneiric-proposed work
and fix this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/918208
Title:
Connection switches in Bluetooth menu are not
** Changed in: appmenu-gtk
Status: New = Confirmed
** Changed in: indicator-appmenu
Status: New = Confirmed
** Changed in: inkscape
Status: Confirmed = Invalid
** Changed in: openshot
Status: Confirmed = Invalid
** Changed in: gitg (Ubuntu)
Status: Confirmed
I've marked this as Invalid for all packages that are not directly
related to the AppMenu.
That is not to say that is is not a confirmed bug and that it shouldn't
be fixed! Thank you, Jonathan, for taking the time to give steps to
reproduce.
But it is clear what the underlying bug is, and it is
It seems like the new gnome-shell package creates a new binary package
gnome-shell-common. It is not in the -proposed repo yet, and I don't see
any mention of it at the oneiric-proposed part of
https://launchpad.net/ubuntu/+source/gnome-shell
(except for Note: Some binary packages for this
** Description changed:
[Impact]
The device connection switches in the gnome-shell bluetooth menu can be
toggled but don't work: their status is independent from the actual connection
status.
[Development Fix]
This is a known bug with a trivial patch, and it has already been fixed in
I think this has to do with the persistency of the notification. My
guess is that the ubuntu network manager (or some other software) sends
the notification with the 'persistent' flag set. In Unity, this doesn't
matter (all notifications are transient), but in gnome-shell, it makes a
difference.
** Description changed:
The device connection switches in the gnome-shell bluetooth menu can be
toggled but don't work: their status is independent from the actual
connection status.
This is a known bug with a trivial patch, and it has already been fixed in
master:
Public bug reported:
The device connection switches in the gnome-shell bluetooth menu can be
toggled but don't work: their status is independent from the actual
connection status.
This is a known bug with a trivial patch, and it has already been fixed in
master:
The package should be okay for Debian now, but it probably won't make it
in time for the sync. I'll make a package for precise, too. Hopefully,
Sebastien can review + upload it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Branch unlinked: lp:~tkluck/ubuntu/oneiric/goocanvas/v2
** Branch linked: lp:~tkluck/ubuntu/precise/goocanvas/v2.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/858954
Title:
[needs-packaging]
* dh_install: usr/lib/python2.7/site-packages/gi/overrides/GooCanvas.py
exists in debian/tmp but is not installed to anywhere
- you need to install this one
This one is only created if you have python-gobject-2-dev installed,
which is deprecated. Do you think I should add a build dependency on
Another question: in addition to libgoocanvas-2.0-9, should there be a
metapackage called libgoocanvas-2.0 that always depends on the current
version? Should this package be made from the same source package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can you explain (or find a link) where the soname number comes from?
In this case, the libtool library version info is equal to 11:0:2.
Where does the 9 come from? Guess: it's 11 - 2, but why?
Relatedly, should I manually rename the binary package (and only the
binary package?) to
What's the standard here? I've already renamed the binary package to
libgoocanvas-2.0{,-common,-dev}. Should the source package just be
goocanvas-2.0 ? (I'm kind of confused by the existence of a
libgoocanvas3 package which just contains version 0.15).
--
You received this bug notification
I can reproduce this bug; see the attached screenshots. The windows are
rendered on top of the dash, and also on top of the alt+tab dialog.
However, you can click through them, and the dash also has keyboard
focus.
For me, I can reproduce this 100% with maximized windows, and most of
the time
** Attachment added: Schermafdruk op 2011-10-19 16:37:39.png
https://bugs.launchpad.net/unity/+bug/831466/+attachment/2560523/+files/Schermafdruk%20op%202011-10-19%2016%3A37%3A39.png
** Changed in: unity
Status: Incomplete = Confirmed
** Changed in: unity (Ubuntu)
Status:
For me, it happens immediately after login with a firefox window. I
don't need any steps to reproduce it (this is obviously unworkable, so
I'm using gnome-shell at the moment).
I've tried to experiment with this a bit more.
* This happens every time at logon. The first window is always above
Found it: this was due to the key `idle-delay` in
org.gnome.desktop.session being set to 1 second. I don't think I set
that myself, but it is not the default value.
Marking this as invalid.
** Changed in: gnome-shell (Ubuntu)
Status: New = Invalid
--
You received this bug notification
Public bug reported:
When I set the notifications to on, the switch stays on for about two
seconds, then goes back off for about two seconds, comes on again, and
so on. This also means that my visible status on Empathy keeps on
switching, which is probably very annoying for the people who have me
** Attachment added: ps-A.txt
https://bugs.launchpad.net/bugs/872186/+attachment/2536162/+files/ps-A.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872186
Title:
notification state continues
** Attachment added: pyparsing-1.5.2-to-1.5.6.debdiff.gz
https://bugs.launchpad.net/ubuntu/+source/pyparsing/+bug/868318/+attachment/2512717/+files/pyparsing-1.5.2-to-1.5.6.debdiff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: pyparsing-1.5.2-to-1.5.6.debdiff
https://bugs.launchpad.net/bugs/868318/+attachment/2512706/+files/pyparsing-1.5.2-to-1.5.6.debdiff
** Patch removed: pyparsing-1.5.2-to-1.5.6.debdiff
Public bug reported:
New upstream version. Debdiff attached. (I am relatively new to
packaging; please check my work carefully)
** Affects: pyparsing (Ubuntu)
Importance: Undecided
Status: New
** Tags: debdiff needs-packaging
--
You received this bug notification because you
Public bug reported:
The new version goocanvas 2.0 hasn't been packaged yet. It can be
installed concurrently with goocanvas-0.15.
I've started a packaging branch. It works on my computer but I'm no
packaging wizard. Please check my work.
** Affects: goocanvas (Ubuntu)
Importance:
I'm marking this as affecting mutter, because it's easy to distro-patch
mutter to ignore the shadow and padding arguments. I'm attaching a
debdiff.
I'm not familiar with all procedures yet, but I'll try to find a sponsor
for this.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Andrea: Thanks for your comments!
1) yes, this was a mistake.
2) the new patch implements what you suggest.
** Patch added: ignore-shadow-and-padding-v2.debdiff
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/800315/+attachment/2437727/+files/ignore-shadow-and-padding-v2.debdiff
** Also affects: xserver-xorg-input-evdev (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Samuel: by 'source directory', I meant the one that contains the files
that you extracted. It is the directory that contains the file named
autogen.sh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am experiencing the bug that Barry Warsaw describes: I cannot login
unless I login to a virtual terminal first (which, possibly relatedly,
mounts my ecryptfs partition).
I could attach additional debugging info. Please let me know if you need
this, and also whether I should open an new bug for
Ngassam Nkwenga: the new version of webkit will be in the upcoming
version 11.10 of Ubuntu. Postler doesn't have this issue on the alpha
version.
I haven't seen any activity on this on the webkit packaging front, so my
guess is that we'll just have to wait for the Oneiric release.
--
You
*** This bug is a duplicate of bug 752674 ***
https://bugs.launchpad.net/bugs/752674
** This bug is no longer a duplicate of bug 708185
all recent items open the same recent image no matter what is selected
** This bug has been marked a duplicate of bug 752674
GtkRecentChooserMenu
*** This bug is a duplicate of bug 752674 ***
https://bugs.launchpad.net/bugs/752674
** This bug has been marked a duplicate of bug 752674
GtkRecentChooserMenu always selects first entry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: appmenu-gtk
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/752674
Title:
GtkRecentChooserMenu always selects first entry
To manage
I have been running Bryce's patched version of Xorg for a while. I still
experience occasional crashes. However, I haven't succeeded in crashing
X by moving my stylus along the screen like a madman (like what I
described earlier).
I found out that I can reliably produce a crash by running the
Bryce: before you spend too much time on it: I cannot immediately
reproduce this last crash in Oneiric. So perhaps you only want to take a
superficial look at it.
I may be able in the near future to switch to Oneiric for 'production';
from that point onwards I'll be able too see if the incidental
Thank you Bryce for finding a possible cause. I'm building your patched
version now. (I couldn't use the ppa because its version doesn't
supersede the version I have installed (2:1.10.2-1ubuntu1.2~utouch1), so
it would cause all drivers to be removed). I will call back here as soon
as I can give
Same problem on HP TouchSmart tm2, with a slightly different lspci:
lspci -vvx:
03:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless
LAN Controller (rev 01)
Subsystem: Hewlett-Packard Company Device 145c
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV-
Turns out I can more or less reliably reproduce a crash by frantically
moving my pen along the tablet for about a minute or two. That allowed
me to attach gdb and get a backtrace (attached).
It seems that I get a different backtrace at different times. For
simplicity, I will assume it is all
Here's Xorg.0.log.old right after a crash. I did install debugging
symbols but I don't see them in the backtrace it contains. Are there any
utouch specific debugging symbol packages I should install?
I could not find the core dump that is mentioned in
https://wiki.ubuntu.com/X/Backtracing. I also
Thanks, I installed the debug symbol packages and will call back here
when I have a backtrace.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764700
Title:
Xorg crashed with SIGABRT in
Hi Chase,
Thanks for taking a look. I still have occasional X crashes ( every 3 -
4 days) with the utouch and utouch-unstable repositories enabled (in
particular, I am using the wacom-dkms module from unstable, and I
uninstalled xserver-xorg-input-wacom). I have no way of telling whether
these
Felix: I think this was default behaviour back then, I didn't do
anything to get it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/737015
Title:
white-listed indicators appear on wrong display
--
Hernán: I haven't managed to do so yet. I wanted to use the launchpad
recipe feature, but it imports the entire webkit source modification
history (~30Gb) so it just takes to much time and bandwidth for me to
properly write and test a recipe. Perhaps someone with more know-how
about daily ppas (ie
** Also affects: webkit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753642
Title:
impossible to write the message body
--
ubuntu-bugs
Chase, sorry for not having had time to provide the files that you
requested. But I can confirm that the issue with the coordinate matrix
has been fixed (by you?) in a recent update (xserver-xorg-input-
evdev=1:2.6.0-1ubuntu12 right now). Thanks!
--
You received this bug notification because
Chase: do you have any guess as to why the touch input would be
normalized differently (I'm guessing [-0.5, 0.5]) than the pen input
([0.0, 1.0]) ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
Wait, I mean [0.0, 0.5] for the touch input.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
multitouch events do not respect swap/invert axes properties
--
ubuntu-bugs mailing list
Chase: thanks for the wiki article, it is very helpful! I have found
that on my devices, the affine coordinate translation is done in
normalized floating point coordinates and not in pixel coordinates. And
the normalization is different for different devices. For example, to
rotate 180 degrees, I
** Also affects: utouch
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
multitouch events do not respect swap/invert axes properties
--
I can reproduce this problem on a fresh daily live-usb with only xournal
and ppa:utouch-team/unstable as extra software. I uninstalled xserver-
xorg-input-wacom to make the evdev driver take over.
I can reproduce it both with my tablet's built-in wacom, and with my
girlfriend's Bamboo PenTouch. I
This trivial patch to xournal is a workaround. The surrounding code (a
function called 'fix_xinput_coordinates') suggests that this bug has
existed (in xinput? gdk?) for some time already. It just manifests
itself slightly differently with these new packages, which makes
Xournal's workaround fail.
** Bug watch added: SourceForge.net Tracker #3244118
http://sourceforge.net/support/tracker.php?aid=3244118
** Also affects: xournal via
http://sourceforge.net/support/tracker.php?aid=3244118
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Public bug reported:
Binary package hint: xserver-xorg-input-evdev
I'm using the (unstable) evdev driver from the utouch ppa
(1:2.6.0-1ubuntu11~utouch2). The bug title says it all: touch and multitouch
events are not translated according to the swap/invert axes properties.
---
Architecture:
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940411/+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/742567
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940412/+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/742567
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940413/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940414/+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/742567
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940415/+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/742567
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940416/+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/742567
Title:
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940417/+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/742567
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940419/+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/742567
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940420/+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/742567
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940418/+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: UdevLog.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940421/+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/742567
Title:
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940422/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940423/+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/742567
Title:
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940424/+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/742567
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940425/+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/742567
Title:
apport information
** Attachment added: locale.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940426/+files/locale.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
apport information
** Attachment added: monitors.xml.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940427/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
apport information
** Attachment added: peripherals.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940428/+files/peripherals.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
apport information
** Attachment added: setxkbmap.txt
https://bugs.launchpad.net/bugs/742567/+attachment/1940429/+files/setxkbmap.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742567
Title:
1 - 100 of 135 matches
Mail list logo
