As a final check, I reinstalled the package again. Now apt is finding it
properly:
$ sudo apt-get reinstall libvirt-dev
[sudo] password for trinitronx:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly
Hmm... yes it seems like universe & multiverse pockets are enabled on
this system for main and focal-security. However, it does have debug
packages enabled for focal-updates via ddebs.list:
$ grep -ri '^deb.*ubuntu\.com' /etc/apt/sources.list* | sort | uniq
The "statoverride" script appears to work on the first run for each
kernel. However, any subsequent times the `dpkg-statoverride` command
exits with errorcode 2:
$ apt-get install something-triggering-dkms
Processing triggers for linux-image-5.4.0-96-generic (5.4.0-96.109) ...
I was able to verify that "Depends: " line for libvirt-dev should work
based on the source package.
Testing a local 'debuild' of libvirt packages seems to work and
produced: libvirt-dev_6.0.0-0ubuntu8.15_amd64.deb
Build + Sign + Install on my local machine provided a workaround for the
missing
Public bug reported:
It looks like libvirt-dev package "Depends:" line needs an update after
the libvirt0 package update from focal-updates:
$ sudo apt-get install libvirt-dev
Reading package lists... Done
Building dependency tree
Reading state information...
It appears the same crash symptoms are still happening on Ubuntu 20.04
with xserver-xorg-video-nouveau package and Nvidia GT240 chipset.
Details in Launchpad bug #1954335 -
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
nouveau/+bug/1954335
Package version:
$ dpkg -l
*** This bug is a duplicate of bug 1217585 ***
https://bugs.launchpad.net/bugs/1217585
** This bug has been marked a duplicate of bug 1217585
System hangs after some time with nouveau and GT240
** Tags added: amd64
** Tags added: focal
--
You received this bug notification because you
*** This bug is a duplicate of bug 1217585 ***
https://bugs.launchpad.net/bugs/1217585
Public bug reported:
Hello,
I'm experiencing frequent crashes that hard-lock the system and kernel
completely.
Symptoms are:
- Frozen screen
- No Keyboard or Mouse input accepted
- Remote SSH times out
> I have updated the Debian package to version 540.1.linux3-1 now which
is used by Fedora, openSUSE and other distributions.
@glaubitz - Excellent! Thanks for your hard work porting this
over!
> Great! This was synced automatically and built in the current Ubuntu
development release,
After testing out the newer version of libmtp v1.1.18, I was able to get
even the current version of Calibre working (as long as I unmounted the
device from Nautilus / GVFS first!)
Here is the initial error if the device is already automounted by GVFS:
Device 0 (VID=1949 and PID=0581) is a
Same issue observed in calibre 4.99.4+dfsg+really4.12.0-1build1
on Focal 20.04 LTS
with Kindle Fire HD 8 plus (10th generation)
Following the guide here seems to help: https://manual.calibre-
ebook.com/faq.html#android-usb
If you miss or can't find the USB notification by swiping down:
- Swipe
** Also affects: calibre (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/1797890
Title:
Enhancement-Kindle fire HD 8
To manage notifications
** Changed in: rhythmbox (Ubuntu)
Status: Triaged => In Progress
** Changed in: rhythmbox (Ubuntu)
Assignee: (unassigned) => James Cuzella (trinitronx)
** Changed in: hundredpapercuts
Assignee: (unassigned) => James Cuzella (trinitronx)
** Changed in: hundred
** Branch linked: lp:~trinitronx/rhythmbox/fix-party-mode-docs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/329389
Title:
"Party mode" ununderstandable and undocumented
To manage notifications
Attaching upstream patch with fixed conflicts & updated date
** Patch added: "Upstream Patch from
https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/59;
I was able to find that this was documented upstream in patch for Gnome
bug #572651
Source: https://bugzilla.gnome.org/show_bug.cgi?id=572651
I've applied the patch, fixed the failing patch hunks and created a
merge request (GitLab's version of pull request) here:
Public bug reported:
drobo-utils package is out of date with upstream.
Ubuntu version: 0.6.1+repack-2
Upstream version: 0.6.2.2
This project needs to be updated to support newer Drobo models with
vendor string "Drobo". Older models have a different string "Data
Robotics". Details can be found
The current package version in Ubuntu 16.04 is: 0.6.1+repack-2
Unfortunately it lacks the support for newer Drobo models with vendor id:
"Drobo". Older Drobo models have vendor string "Data Robotics", which this
version of drobo-utils does not know how to identify still as of 0.6.1+repack-2
@hjd: Thanks for the quick response! As you pointed out, it looks like
the upstream bug report has more info and discussion here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765104
So far, no movement since February 2019 from the maintainer and some
offers of help from others in
Still seems to be an issue in modern Ubuntu 18.04.4 bionic LTS. The
upstream Apple source for HFS+ projects can be found here:
https://opensource.apple.com/source/hfs/
https://opensource.apple.com/source/diskdev_cmds/
Debian package for hfsprogs seems woefully out of date (based on macOS
10.4
PING! Any plans for movement on updating this package?
Is this package mainly imported from upstream (Debian) ?
How can I verify which version of the "diskdev_cmds" project is used on
modern macOS?
Current macOS version 10.15.4 has binary "fsck_hfs" from
"hfs-522.100.5".
As evidenced by:
@fermulator: It looks like it's likely to be
https://en.wikipedia.org/wiki/GDK
$ sudo find /usr/ -iname 'libgdk-3.so*' -exec dpkg -S '{}' \;
libgtk-3-dev:amd64: /usr/lib/x86_64-linux-gnu/libgdk-3.so
libgtk-3-0:amd64: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
libgtk-3-0:amd64:
So due to differing stacktrace here, I think #911591 is likely a
different issue than this one. Different stack library means different
codepath.
@fermulator: Does seem a bit odd at first glance... does gnome-shell
use .NET or C# (gdk-sharp)?
libgdk3.0 is a valid package name in Ubuntu, but
@dino99
Happy to open a new bug report on this, as it still appears to be an
issue in latest Ubuntu 17.10. Usually when reporting bugs, I opt to
prefer adding information to an existing bug report that I have high
confidence describes the problem I am seeing. I believe this helps to
reduce
At first glance, bug may be related to this upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=768204
** Bug watch added: GNOME Bug Tracker #768204
https://bugzilla.gnome.org/show_bug.cgi?id=768204
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've added more details for the crash I am seeing in this bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/911591
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580605
Title:
Adding journalctl logs for gnome-shell crash. After segfault line,
gnome-shell crashes and I'm returned to gdm login screen. Once I login,
everything works again until next crash, usually caused by OpenGL window
resizing or xrandr resolution changes.
** Attachment added: "gnome-shell-crash.log"
Bug seems to be reported also elsewhere:
- ArchLinux: https://bbs.archlinux.org/viewtopic.php?id=231158
- RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1250128
The RHEL bug report mentions that they have Xorg configured without
RandR support. I do see a message in my logs that says gdm
As original reporter stated, it usually appears related to OpenGL window
resize events. I have also noted that xrandr display resolution changes
can trigger the crash.
I see errors in dmesg that mention libmutter:
[15040.472843] gnome-shell[32127]: segfault at 8 ip 7f327f29d5d0 sp
I am seeing gnome-shell crashes also. However, it usually appears
related to OpenGL window resize events as well as xrandr display
resolution changes.
Errors in dmesg mention libmutter:
[15040.472843] gnome-shell[32127]: segfault at 8 ip 7f327f29d5d0 sp
7ffeccf94a38 error 4 in
I can confirm this bug is still happening on:
Ubuntu 17.10 (Artful Aardvark)
gnome-shell 3.26.1-0ubuntu5
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Christian: I've tried as I believe you have asked.
When in the bad case (I comment out the line: DNSMASQ_EXCEPT=lo and then
reboot):
- Running this did not resolve the issue: `sudo resolvconf -a lo.dnsmasq`
- Running this did not resolve the issue: `echo "nameserver 127.0.0.1" |
Maybe interesting things to note:
1. When in bad state:
- The mentioned ENV var change in /etc/default/dnsmasq and `sudo systemctl
restart dnsmasq` immediately resolves the issue
2. When in good state:
- Commenting out the ENV var and running `sudo systemctl restart dnsmasq`
does not
Also seeing this issue in Ubuntu 17.10 (artful) with:
dnsmasq-base 2.78-1
systemd 234-2ubuntu12.1
I can confirm that following https://askubuntu.com/a/968309/ resolves
the issue!
Steps to fix the issue:
Added this line to /etc/default/dnsmasq:
DNSMASQ_EXCEPT=lo
Then restarting
Since the bug-watch-updater updated this... Just want to make it clear
that I was no longer seeing this problem since 16.04. Since then I've
upgraded multiple times, and even swapped the motherboard and a lot of
hardware out. Still no recurrence of the problem for me.
--
You received this bug
** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After trying to build a different kernel module on Ubuntu 17.04 (Zesty),
I can replicate these errors.
The first "error" isn't really an error unless the echo statements are
triggered if the "test" command fails:
test -e include/generated/autoconf.h -a -e include/config/auto.conf
|| (
unity-scope-virtualbox seems not to affect this bug, but was in my list
so I removed it just to be safe. To restore Unity virtualbox search
support, reinstall it:
sudo apt-get -y install unity-scope-virtualbox
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1608208 ***
https://bugs.launchpad.net/bugs/1608208
Duplicate of Bug #1608208. Please remove all old virualbox packages
prior to virtualbox 5 installation. See Bug #1608208 for more detailed
commands to run.
** This bug has been marked a duplicate of bug
*** This bug is a duplicate of bug 1608208 ***
https://bugs.launchpad.net/bugs/1608208
Duplicate of Bug #1608208. Please remove all old virtualbox packages
prior to installation of virtualbox 5. See Bug #1608208 for more
detailed commands to run if you need help.
** This bug has been
Possible duplicate of Bug #1608208. Try removing all old virtualbox
packages prior to installing virtualbox 5. See my comment on Bug
#1608208 for detailed commands to run in order to find all the ones you
have installed.
Hint: Check for "ii" lines in output of: dpkg -l | grep virtualbox
--
*** This bug is a duplicate of bug 1608208 ***
https://bugs.launchpad.net/bugs/1608208
It appears that you've solved your problem. Great job! Looks like this
is a duplicate of Bug #1608208. Fix I found was to uninstall & purge
all old virtualbox packages prior to installing the new
*** This bug is a duplicate of bug 1608208 ***
https://bugs.launchpad.net/bugs/1608208
Duplicate of Bug #1608208. Remove and purge all old virtualbox
packages. See Bug #1608208 for detailed instructions and commands to
run.
** This bug has been marked a duplicate of bug 1608208
package
*** This bug is a duplicate of bug 1608208 ***
https://bugs.launchpad.net/bugs/1608208
Duplicate of Bug #1608208. Remove all old virtualbox packages before
installing the new one. See Bug #1608208 for detailed instructions &
commands to run.
** This bug has been marked a duplicate of bug
Got same issue when upgrading to virtualbox 5 on Ubuntu 16.04.
Fix was to uninstall & purge all old virtualbox packages:
# Find your installed old packages with:
sudo dpkg -l | grep virtualbox
# Uninstall all packages listed:
sudo apt-get purge virtualbox-qt virtualbox
*** This bug is a duplicate of bug 1200950 ***
https://bugs.launchpad.net/bugs/1200950
I'm seeing this too upon upgrade to 16.04.3 LTS with Unity. This
appears to have been reported many times and marked as duplicate of
#1200950 by the Apport Launchpad bot.
I'm marking this one also as dupe
On my Raspberry Pi OpenELEC device, I see that they have cec-client
working. However, it's not cec-client 4.0.1, but an older 3.0.1:
# cec-client -i
libCEC version: 3.0.1, git revision: f3d0ca2
, compiled on Sun May 1 12:14:09 UTC 2016 by step...@buildserver.openelec.tv
on Linux
For what it's worth, trying the above posted command `cec-client -s` did
not work for me on an x86_64 Intel i7 machine either.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:
Not sure if it fits the description and errors originally in this bug.
However, I do see some issues on the plugins tab with mythbuntu-control-
centre 0.64.1 on recently upgraded Ubuntu 16.04 machine. I can
reproduce it by clicking on the "Enable/Disable All MythTV Plugins"
CheckButton.
The
I am able to reproduce issue when using:
VNC Server: Ubuntu trusty 14.04.3 LTS running x11vnc 0.9.13-1.1
$ x11vnc -version
x11vnc: 0.9.13 lastmod: 2011-08-10
VNC Clients:
- Mac OS X 10.9.5 running Screen Sharing app Version 1.5 (481.1)
- Mac OS X 10.10.5 running Screen Sharing app
Above reproduction was tested using Unity package:
unity 7.2.0+14.04.20140416-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219525
Title:
Cannot unhide (show hidden) launcher over
Apologies for not responding sooner (I get waaay too many emails and
have filtered automated mailings like the ones sent by launchpad to
Gmail labels which generally never get looked at).
After upgrading to the next LTS release (12.04) I believe I stopped
seeing this bug. Upgraded since to
Verified it still is a problem in: Ubuntu 14.04.1 LTS (Trusty)
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902134
Title:
k3b: Device in use - It is urged to terminate the
Complaints show fear, anger ungratefulness while calm feature requests
show peace, gratefulness understanding of a problem.
Community giving of FOSS shows kindness compassion, while taking
complaining shows an unsatisfied desire for control.
True control lies in harmonising with the
On this same motherboard (Gigabyte GA-MA74GMT-S2), I had success getting
the front panel input to work by adding the following line to
/etc/pulse/default.pa
load-module module-alsa-source device=hw:0,0
I added this just before the udev auto-detect module:
### Automatically load driver modules
Still seeing this in Ubuntu 13.10 Saucy Salamander with mythbuntu-
control-centre package version: 0.63-0ubuntu2
I can verify that the patch attached to this issue works and the
mythbuntu-control-centre app opens after I've applied it!
Thanks @Sebastian ;-)
--
You received this bug
Ran baobab today and found that gwibber was using about 30GB of space in
my home dir!
~$ ls -sh ~/.local/share/desktop-couch/.gwibber_messages_design/
total 26G
13M 0526a2ae236cc99c2b84d33f1be6cea1.view 2.7G
2f3267703246f5e02533e59714915b7d.view 24G
8873a749eadc0dee755b5fdfdc59c0a1.view
Ran across this dependency when installing e4rat. I've created a .deb
metapackage for ubuntu-minimal without the ureadahead dependency here:
https://launchpad.net/~trinitronx/+archive/minimal-no-ureadahead/
DISCLAIMER: I do not guarantee that you won't run into any problems, so if in
doubt
Confirmed still in network-manager-vpnc 0.9.4.0-0ubuntu1 on Ubuntu
12.04.1 LTS (Precise Pangolin).
Would be really nice if connect automatically checkbox would actually
work! I think it's about time someone who knows about this piece, and
where to look in order to fix it took it into
*** This bug is a duplicate of bug 989653 ***
https://bugs.launchpad.net/bugs/989653
Public bug reported:
Was able to fix this. For more details see:
http://askubuntu.com/q/126322/19264
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libatk-adaptor-schemas 2.4.0-1ubuntu2
*** This bug is a duplicate of bug 989653 ***
https://bugs.launchpad.net/bugs/989653
** This bug has been marked a duplicate of bug 989653
package libatk-adaptor-schemas 2.4.0-1ubuntu2 failed to install/upgrade:
trying to overwrite
Thanks for fixing this!!! ^_^
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/856205
Title:
run the wrong command if enter is hit before the view is refreshed
To manage notifications about this bug
Trebacz (from Comment #25),
I was able to simply uninstall and re-install the package, and it seems
to work fine now. I pressed Ctrl+Alt+F1 when I got the blank screen
after a reboot, logged in, and did this:
sudo apt-get remove nvidia-current
sudo apt-get install nvidia-current
--
You
Update: I found that the root cause of my X11 not starting was due to
my nvidia-current package being in a bad state during the upgrade. The
video drivers were not installed for the new kernel, which was causing
the second issue.
After manually doing the move symlink of /var/run and
I'm seeing this on a Thinkpad T410 that has been dist-upgraded to
Oneric. It started out running a freshly installed Maverick, which I
have upgraded up to Oneric now.
The system failed to boot after dist-upgrade with dbus error messages
like in Bug #811441
I do not have any weird cifs or nfs
FYI: I had previously upgraded from Maverick - Natty
I experienced the issue when upgrading from Natty - Oneric
I manually did the following:
sudo mv /var/run/* /run/
sudo mv /var/lock/* /run/lock/
sudo rmdir /var/run
sudo rmdir /var/lock
sudo ln -s /run /var/run
sudo ln -s /run/lock /var/lock
I'm getting a similar error:
sudo apt-get purge adobe-pgrep-status: /var/lib/dpkg/status:44726:
expected a colon
Here is a snippet of this file with the line numbers included:
http://pastebin.com/YkSpHjah
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I am seeing this bug for 'various artists' albums being that are not
marked as compilations sorted incorrectly.
I have *tons* of these in my library. Is there an easy way to auto-
detect them and set them having Compilation Album Artist set to 'VA' ?
--
You received this bug notification
I stumbled upon this bug when using a color PS4 prompt to trace bash
scripts. Usually it would display fine, but I noticed some strange
behavior once the shell level increased enough.
Bash repeats the first character of the PS4 prompt to indicate the shell
level for scripts that call other
Disregard my last question. I found this output in my build log:
checking for standard-conformant vsnprintf... yes
It appears that I must have not added my patch to the debian/patches
folder the correct way. I didn't see that the patch was applied during
the build log, and it was not listed in
I am seeing this In Ubuntu using the Gnome desktop as well. The konsole
window gets into a state where it appears that it has focus, but does
not respond to keyboard input, and has a 'hollow cursor'. The way I ran
into it was by using multiple konsole windows on different desktops and
switching
Which packages from the ppa are necessary for testing out the fix for
this?
I'm seeing this issue on a Thinkpad T410 with this hardware
$ lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 06)
01:00.1 Audio device: nVidia
Confirmed on a Thinkpad T410 using the nvidia proprietary drivers
throught synaptic. Wallpaper looks similar to screenshot upon login
$ lspci | grep -i nvidia
01:00.0 VGA compatible controller: nVidia Corporation GT218 [NVS 3100M] (rev a2)
01:00.1 Audio device: nVidia Corporation High
Public bug reported:
Sometimes, I am affected by bug 808962 where unity always stays on top
of my windows. This is very annoying. In an attempt to workaround
this, I opened ccsm and disabled re-enabled Unity (unchecked and then
rechecked the compiz plugin).
After doing this, I end up with a
** Attachment added: Screenshot of the problem
https://bugs.launchpad.net/bugs/816527/+attachment/2234429/+files/Unity-purple-redraw-issue.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816527
apport information
** Tags added: apport-collected compiz-0.9 natty needs-reassignment
possible-manual-nvidia-install regression-update running-unity ubuntu
** Description changed:
Sometimes, I am affected by bug 808962 where unity always stays on top
of my windows. This is very annoying.
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234433/+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/816527
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234434/+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/816527
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234435/+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/816527
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234436/+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/816527
apport information
** Attachment added: GlConf.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234437/+files/GlConf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816527
Title:
Unity
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234438/+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/816527
Title:
Unity
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234439/+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/816527
Title:
Unity
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234440/+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/816527
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234441/+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: ProcModules.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234442/+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/816527
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234443/+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/816527
Title:
Unity
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/816527/+attachment/223/+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/816527
Title:
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234445/+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: XorgConf.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234446/+files/XorgConf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/816527
Title:
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234447/+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/816527
Title:
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234448/+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/816527
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234449/+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/816527
Title:
Unity
apport information
** Attachment added: monitors.xml.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234450/+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/816527
apport information
** Attachment added: nvidia-installer.log.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234451/+files/nvidia-installer.log.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: nvidia-settings.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234452/+files/nvidia-settings.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: peripherals.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234453/+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/816527
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234454/+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/816527
Title:
apport information
** Attachment added: xinput.txt
https://bugs.launchpad.net/bugs/816527/+attachment/2234455/+files/xinput.txt
** Changed in: unity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Tags added: apport-collected running-unity
** Description changed:
I originally reported this in Bug 285392. However, I'm not sure that
this is the same bug, or a different one with the same symptom.
I am seeing this problem on a Gigabyte GA-MA74GM-S2
1 - 100 of 144 matches
Mail list logo
