The reversion of nautilus for 16.04 back to 3.14 resolves this bug
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
For 16.04 this will no longer be an issue with reversion to 3.14
** Changed in: nautilus (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
Not speaking for seb128 but it's not as simple as that 'change' by
itself. It would have lead to new issues, ect.
Anyway for the moment a moot point for 16.04, as far as the future this
is better addressed upstream.
On 02/05/2016 01:07 AM, Khurshid Alam wrote:
>
I now why this 'seems' fixed, now if an external mouse is removed while the
touchpad is disabled the touchpad stays disabled.
(at least in 16.04
May have misunderstood the previous behaviour that when an external mouse was
removed with touchpad being disabled the touchpad was immediately
** Changed in: unity-settings-daemon (Ubuntu)
Status: Fix Committed => Confirmed
--
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/1283863
Title:
disabling touchpad
Public bug reported:
The past & current in 14.04 behaviour was to always re-enable the touchpad
immediately if disabled upon removing an external mouse
(- either explicitly or having the mouse break or batteries go bad, ect.
Now the touchpad stays disabled, both in current session & after a
** Tags added: any-hope xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1260128
Title:
Nvidia-prime produces unbearable visual stutter
Status in
Public bug reported:
Also affects cdplayer (goobox).
Is not seen in audacious or vlc at all (using default audio of pulse
Test case: insert audio cd, play in rhymbox or cdplayer
What happens: significant background buzzing
May be gstreamer issue?
Attached is simple recording of what Rb is
Results of some suggested gst commands -
gst-launch-1.0 cdparanoiasrc mode=1 ! audioconvert ! audioresample ! alsasink
# bad
gst-launch-1.0 cdparanoiasrc mode=1 ! audioconvert ! audioresample ! pulsesink
# bad
gst-launch-1.0 cdiocddasrc mode=1 ! audioconvert ! audioresample ! pulsesink
#
Seems so, I had attached an audio recording to the orig. report, look
above, sounds similar
On 01/29/2016 01:10 PM, flocculant wrote:
> Is it like this? https://sendvid.com/sa7b0i4n
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Clementine's issue here is it uses wrong sample rate
--
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/1539700
Title:
Audio cd's play with background buzzing
Status in alsa-driver
** Tags added: xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1502652
Title:
File-roller does not fully display or extract some archives
Status in file-roller package in
Not to dissuade you but -
15.04 is just about EOL, 15.10 to follow this early summer so if
affected they don't really matter anyway.
This is not an issue in 16.04 as evince opens to a populated recent
documents screen
So that leaves 14.04 where this is a current issue however a fix could
Sorry Brian, meant to check back & mark invalid as the issue seemed to resolve
itself with a new install several days later.
(- no, it was a straightup install from a daily image, no ppa's of any sort..
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this
Public bug reported:
If renaming a file that's located close to an open window the nautilus dialog
box opens under that window
screen attached
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux
Sorry to report that see same crash with the patch
Tried with both ubuntu & gnome sessions. (shouldn't matter & didn't but
recent mesa issue makes me test both just in case.
On 01/14/2016 01:19 PM, Robert Hooker wrote:
> Chris Wilson from Intel has passed along a patch that may fix it and
> asked
Marking this as invalid as it was upstream intent & in the case of
sidebar dnd hover > open dir. really doesn't matter whether it was
enabled or now been removed.
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a
Public bug reported:
It's what's best for most users & it seems that was the intent also upstream
when they created the gsetting
See here -
https://git.gnome.org/browse/nautilus/commit/?id=2338a9239496b8204d302388649c2b45a57c38e9
In current nautilus source for ubuntu -
true
Just to note concerning this - ctrl+h now shows hidden files & sets
global option to show hidden files to enabled
--
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/1527867
Title:
no
If backporting then without any real code changes setting the default to true
would make available.
(- it could be that some users would prefer not to have the option available so
keeping the gsettings is useful.
A gschema.override could be used but seems not a good way, exposing the option
Personally, no, either delete to trash or the keybinding is fine.
I guess the most valid complaint upstream was for users of apple
hardware stating they have no delete key.
I take it then that 16.04 will use nautilus 3.18 & not go to 3.20?
On 01/08/2016 10:37 AM, Sebastien Bacher wrote:
> is
Public bug reported:
Instead the user is prompted to go to the unity (ubuntu) bug page & manually
open a new report.
This is obviously not as useful as no info about reporting machine or env is
added.
Test case:
in terminal ubuntu-bug unity
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Public bug reported:
But only when using the copy to... option on files from another partition,
locally there is no issue.
The nauutilus window just goes gray & no other nautilus windows can be opened
or accessed if already open.
The nautilus process is still running, no crash.
Test case
Fixed in totem-pl-parser-3.10.6
** Changed in: totem-pl-parser (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem-pl-parser in Ubuntu.
https://bugs.launchpad.net/bugs/1520379
Title:
** Changed in: xorg-server (Ubuntu)
Status: Invalid => New
--
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/1528667
Title:
Xorg crashed with SIGABRT in
Upstream bug concerning missing context menu delete option
https://bugzilla.gnome.org/show_bug.cgi?id=757375
Has been returned in nautilus-3.20 as seen here, is now a dconf option, default
of false -
https://git.gnome.org/browse/nautilus/commit/?id=0e5f6710df593de3455fe0e8b1509cdf2fb55bbe
The
Some file names are displayed oddly, ex.
.
thunderbird
.
launchpadli
b
On Dec 8, 2015 2:50 AM, "Sebastien Bacher" wrote:
> @Doug, what issue do you want to show with your screenshot? the
> icons/padding/labels don't look buggy in an obvious way to me
>
> --
> You received
May not be as simple as changing size values as the padding is currently
screwed up as is. Could make that worse or solve, one would have to try..
screen shows current using small, some folders have names broken up, ex.
.thunderbird, .macromedia, ect.
** Attachment added: "Screenshot from
At the very least set the default to 'small' as that setting is still a
bit larger than the previous one of 100%
--
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/1523015
Title:
Icons
Public bug reported:
nautilus is using that unfortunate csd/GtkHeaderBar but none of the context
menu pop ups do. They remain on unity window deco
(where nautilus belongs..
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.2-1ubuntu2
ProcVersionSignature: Ubuntu
Public bug reported:
Same as gedit except now the default file manager
nautilus should provide a means to disable csd/GtkHeaderBar if 3.18 is to be in
16.04
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Public bug reported:
It currently doesn't look correct in an ubuntu session. It's one thing
for an app here or there to use csd/GtkHeaderBar & be different than the
bulk of apps but not the file manager.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.2-1ubuntu2
Public bug reported:
Obvious
(The file manager should fit the theme & other windows, csd has no relevant
place in Ubuntu/Lights themes/Unity7/compz
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname:
Could be a limitation of the narrowness of the default "Type" in
nautilus. They have the possibility for a detailed type, just not
enabled though can easily be done with small non-invasive patch. Screen
shows the diff between the 2
** Attachment added: "Screenshot from 2015-11-29 20-28-41.png"
Public bug reported:
Since 3.10 this has been broken, totem will report, "m3u-files will not start
any more; error "The given film cannot be found"
Fixed upstream in git, could be applicable to 3.10 if 16.04 doesn't move up.
(will test patch
https://bugzilla.gnome.org/show_bug.cgi?id=758710
The upstream commit to fix works fine, 1 word change in 2 lines. -
--- totem-pl-parser-3.10.5.orig/plparse/totem-pl-parser-lines.c
+++ totem-pl-parser-3.10.5/plparse/totem-pl-parser-lines.c
@@ -502,7 +502,7 @@ totem_pl_parser_add_m3u (TotemPlParser *
/* + 2, skip drive
Maybe some progress
http://lists.freedesktop.org/archives/dri-devel/2015-October/093691.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1260128
Title:
Nvidia-prime produces
Public bug reported:
Test case:
View > Side panel
The close, min, & max buttons are replaced by the side panel instead of being
moved to the right with the rest of whatever gnome calls that topbar.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.2-1ubuntu2
ProcVersionSignature:
Public bug reported:
As described.
The option is global & gedit can't be excluded nor show it's menus if the
option is enabled
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit 3.18.2-1ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
Public bug reported:
Seems to be from recent gtk3 upgrades which have affected sidebar in several
ways.
Test case:
Open nautilus to any directory
Grab a file with cursor, bring over to sidebar & hover over a directory such as
Documents
What happens: nothing
What should happen: the main
Public bug reported:
In a ubuntu session open gedit, maximize.
I guess because it doesn't use window deco (unity) when maximized you get 2
sets of action buttons, one from gedit in toolbar, one from light-themes in
unity panel
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit
Public bug reported:
Did not happen with initial upgrade to gedit-3.18 but showed up with some
subsequent updates of other packages.
(may be able to track down by manually parsing synaptic's history logs
Please see attached screenshot
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gedit
** Tags added: xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in non gnome sessions when using nvidia drivers via
Doesn't happen with modesetting so currently not an issue
** Summary changed:
- Switch from nvidia to intel via a log out/in fails
+ Switch from nvidia to intel via a log out/in fails with SNA
--
You received this bug notification because you are a member of Desktop
Packages, which is
Well then hopefully you can get it so this change to modesetting can be
reverted & one isn't forced to get screen to sleep then awake.
My whole point was that this report is claiming that the switch from Intel to
Nvidia fails which is not true is any respect.
It's purely a matter of no visible
** Summary changed:
- No visible display in ubuntu session when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
+ No visible display in non gnome sessions when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
--
You received this
Not really fixed so opening again
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Fix Released => Confirmed
** Changed in: lightdm (Ubuntu)
Status: Invalid => Confirmed
** Changed in: xorg-server (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug
A "regression in the intel driver" doesn't seem to explain why this was not an
issue in a gnome session, nor to the fact that -
xset dpms force off
xset dpms force on
returned display both in greeter & session
(and nvidia driver loaded & worked fine, with or without a visible display.
you
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Triaged => Invalid
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Invalid
** Changed in: unity-greeter (Ubuntu)
Status:
*** This bug is a duplicate of bug 1501041 ***
https://bugs.launchpad.net/bugs/1501041
** This bug has been marked a duplicate of bug 1501041
No visible display in ubuntu session when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
--
You received this
Public bug reported:
However switching from intel to nvidia works ok thru a log out/in. A restart is
needed when going from nvidia to intel.
This is basically what is shown on the screen when attempting a n intel to
nvidia via a log out
Oct 19 09:11:12 doug-Lenovo-IdeaPad-Y510P kernel: [
*** This bug is a duplicate of bug 1501041 ***
https://bugs.launchpad.net/bugs/1501041
** This bug has been marked a duplicate of bug 1501041
No visible display in ubuntu session when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
--
You received this
** Tags added: lubuntu xubuntu
** Tags removed: amd64
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu session when using nvidia drivers
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-greeter in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in ubuntu
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
No visible display in
Seems to have been resolved by recent gstreamer updates
** Changed in: totem (Ubuntu)
Status: Confirmed => Fix Released
--
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/1490090
previous and useful view from file-roller (archive manager
** Attachment added: "Screenshot from 2015-10-04 12:00:40.png"
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1502652/+attachment/4484004/+files/Screenshot%20from%202015-10-04%2012%3A00%3A40.png
--
You received this bug
Public bug reported:
It acts more like a gui version of ar -t or ar -x respectfully.
Test case:
right click on a .deb file > Open with archive manager
What is displayed is seen in first attached screenshot.
What has always previously been displayed is seen in 2nd attached screenshot
This same
current view with file-roller (archive manager) from context menu
** Attachment added: "Screenshot from 2015-10-04 12-04-25.png"
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1502652/+attachment/4484003/+files/Screenshot%20from%202015-10-04%2012-04-25.png
--
You received this
** Description changed:
- Please note that this bug is being filed on a recent 15.10 Ubuntu image
- install but from a gnome session
+ ** this appears to be that the display is blanked/asleep at greeter & login.
+ Forcing or waiting for screen to blank/sleep then waking up restores display
+ See
Demonstration 2
If the autostart script was in place then disable
Alter the sleep time of unity-greeter from 300 to 6 (sec) in
/usr/share/glib-2.0/schemas/com.canonical.unity-greeter.gschema.xml
(at bottom of file, assumes 6 sec is enough time to enter password, if not
increase 6 to something
Also affects Xubuntu
** Also affects: xfce4-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1501041
Title:
** Summary changed:
- No visible display in ubuntu session when using nvidia drivers via
nvidia-prime
+ No visible display in ubuntu session when using nvidia drivers via
nvidia-prime until screen goes to sleep, then waked up
** Description changed:
Please note that this bug is being filed
What happens in an ubuntu session is -
After logging in, no display. If the session is left inactive until display is
put to sleep, then awakining it thru keyboard or mouse brings back a visible
display. (default is 5 min. of inactivity
A simple startup script via startup applications
journalctl from a gnome session
** Attachment added: "gnome-journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479224/+files/gnome-journalctl.log
--
You received this bug notification because you are a member of Desktop
Packages, which is
journalctl from an ubuntu session
** Attachment added: "no-display-journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479223/+files/no-display-journalctl.log
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
Please note that this bug is being filed on a recent 15.10 Ubuntu image
install but from a gnome session
In a nutshell -
Once nividia drivers are installed & used from nvidia-prime there is no longer
a visible display in unity-greeter nor in an ubuntu session once logged
gpu-manager log from an ubuntu session
** Attachment added: "gpu-manager-ubuntu.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479225/+files/gpu-manager-ubuntu.log
--
You received this bug notification because you are a member of Desktop
Packages, which
Ex. of stdout from playing a vid in cli player in an ubuntu session with
nvidia(vdpau), no errors
(obviously I only here sound as there is no visible display
Playing: 1.mp4
(+) Video --vid=1 (*) (h264)
(+) Audio --aid=1 --alang=und (*) (aac)
AO: [pulse] 44100Hz stereo 2ch float
Using hardware
*** This bug is a duplicate of bug 1501041 ***
https://bugs.launchpad.net/bugs/1501041
** This bug has been marked a duplicate of bug 1501041
No visible display in ubuntu session when using nvidia drivers via
nvidia-prime
--
You received this bug notification because you are a member of
glxinfo log from an ubuntu session
** Attachment added: "glxinfo.log"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1501041/+attachment/4479226/+files/glxinfo.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Installed fine in 14.04.3 (using hwe vivid stack), both the lib & -dev packages
Also allowed desmume to install & open
** 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
Also fails to produce a display on Xubuntu & Lubuntu, both of which use
lightdm
** Also affects: lightdm
Importance: Undecided
Status: New
** Summary changed:
- nvidia via nvidia-prime on Ubuntu, no display
+ nvidia via nvidia-prime, no display on Ubuntu, Xubuntu, Lubuntu & probably
On 2 new 09/22 image installs -
Ubuntu-Gnome - install nvidia-352, reboot, works on nvidia fine
Ubuntu - install nvidia-352, reboot, no display (black) on unity-greeter, no
display on log in (blind from greeter
** Summary changed:
- nvidia fails, likely from xserver-core
+ nvidia fails on
** Summary changed:
- nvidia fails on nvidia via nvidia-prime on Ubuntu
+ nvidia via nvidia-prime on Ubuntu, no display
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1492864
Title:
You should just set texlive-lang-cjk as an *actual* Suggest: for ghostscript,
not a Recommend:
Why? -
Well the Ubuntu image will not contain that package nor any texlive packages so
the bug will still be present to the relatively few affected.
For them to fix they'd need to install
I will amend the above -
On a fresh install texlive-lang-cjk does show as a recommend of libgs9-common.
Still would need to be installed by the user so still seems making it a suggest
would be better, what's the difference other than forcing 800+MB of unneeded
packages on most users when it's
Just to note -
On Ubuntu-gnome 15.10 install, same hardware have gotten nvidia via
nvidia-prime to work. Initially on fresh install it did the same, ie. black
greeter, black login.
Downgrading those 2 xorg packages & a reboot allowed nvidia to work. Then
upgraded xserver back & it still worked
** Summary changed:
- Fails to load nvidia, fails to fallback to intel properly
+ nvidia fails, likely from xserver
** Description changed:
- Fresh install of 15.10, image of 09/06, only synaptic installed
+ Fresh install of 15.10, image of 09/06, only synaptic installed
Hardware is
Public bug reported:
Test Case:
r. click > New Document
Try to directly open the created file with a double left click
A pop up about 'file is of unknown type' , ect.
(- gedit can open & edit the file, directly or thru the context menu.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package:
nvidia driver install log
** Attachment added: "installnv.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458481/+files/installnv.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime
Xorg.0.log prior to nvidia driver install
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458482/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
lightdm.log prior to nvidia driver install
** Attachment added: "lightdm.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458483/+files/lightdm.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
from boot up with nvidia to black greeter, blind log in to black screen
** Attachment added: "unity7.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458583/+files/unity7.log
--
You received this bug notification because you are a member of Desktop
Public bug reported:
Fresh install of 15.10, image of 09/06, only synaptic installed
Hardware is i7-4700MQ CPU, IntelĀ® Haswell Mobile Nvidia GT770m
Initial bootup/ login is fine
Installed nvidia-352, install went fine, will attach log
Rebooted to a black greeter screen (heard sound
Logged in
lightdm.log after nvidia install
** Attachment added: "1ldm.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458488/+files/1ldm.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in
An Xorg crash report is generated, not sure of value, goes to the Db
anyway
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1492864
Title:
Fails to load nvidia, fails to fallback
Xorg.0 .log after nvidia install
** Attachment added: "1xorg.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1492864/+attachment/4458487/+files/1xorg.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime
At least here & others confirmed with recent nvidia mobile chips the latest
nvidia drivers from the new ppa & an edit to xorg.conf eliminates most tearing
(some vids here show a little on occasion
The ppa - https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa
The additional line added
Found what generates & regenerates the xorg.conf & patched to include the
tearfree line.
Users wishing to test can get an patched ubuntu-driver-common here,
instructions on page to get going & how to purge if unsuitable.
Note that it's for Trusty only
Just to note about the above -
If nvidia-prime is used to switch to the intel gpu the xorg.conf is removed or
moved to xorg.conf.xx
When switching back a new xorg.conf is created which will not contain the
Option "TearFree" "True" line.
Whether whatever creates that xorg.conf should add
2 things here -
This never occurs on the 1st. insertion of blank optical media in an internal
cd/dvd drive but happens on all subsequent insertions in that session
This never occurs when automount is disabled (org.gnome.desktop.media-
handling
There is likely no tie in to the above 2 but does
** Information type changed from Private to Public
--
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/1490090
Title:
totem crashed with SIGSEGV Or 'No h.265 support in gstreamer'
Status
*** This bug is a duplicate of bug 1424466 ***
https://bugs.launchpad.net/bugs/1424466
** This bug has been marked a duplicate of bug 1424466
Devel package not installable in 14.04.2 (mesa-lts-utopic
--
You received this bug notification because you are a member of Desktop
Packages,
Works fine here also, some above comments are using wrong version (not from
-proposed, it's 0.4.3.1, not 0.4.3build1 -
$ dpkg -l | grep libtimezonemap
ii libtimezonemap-data 0.4.3.1
all GTK+3 timezone map
Anyone know of a workaround for this?
Do a fresh install using the 14.04.1 image from Ubuntu old-releases.
If needing for some reason a newer mesa then use a ppa like xorg-edgers fresh X
crack or oibaf
--
You received this bug notification because you are a member of Desktop
Packages, which is
This appears to have been fixed with unity-settings-daemon
14.04.0+14.04.20140606-0ubuntu3
At least a short test shows log outs restarts are not re-enabling the
touchpad.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Changed in: unity-settings-daemon (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: unity-settings-daemon (Ubuntu)
Status: Fix Released = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
And the shame of it is it would only take a min. to add to
debian/patches/ubuntu-config.patch a section changing the default of 1
(Low) to 0 (Off)
option name=focus_prevention_level type=int
_shortFocus Prevention Level/_short
** Tags added: trusty-lts
** Description changed:
Is the current default of low actually doing anything positive?
Two examples of where low interferes Off produces expected behavior
Download something in Firefox
Go expose FF dropdown for downloads
R. click on the dl Open
301 - 400 of 1302 matches
Mail list logo