for the xpad guys. the FreeBSD port has the same issue
** Also affects: xpad (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: xpad (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On 07/19/2017 01:22 PM, Tommy Nevtelen wrote:
> What do you mean when you say it's working? On 17.10 the display just
> freezes when I load the nvidia driver 378 or 384 with modeset=1.
>
Did you do as I laid out in link above? Works just fine here in 17.10 &
16.04.3 (from -proposed
--
You
*** This bug is a duplicate of bug 1705157 ***
https://bugs.launchpad.net/bugs/1705157
** This bug has been marked a duplicate of bug 1705157
On fresh install or fresh boot greeter always show "ubuntu" though selected
session may be ubuntu-wayland
--
You received this bug notification
In other words the greeter will always show "ubuntu" as selected even if
last session was ubuntu-wayland
** Also affects: gdm
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- Test case:
+ Test case:
Do a fresh install of current image (july 19 here
Boot up, check selected session at the greeter - it will say "ubuntu"
Log in, ck. env., it will actually be ubuntu-wayland
Ex.
$ env | grep -i wayland
DESKTOP_SESSION=ubuntu-wayland
Public bug reported:
Test case:
Do a fresh install of current image (july 19 here
Boot up, check selected session at the greeter - it will say "ubuntu"
Log in, ck. env., it will actually be ubuntu-wayland
Ex.
$ env | grep -i wayland
DESKTOP_SESSION=ubuntu-wayland
WAYLAND_DISPLAY=wayland-0
Public bug reported:
Test case on a laptop:
With nvidia drivers installed, set prime profile of Intel, reboot
Open nvidia settings to confirm it opens.
Let machine stand for 10 min. or so until screen blanks.
Wake up, unlock, then try to open nvidia-settings
What happens: nothing
>From terminal
This happening in an ubuntu-wayland session is well known & expected behavior.
However now it's occurring in the default ubuntu session which is new &
hopefully unexpected behavior.
Note that some other apps would be also affected, example gparted
** Tags added: ubuntu-session
--
You received
Is now working but users need to set up themselves, instructions here
https://ubuntuforums.org/showthread.php?t=2365449=13663158=1#post13663158
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: nvidia-prime (Ubuntu)
Status: Confirmed => Fix Released
Public bug reported:
Test case:
Install nvidia drivers ,restart.
Open nvidia-settings, switch prime profile.
Will be prompted to log out/in, do so
What happens: user goes into a log in loop
To actually get back to the ubuntu-session one must restart.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Seen in Ubuntu 17.04 nvidia-375.66 but has no affect on install or use..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662860
Title:
/sbin/ldconfig.real: /usr/lib/nvidia-375/libEGL.so.1 is not a
vaapi in mpv in a wayland session was broken due to this commit
https://github.com/mpv-player/mpv/commit/bba08e38ff9842c4edf9da6a1d54066a01acd982
Testing here a reversion to allow, seems ok for at least me to date, as in
Just to clarify current behavior with recent gdm updates
If nvidia drivers are installed but not in use (intel prime profile) then the
wayland on ubuntu option is present & usable.
If the nvidia drivers are in use (nvidia prime profile) then the wayland on
ubuntu option is no longer available
On 07/13/2017 07:49 AM, Daniel van Vugt wrote:
> Sounds like this is the opposite of bug 1697882 :)
>
Yes, atm bug 1697882 doesn't exist, at least as tested here with a
couple of hybrid laptop machines (optimus
I don't believe this should of been unknown behavior as, for example,
all
On 07/11/2017 12:35 PM, Iain Lane wrote:
> Doug, are you saying that what Alberto is saying - that X11 sessions
> with KMS enabled on Nvidia is broken - isn't right?
>
> Maybe the two of you could look into that together.
>
Absolutely isn't broken, at least here with a hybrid(
Just to reiterate, scorecard here on i7-4700MQ, GeForce GT 755M,
nvidia-375.66 drivers, prime profile of nvidia selected.
gnome-wayland session, gdm, KMS = total fail
gnome-wayland session. gdm = total fail
default (ubuntu) session, gdm KMS, = all good, happy days, PRIME
Synchronization = yes
xorg-server-hwe-16.04 (2:1.19.3-1ubuntu1~16.04.1) is working fine here (along
with other related or required -proposed packages listed here.
Additionally with a modification to
/etc/modprobe.d/nvidia-graphics-drivers.conf to enable KMS PRIME
Synchronization is working on my hybrid (optimus)
For 17.10 fresh install the best solution was just the "disable pulseaudio's
bluetooth in gdm", i.e.
Add this to /var/lib/gdm3/.config/pulse/default.pa:
#!/usr/bin/pulseaudio -nF
#
# load system wide configuration
.include /etc/pulse/default.pa
### unload driver modules for Bluetooth hardware
ture: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-56-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: doug 1843 F pulseaudio
/dev/snd/controlC0: doug 1843 F pulseaudio
Cu
Actually stand corrected, after a couple of restarts PRIME Synchronization is
now working.
So until you all can provide nvidia thru Wayland X11 sessions Should be
allowed..
$ xrandr --verboseScreen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x
16384
eDP-1-1 connected primary
Don't see it crashing X11 session here at all, 17.10 -
$ echo $DESKTOP_SESSION
ubuntu
sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
(- But the disappointing thing is this -
$ xrandr --verbose
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
eDP1 connected primary
With gdm3 there is no option for wayland
** Also affects: gdm3 (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/1702345
Title:
ubuntu-wayland:
Public bug reported:
Just loops back to greeter.
Where is EGLStreams support?
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-session 3.24.1-0ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm
Public bug reported:
It has to be disconnected then reconnected to work
Test case:
wireless usb mouse connected
reboot, login to ubuntu-wayland session
What happens:
wireless mouse doesn't work. To get functional it has to be removed &
reconnected.
log attached, device is initially found @
@Eric (although you do not seem to have subscribed to this bug report).
Your issue is different than what this bug report is/was covering.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1649905
Title:
** Changed in: serverguide
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604010
Title:
sntp missing
To manage notifications about this bug go to:
** Changed in: serverguide
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697861
Title:
Server-guide should get a section about accessing qemu monitor via
** Changed in: serverguide
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686330
Title:
Server-guide should get a section about VF and usb passthrough
To manage
** Changed in: serverguide/trunk
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676058
Title:
build process extra doctype directive
To manage
On 2017.06.04 22:51 Doug Smythies wrote:
> Due to good subject matter expert contributions, we want
> to do another 16.04 Ubuntu serverguide point release already.
>
> The .POT file has been updated and translation work can be done.
> We will target the actual point release for a
Still not working in 17.10 dev (gdm3
Workaround by James does allow audio but you all need to fix this if you're
dumping lightdm
** Tags added: aardvark
** Tags added: gnome-3.24
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: gdm3 (Ubuntu)
Status: New =>
@Daniel van Vugt (vanvugt): Thanks for your assistance!
I am not Mary Sherman, and I'm continuing to experience this problem,
even with the PPA and after rebooting.
I didn't subscribe to this bug, I didn't even know about it. I report
bug 1691556 and you marked it a duplicate of this one.
As
if someone
wants more time.
Reference:
https://translations.launchpad.net/serverguide
... Doug
On 2016.12.22 16:46 Doug Smythies wrote:
> On 2016.12.06 23:32 Doug Smythies wrote:
>
>> The Ubuntu serverguide is only released on a per LTS basis.
>> i.e 12.04, 14.04, and 16.04.
&
The problem appears to be with setting up the input sink, which I
couldn't care less about. If any knows of a way for bluez / pulseaudio
to force a device to just connect as an output-only device (e.g., normal
bluetooth speaker), I think I'd be fine, as I have no problems with
numerous other
@hife and @Mary Sherman (spot9019): Thanks for the speedy replies!
@hife: Thanks for describing your workaround in greater detail.
I've already tried the a2dp.py script, it doesn't fix the problem for
me. I just downloaded again the latest version and
@hife and @Mary Sherman (spot9019):
You both indicate that the latest pulse-testing ppa fixes the problem
for you.
Can you both indicate whether you are running Unity as the desktop or
KDE or perhaps some other?
I still have suspicions that there may be a permissions issue that is
specific to
I must unfortunately report that that the recently reported fix does not
work for me. Ubuntu 16.04 LTS connecting to Amazon Echo. Pulseaudio
1:8.0-0ubuntu3.3~xenial1, which is the latest presently available from
ppa:ubuntu-audio-dev/pulse-testing as of today.
The problem appears to result in
g, even the second to last one.
I have managed to stop this on my main test server, but I have no
idea if I did it correctly.
References:
https://bugs.launchpad.net/serverguide/+bug/1031091
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1647790
... Doug
--
ubuntu-server
Public bug reported:
Since upgrading to Ubuntu 17.04 (zesty), okular starts up with an
initial window size which is much too small (640x480 pixels, which is
tiny on my screen). Each time I invoke okular I first have to adjust
the window size to something useable, but the next time I invoke it,
marking invalid as old news, who cares, ect. ect.
** Changed in: mpv (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1371978
Title:
video rendering can break
Additionally, this issue also appeared along the line with Ubuntu+KDE
and apparently was easily resolved, as described in ubuntuforums.org,
[link](https://ubuntuforums.org/showthread.php?t=2318966). Quoting
another ubuntuforums.org post (also KDE),
I should also note that on the askubuntu.com site, I speculate that it
may just be some permission issue deep down somewhere, and why.
** Description changed:
- Pairing and coupling to Amazon Echo works, but sound is heard.
+ Pairing and coupling to Amazon Echo works, but no sound is heard.
Public bug reported:
Pairing and coupling to Amazon Echo works, but no sound is heard.
I believe the issue is related to the fact that Amazon Echo is paired as
a handset (i.e., speaker + microphone) rather than just as a speaker. I
believe the critical error is found in a dmesg line such as:
Kernel 4.12-rc1 has this change, so the console now defaults to never
going blank. I disagree with this change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869017
Title:
Ubuntu server enables
It appears that there have been several unreleased commits to netatalk's
2.2 branch after the release of 2.2.5:
https://github.com/Netatalk/Netatalk/commits/branch-netatalk-2-2
One of the commits from September 1, 2014 appears to fix this problem,
and the other one is probably a fix for the
Public bug reported:
After upgrading from trusty to xenial, I've noticed that old classic Mac
clients logging in through AppleTalk see an empty volume list from afpd.
The server appears in the Chooser on the Mac, but after you log in, the
volume list being supplied is empty.
Public bug reported:
Test case:
use sudo apt build-dep amarok
get source build as package, i.e. dpkg-buildpackage -uc -us -b
What happens: fails at end with /usr/bin/ld: cannot find -llz4
One way to resolve is to install liblz4-dev
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: amarok
** Description changed:
- Refer to https://help.ubuntu.com/13.04/serverguide/postfix.html
+ Refer to https://help.ubuntu.com/lts/serverguide/postfix.html
By default IPv6 privacy extensions is installed on Ubuntu server and
temporary addresses are preferred.
This means that outgoing
tested nagios-nrpe-server
2.15-1ubuntu3 on yakkety
2.15-1ubuntu1.1 on xenial
Both tests yielded same result as described in comment #18, i.e.
positive, as intended.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
plymouthhd crashers have been happening for years now, never ever fixed
so why start now. Just ignore or set apport to ignore..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542000
Title:
Tested 3.0.1-3ubuntu0.17.04.1 on zesty with positive result.
nrpe.cfg:dont_blame_nrpe=0 [ is set this way as part of install - no
editing done ]
In syslog:
May 4 21:36:18 cmonb nrpe[6381]: Error: Request contained command arguments,
but argument option is not enabled!
May 4 21:36:18 cmonb
Checking in 17.10 PRIME Synchronization can be enabled & works in
UbuntuGnome but doesn't in Ubuntu. Main reason is in UbuntuGnome
nvidia_drm.modeset can be enabled, in Ubuntu it can't.
ex.'s
UbuntuGnome, gdm3
$ sudo cat /sys/module/nvidia_drm/parameters/modeset
[sudo] password for doug
Excerpts from mynrpe-server's /var/log/syslog when running check_nrpe
from mynagios-master (nrpe.cfg debug=1):
Before install of xenial recompiled package:
ubuntu@mynagios-master:~$ sudo -unagios /usr/lib/nagios/plugins/check_nrpe -H
192.168.1.12 -p 5664 -c check_procs -a rsyslogd 1 0
No - the current behavior is the permissions property is ignored.
Currently the user is just informed that the launcher is untrusted with
no option to set as trusted. See attached
** Attachment added: "Screenshot from 2017-04-29 11-41-13.png"
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674304
Title:
PRIME synchronization not working with xserver-1.19.x
To manage notifications about this bug go to:
>From reading the Debian bug #756479 cited above, it appears there was
considerable impact to users whose Nagios monitors depended on this
feature when upgraded to 2.15. Some users of NRPE are customers of
Canonical's, one of whom I support as a Dedicated Support Engineer.
This customer would
This is fixed with updated systemd package so marking as such. The
install image is broken but I guess 4+ months wasn't enough time to get
it together...
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux
Status: New => Invalid
**
Just upgraded to 17.04 from 16.10 and it's just plain broken (i.e. h/w
restart and/or 'service network-manager-restart' doesn't fix it).
Tried GRUB boot from 14.04 (which I still have on a spare partition) and
all working ok - so we can't blame hardware or ISP problems...
--
You received this
Noting that above suggestion probably doesn't help ethernet..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654918
Title:
No Internet access with default of Automatic (DHCP)
To manage
Another 'fix' suggested is to
Open
/etc/NetworkManager/NetworkManager.conf
add lines
[device]
wifi.scan-rand-mac-address=no
then
sudo service network-manager restart
I'm fine with just changing the nameservers as previously mentoned, in
any event users shouldn't have to do anything. (even with
*** This bug is a duplicate of bug 1551886 ***
https://bugs.launchpad.net/bugs/1551886
The automated link to bug 1551886 does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564997
@Walter: On our forums exchanges, I missed that your "stuck" messages
have "[ksmd:64]" at the end. I get that often also, but I also sometimes
get "[qemu-system-x86:8549]" and "[qemu-system-x86:8552]".
I do not know what commits may or may not have been migrated back to
kernel 4.10. At least for
Public bug reported:
Will not run without netstat & net-tools package is neither a dep or installed
on image by default.
Test case:
Install gufw
Try to open
What happens:
>From terminal will see this message
Traceback (most recent call last):
File "/usr/share/gufw/gufw/gufw.py", line 30, in
While much better the 4.11 kernel is reported fail occasionally in this
regard. This is in contrast to current kernel in 17.04 (4.10.x) where
this happens all the time either right away or after the first reboot or
so..
** Summary changed:
- No Internet access with default of Automatic (DHCP) &
*** This bug is a duplicate of bug 1654918 ***
https://bugs.launchpad.net/bugs/1654918
** This bug has been marked a duplicate of bug 1654918
No Internet access with default of Automatic (DHCP)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
of it actually working,
tearing while using nvidia drivers (375.x) is rampart.
Testing with both current 4.10.0-13 & previous 4.9.0-11 kernels.
Shows this in kern.log so support is enabled
Mar 19 08:18:47 doug-Lenovo-IdeaPad-Y510P kernel: [1.746443] [drm]
Supports vblank times
also seen in Ubuntu-Gnome install
** Also affects: network-manager
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/1654918
Title:
No Internet access with
The reference that was 192 MB of RAM was for the server edition only,
and was updated to 256 MB recently. While 256 MB works for me, it
doesn't work for someone else. See also:
https://bugs.launchpad.net/serverguide/trunk/+bug/1294908
--
You received this bug notification because you are a
** Changed in: serverguide/precise
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173426
Title:
html - new theme - in .xml does not display with
For me these messages were a side effect of unattended upgrades, and the
os-prober running as some auto-removal thing. All stuff that I do not
want, and did not use to be the default. Having either disabled or
uninstalled that stuff, I now expect these message to go away.
--
You received this
The upstream link is no good, and I haven't been able to find it on
bugzilla.kernel.org by searching.
It is unclear to me why this bug report was set to incomplete.
While I do get the log entries listed herein, I am also using the latest
mainline kernel, 4.11-rc5 (but also noticed it for the
The correct upstream link is:
https://bugzilla.kernel.org/show_bug.cgi?id=194835
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671287
Title:
I'm not working with SGI, JFS and QNX4.
To manage
Tested with both nvidia-375 & nvidia-378 (deb packages) & various kernels
(ubuntu packaged
17.04 - same deal with 4.9.x & 4.10.x
16.04 - same deal with 4.8.x, 4.9.x & 4.10.x
In all cases see a single line in Xorg.0.log -
randr: falling back to unsynchronized pixmap sharing
--
You received
Public bug reported:
Test case: log in to a unity8 session
Log out & in to unity7 session
Try to open System Settings from indicator
What happens: nothing as it's attempting to open unity8's system settings
A reboot is needed to return proper behavior in an unity7 session
ProblemType: Bug
to manage the process, ultimately putting the translations
back into Launchpad, perhaps as a .po file import.
... Doug
--
ubuntu-translators mailing list
ubuntu-translators@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-translators
error for all apps would be like in screenshot (files
scope is also shown, this is how it opens,i.e. empty, nothing to do..
** Attachment added: "screenshot20170401_204726118.png"
Public bug reported:
scope just shows 'Manage', nothing else
No gnome apps will open, either close immediately or windows shows blue
spinning 'cursor' forever
Only webbrowser, terminal & libreoffice apps open
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity8
Public bug reported:
occurred during boot
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: i386
*** This bug is a duplicate of bug 1677054 ***
https://bugs.launchpad.net/bugs/1677054
Public bug reported:
This error popped up on boot.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
Uname:
Lets call invalid as option to allow all users will allow guest wifi
automatically. Whether this should be the default setting would be the
only possible bug, not sure that matters
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you
Lets call invalid as option to allow all users will allow guest wifi
automatically. Whether this should be the default setting would be the
only possible bug, not sure that matters
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because
** Attachment added: "kernel log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1674304/+attachment/4848212/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674304
On 03/27/2017 02:03 PM, Mario Kleiner wrote:
> Is the nvidia-drm module loaded and its drm modesetting enabled?
>
> E.g., via kernel cmdline option nvidia_drm.modeset=1
> cat /sys/module/nvidia_drm/parameters/modeset should be 1 or "Y"
>
> I think that isn't needed for PRIME outputs, but it is
Adding linux as also seems resolved using the latest kernel, tested with
4.11.0-041100rc4-generic #201703261831 from mainline
** Also affects: linux
Importance: Undecided
Status: New
** Summary changed:
- No Internet access with default of Automatic (DHCP)
+ No Internet access with
Public bug reported:
Likely not network-manager but it's affected & got to start somewhere.
Test case:
Boot up to greeter & login to guest session.
Click on network indicator, choose wifi network used by main user
What happens:
Password to network must be entered, then a keyring must be created.
** Changed in: serverguide/trusty
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675452
Title:
submit button of find field is shifted down
To manage
** Changed in: serverguide/trusty
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676058
Title:
build process extra doctype directive
To manage
** Changed in: serverguide/trunk
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676058
Title:
build process extra doctype directive
To manage
** Changed in: serverguide/trusty
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675452
Title:
submit button of find field is shifted down
To manage
** Changed in: serverguide/trusty
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676058
Title:
build process extra doctype directive
To manage
@Gunnar : you are too fast for me. I would have checked out desktop docs
eventually, particularity since that is where I stole that part of the
Serverguide Makefile from in the first place.
Because builds with a 14.04 computer used to work fine and that part of
the Makefile is so old, I can only
Ot to FFe
Bug filed regarding PRIME synchronization with hybrid hardware implemented via
nvidia-prime
Bug 1674304
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671799
Title:
FFe: xserver 1.19.3
** Changed in: serverguide/trunk
Status: In Progress => Fix Committed
** Changed in: serverguide/trusty
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
=> Won't Fix
** Changed in: serverguide/trunk
Status: Triaged => In Progress
** Changed in: serverguide/trusty
Status: New => Triaged
** Changed in: serverguide/trusty
Importance: Undecided => Medium
** Changed in: serverguide/trunk
Assignee: (unassigned) =>
O.K. Gunnar, Pavel, I now understand what I was not understanding
before. It looks O.K. on my test web site. I'll assign myself the
serverguide, no use fixing the 12.04 serverguide.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
16.04 Ubuntu desktop with default firefox has the issue.
14.04 Ubuntu desktop with default firefox does NOT have the issue.
(45.0+build2-0ubuntu0.14.04.1)(not up to date, and I see firefox in the
update list. Will report back later after updates).
--
You received this bug notification because
O.K., I have re-created the issue on my test 17.04 desktop (VM) and my
16.10 test Laptop using the default firefox web browser.
The issue does not occur with any of 3 different web browsers from my
windows 10 laptop.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Can we get some more details please. So far, I am unable to recreate the
situation shown in the screen shot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675452
Title:
submit button of find field
@fish : Yes your issue does not belong here.
To figure out where your issue actually belongs, some details are
missing:
If your stuck at low frequency issue only occurs after a suspend and on
battery power, then your issue is covered by:
https://bugzilla.kernel.org/show_bug.cgi?id=90041 (and it
$ inxi -G
Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
Card-2: NVIDIA GK107M [GeForce GT 755M]
Display Server: X.Org 1.19.3 drivers: modesetting,nvidia
Resolution: 1920x1080@59.91hz
GLX Renderer: GeForce GT
701 - 800 of 6714 matches
Mail list logo
