This also impacts me. Screen becomes garbled quicker if Firefox is
running. Screen takes a bit longer to become garbled if only Thunderbird
is running.
I tried Cory's fix above, and it hasn't garbled the screen in about 45
minutes minutes with Firefox, Thunderbird, and other graphical apps
** Project changed: software-center => cute-software-center
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/1097946
Title:
software-center crashed with TransactionFailed in
Public bug reported:
On upstart init system work fine.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lightdm 1.16.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic i686
ApportVersion: 2.19.1-0ubuntu4
Architecture: i386
CurrentDesktop:
Just to say, reformated reinstalled and its working fine with dual
graphics, thanks :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX incompatible with
Modifying /usr/share/X11/xkb/symbols/pc has the side effect that SDL is
unable to recognize the keyboard layout, and most keys do not work in
SDL applications if a modified keymap is used.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Dear Reporter,
Thank you for taking the time to report this bug and helping to make openSUSE
better.
We are sorry that we do not always have the capacity to look at all reported
bugs in a timely manner. There have been many changes in openSUSE since the
time you reported the bug and your
Phil Boutros, is there a file is /var/crash after the crash occurs?
** Tags removed: bios-outdated-a18
** Tags added: latest-bios-a18
** Changed in: xorg (Ubuntu)
Importance: Low => Medium
** Changed in: xorg (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
** Changed in: gnome-panel (openSUSE)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1006490
Title:
Gnome Classic 12.04 panel applet
*** Bug 92739 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001
This one seems to be solved in Wily.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1479054
Title:
Shuffle and repeat buttons pressed state does not visually differ from
Same on KDE, so this is DE-independent.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1509139
Title:
Shows "Chromium isn't your default browser" since 15.10.
Status in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
Public bug reported:
The "Brightness & Lock" dialog reports that my screen should turn off
when inactive for 5 minutes, and it should require my password to
unlock, but this never happens. On a fresh install of 14.04, I've left
it idle for over an hour and the desktop remains visible and
Should be fixed since Vivid (libmtp 1.1.8-1ubuntu2)
http://sourceforge.net/p/libmtp/bugs/864/
** Changed in: libmtp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
According to this thread:
http://askubuntu.com/questions/459840/lock-screen-not-working-14-04
this problem is likely due to a bug in gnome-screensaver, in that the
14.04 package does not configure it to run at startup.
--
You received this bug notification because you are a member of Desktop
That Optiplex is actually my work machine. However, I have also
observed this on my laptop, a Dell Latitude E7450 with an Intel video
card that also uses the i915 driver. I re-enabled animations in compiz,
and it just crashed. I do see a crash file there, which I will attach
here.
**
(In reply to Adrian Johnson from comment #91)
> What is the output of "pkg-config --cflags nss"?
[user@dev-21 poppler]$ pkg-config --cflags nss
-I/usr/include/nss3 -I/usr/include/nspr4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1503418
Title:
[SRU] [REGRESSION] launching byobu from unity uses
Public bug reported:
Required info:
1) Ubuntu 15.10
2) GNOME Terminal 3.16.2
3) Start instances of gnome-terminal with customized window title and icon
which are not grouped with default gnome-terminal instances
4) All instances gnome-terminal are grouped under the same icon, regardless of
what
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509973/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509975/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509978/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509976/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509977/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509974/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Seconded rmuncrief-9's comments.
Compiled Catalyst 14.502 for Firepro W5000 from AMD. Worked flawlessly until
dist-upgrade tried to install fglrx-dev for 15.1 (I think). Only workaround
I've found is to hold packages:
sudo apt-mark hold fglrx-dev fglrx-core fglrx fglrx-amdcccle
I didn't have
Public bug reported:
Using the PPD from
http://www.kyoceradocumentsolutions.de/dlc/de/driver/all/linux_ppd_s_ksl_8
.-downloadcenteritem-Single-
License.downloadcenteritem.html?langLabel=de_de=/content/sites/kme/de/de/index/serviceworld/downloadcenter
(the German one, not sure if that could make a
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509963/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509966/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509967/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509961/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509969/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1511512
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509971/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509972/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509964/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509965/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509962/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "MonitorsUser.xml.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509970/+files/MonitorsUser.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509968/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1511512
apport information
** Tags added: apport-collected
** Description changed:
Xorg crashes when opening new windows.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
Hm. Some more testing revealed an odd difference between the USB ports
on the left and on the back side of my docking station.
The back ports work as one would expect: printer is recognized and gets
registered when plugged in, and gets unregistered when unplugged; USB drive
when plugged in gets
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509980/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Ran apport-collect -p xorg 1511512 on my laptop because I have more
access to it and it exhibits the same problem (and it is running much
newer hardware and BIOS).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
*** Bug 92739 has been marked as a duplicate of this bug. ***
--
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/1140716
Title:
[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509981/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509960/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1511512/+attachment/4509979/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Workaround, tested on 14.04: Meta + W to show all windows and pick the
Mumble window.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1326903
Title:
remmina and mumble windows get lost
Public bug reported:
Every few days a dialog pops up saying "Authentication is required to change
your own user data" with an entry field for a password. If I type my user's
password the dialog will reappear with an empty entry field. If I click on the
cross to close the window many times it
(In reply to Adrian Johnson from comment #79)
> + r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
> + r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
> + r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
>
> According the PDF Reference, the ByteRange array contains
(In reply to Markus Kilås from comment #93)
> Created attachment 119174 [details]
> Handle SEC_ERROR_UNTRUSTED_ISSUER
I pushed this and also some code to differentiate between an unknown and
an untrusted issuer (no idea what's the difference but if nss has this
difference i feel we also have to)
Created attachment 119283
Manpage improvement
Here's an improvement to the manpage.
Corrected a typo and added some missing context
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
Created attachment 119174
Handle SEC_ERROR_UNTRUSTED_ISSUER
When verifying a PDF signed by a certificate issued by a CA not in the
trust store I would expect to get an error "Certificate isn't Trusted"
however currently the error message actually is the more generic
"Unknown issue with
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement
Pushed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085526
(In reply to Adrian Johnson from comment #91)
> What is the output of "pkg-config --cflags nss"?
[user@dev-21 poppler]$ pkg-config --cflags nss
-I/usr/include/nss3 -I/usr/include/nspr4
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.
I'm still waiting for an answer to comment 79.
--
You received this bug notification because you are a member of
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1:
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all
Created attachment 119174
Handle SEC_ERROR_UNTRUSTED_ISSUER
When verifying a PDF signed by a certificate issued by a CA not in the
trust store I would expect to get an error "Certificate isn't Trusted"
however currently the error message actually is the more generic
"Unknown issue with
(In reply to Adrian Johnson from comment #94)
> I suggest we change the pdfsig "-c" switch to "-nocert". We can easily add a
> single character option if we find it is needed. But we can't get rid of it
> if we later regret it.
>
> I'm still waiting for an answer to comment 79.
As said please
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.
I'm still waiting for an answer to comment 79.
--
You received this bug notification because you are a member of
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.
Done. I've also added a man page. If any further information
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement
Pushed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1:
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all
(In reply to Adrian Johnson from comment #79)
> + r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
> + r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
> + r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
>
> According the PDF Reference, the ByteRange array contains
(In reply to Markus Kilås from comment #93)
> Created attachment 119174 [details]
> Handle SEC_ERROR_UNTRUSTED_ISSUER
I pushed this and also some code to differentiate between an unknown and
an untrusted issuer (no idea what's the difference but if nss has this
difference i feel we also have to)
Public bug reported:
Steps to reproduce:
1. open `nautilus` and create a new empty file `d` in your `$HOME` directory
with the `nautilus` context menu and move it to trash
2. right click on the trash icon in the `unity` launcher and click on `Empty
trash`
A new unnecessary `nautilus`
Public bug reported:
Search engine of Google not working
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 41.0.2+build2-0ubuntu0.14.04.1
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic i686
AddonCompatCheckDisabled: False
Public bug reported:
I cannot update or install any program. I have a perl error that i
cannot resolve.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: flashplugin-installer (not installed)
ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
Uname: Linux
Sorry, I have to specify that I haven't non-western characters in my
fstav entries ...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1428417
Title:
Nautilus(and Nemo too) cannot
The bug is still present after upgrading to Kubuntu 15.10.
Same workaround as before to access to the network after booting:
sudo /etc/init.d/network-manager restart
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
Public bug reported:
After switch to xserver-xorg-video-ati (I has to install it by hand -
not seeing that additional drivers gui reported switching to it.) and
after reboot system fall into fallback mode. Logs and hw info below
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package:
Public bug reported:
After upgrading from Ubuntu 14 to 15.10 the touchpad no longer works. To
get it to work, I must manually reload the mouse drivers through
terminal. However, this only works for the current session.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
** Changed in: xorg (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1504816
Title:
Random freezes
Status in xorg package in Ubuntu:
Public bug reported:
At the moment, the latest version of gnome-mahjongg [1] and shotwell [2]
fails to build from source on Xenial since one of the dependencies,
valac, is in Universe [3].
I don't know exactly how these decisions are made, but maybe vala needs
to be added to Main?
[1]
Installation of brasero-cdrkit does not resolve the problem in Ubuntu
Gnome 15.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/783918
Title:
Brasero ejects CD before burning audio
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1511972/+attachment/4509872/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in
The all 3 files - kern.log, Xorg.0.log and Xorg.failsafe.log - are from
system running ati driver. Auto attached files were filed from system
running fglrx.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in
** Attachment added: "Xorg.failsafe.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1511972/+attachment/4509873/+files/Xorg.failsafe.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
You partially right, aldebx. Compiz is essential for crash. But Unity is
not. Under Metacity I found no crashes today.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1511819
Title:
Xorg
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1511972/+attachment/4509871/+files/kern.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Misterx (pivotz1)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1511054
Title:
normal mode boot hangs up... edid error +
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.
Done. I've also added a man page. If any further information
(In reply to Adrian Johnson from comment #94)
> I suggest we change the pdfsig "-c" switch to "-nocert". We can easily add a
> single character option if we find it is needed. But we can't get rid of it
> if we later regret it.
>
> I'm still waiting for an answer to comment 79.
As said please
Created attachment 119283
Manpage improvement
Here's an improvement to the manpage.
Corrected a typo and added some missing context
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
I deleted /var/log/syslog, plugged in the drive (Transcend), it mounted
and nautilus opened, then selected the "safely remove" menu item on its
icon in the ribbon, icon vanished etc, than few seconds later it
reappeared and nautilus opened again.
There was nothing written to the /var/log/syslog
Thank you for your help Christopher.
I updated my BIOS and the output of the command you asked me to execute
is:
N10ET38W (1.17 )
08/20/2015
I'm still having the same issue. Can I provide you with some logs or
something else to help address this issue?
Please note that I dist-ugpraded to Wily.
I've exactly the same bug in my Ubuntu 15.10. It seems related to
mount/umount commands, since mount mounts fstab entries marked as
"user", while umount cannot unmount the same entries.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Sorry, I can't generate a backtrace, same problem as Dirk: after
executing "continue" in gdb my entire system freezes, so I can't get
back to the X session.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Chromium with Native Client is now working for Trusty and newer on both
the Chromium Beta and Dev PPAs.
https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-beta
https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev
Also, there is a duplicate of this bug: bug #882942. Should
The following worked for me:
1. Install xserver-xorg-video-intel package and rebooting.
This showed output on the second monitor in lower resolution.
2. Adding higher resolution via xrandr:
sudo xrandr --addmode DP1 1920x1080
3. Using the Ubuntu settings, display module to switch to higher
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Pietari Heino, could you please test the latest upstream kernel
available from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are
For the USB issues of te different USB ports of your docking station
behaving differently, open a bug on the Linux kernel (Ubuntu package
"linux").
Your printing problem can be a bug in the printer's PostScript
interpreter, so please follow the instructions of section "PostScript
(PDF) printer
Phil Boutros, thank you for reporting this and helping make Ubuntu
better. However, your crash report is manually attached.
Please follow these instructions to have apport report a new bug about your
crash that can be dealt with by the automatic retracer. First, execute at a
terminal:
cd
I agree with Dan Smith's proposal.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1297790
Title:
"Unknown audio device" dialog pops up every time I plug in headphones
I also verified that downgrading to libsane 1.0.24-4ubuntu1 from
1.0.25+git201505 allows me to scan again, so I definitely there's some
sort of sane-pixma regression in there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends
Public bug reported:
Up until recently, I've been able to scan fine with my Canon Pixma
MX7600. Then I upgraded to Ubuntu Wily and I've started getting:
$ scanimage
scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument
The device pings and I can get to its HTTP port.
According to one of the authors of the sane-pixma backend:
"this looks similar to an issue that I fixed some time ago. Please see
if you can find a package of the released 1.0.25. that should fix your
issue"
See http://lists.alioth.debian.org/pipermail/sane-
devel/2015-October/034084.html
--
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
1 - 100 of 111 matches
Mail list logo
