Thanks for the patch, I was having the same issue and this fixed it for
me as well. Much appreciated!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1308187
Title:
Python (v2.7) requires to install p
Blacklisting the nouveau driver worked for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301490
Title:
"PRIME Profiles" option no longer available in Nvidia Settings
To manage notifica
Still affecting me pretty severely, I have all software updates.
I'm using a Nvida Optimus card as well. Occurs with both Nouveau and
Nvidia drivers, as reported. I'm using the Intel card with the Nvidia
drivers.
Minimize freezes the system about 90% of the time. I have to drop to
shell and reboo
I am upstream. The issue is that "gnome-sudoku" is still in your repos.
despite being told repeatedly (elsewhere) to remove it. gnome-sudoku is
part of Gnome Games now and uses the same .py files and paths that the
(very) old gnome-sudoku uses. This is a case that python-support cannot
handle corre
gnome-sudoku IS NOT gnome-games. Please stop confusing the two; do not
file any more bug reports on gnome-sudoku; it should have been removed
from the Ubuntu repositories ages ago.
--
gnome-games should depend on python-glade2
https://bugs.launchpad.net/bugs/230163
You received this bug notificat
*** This bug is a duplicate of bug 234865 ***
https://bugs.launchpad.net/bugs/234865
** This bug has been marked a duplicate of bug 138509
package glchess None [modified: /var/lib/dpkg/info/glchess.list] failed to
install/upgrade: trying to overwrite `/usr/share/applications/glchess.deskto
** This bug has been marked a duplicate of bug 138509
package glchess None [modified: /var/lib/dpkg/info/glchess.list] failed to
install/upgrade: trying to overwrite `/usr/share/applications/glchess.desktop',
which is also in package gnome-games
** This bug is no longer a duplicate of bug 138
On Debian, you need python-gnome2 and python-gnome2-desktop.
** Changed in: gnome-sudoku (Ubuntu)
Status: New => Confirmed
--
gnome-sudoku won't start
https://bugs.launchpad.net/bugs/230163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have applied your patch to Gnome Games upstream. It will be in release
2.23.5. Thanks for the good work!
** Changed in: glchess (Ubuntu)
Assignee: (unassigned) => Jason D. Clinton (me-jasonclinton)
Status: New => Fix Committed
--
glchess fails to render in 3d view
Hello. We are using firefox-2 on a large LTSP enterprise desktop roll-
out and this bug is still there in Hardy. I have tested Debian unstable
and the bug is not there so it's probably related to the way the
firefox-2-gnome-support package is being built.
--
Bad gnome vfs support
https://bugs.lau
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Mozilla Team (mozillateam)
--
Bad gnome vfs support
https://bugs.launchpad.net/bugs/153716
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Hi, I'm an Gnome Games maintainer in upstream. This appears to be a
dependency problem in the Ubuntu package. It should depend on
python.*gnome.*desktop.
--
gnome-sudoku won't start
https://bugs.launchpad.net/bugs/230163
You received this bug notification because you are a member of Ubuntu
Bugs,
Ubuntu must use the open source Radeon DRI2 driver or ATI must support
GL-on-GL. There is no other fix.
--
gnometris doesn't display the game area
https://bugs.launchpad.net/bugs/428396
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi, I am the upstream maintainer of Gnometris. This appears to be a bug
in fglrx. The critical warnings are harmless, as far as I know--I get
them they do not cause any issues. Can you try without compositing
window manager? I think that fglrx is failing to render OpenGL while
compositing.
--
gno
This is a bug in fglrx, not Gnometris (or Clutter). It works fine on
Intel and NVidia.
--
gnometris doesn't display the game area
https://bugs.launchpad.net/bugs/428396
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
Yes, 2.28 is the first release with Clutter.
On Oct 5, 2009 7:30 PM, "Serge" wrote:
But it only happens in kramic koala not earlier releases
-- gnometris doesn't display the game area
https://bugs.launchpad.net/bugs/428396 You received thi...
--
gnometris doesn't display the game area
https:/
This bug is already open upstream.
https://bugzilla.gnome.org/show_bug.cgi?id=594970
** Bug watch added: GNOME Bug Tracker #594970
http://bugzilla.gnome.org/show_bug.cgi?id=594970
--
in Gnometris, the game option "Show where the block will land" doesn't take
effect
https://bugs.launchpad.net
Ubuntu should be shipping radeon with KMS and DRI2 enabled. If they
aren't, that's a bug.
--
gnometris doesn't display the game area
https://bugs.launchpad.net/bugs/428396
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
The open source driver uses DRI2 and is not affected by fglrx's
shortcomings. I would recommend the open source radeon driver.
On Sat, Oct 17, 2009 at 8:48 PM, gavintlgold
wrote:
> It's unfortunate that this happens, but any way to disable the clutter
> graphics while desktop effects are running
Anyone know if this affects KDE on 19.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774902
Title:
kubuntu - can't login with NFS $HOME
To manage notifications about this bug go to:
https://bug
My solution has been to fully remove all snap functionality.
sudo apt purge snapd
sudo rm -vrf /snap /var/snap /var/lib/snapd /var/cache/snapd /usr/lib/snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
I can confirm this bug and workaround on kubuntu 20.04.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
$
$ ls -la $HOME/.config/plasma-workspace/env/nfs_home_workaround.sh
-rwxr-xr-x 1 ---
The KDE_HOME_READONLY workaround stopped working and failure behavior
changed last week after I applied updates to kubuntu 20.04.
Instead of a logout as previously experienced, NFS home now results in a
black screen with a mouse pointer.
See attached apt history.log and .xsession-errors for more
Created attachment 129548
apt history.log
apt history log showing updates that correspond to timing of
KDE_HOME_READONLY workaround no longer working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/177
Created attachment 129549
.xsession-errors
.xsession-errors file for new black screen behavior after recent
updates. Note that the read-only home directory error is no longer
displayed, so not sure how this relates to previous behavior.
--
You received this bug notification because you are a mem
** Also affects: kde-baseapps
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/1774902
Title:
kubuntu - can't login with NFS $HOME
To manage notifications a
Public bug reported:
If a users home directory is an NFS server, KDE fails to start with the
error "No write access to $HOME directory". The fact that the error is
logged to .xsession-errors in the users home directory is a bit ironic.
This is reproducible on 20.04 and 18.04
kelleher@numbersix:~
Reproducible on 20.04.
kelleher@numbersix:~$
kelleher@numbersix:~$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
kelleher@numbersix:~$
kelleher@numbersix:~$ apt-cache policy kubuntu-desktop
kubuntu-desktop:
Installed: 1.398
Candidate: 1.398
Version table:
*** 1.3
** Package changed: snapd (Ubuntu) => kubuntu-meta (Ubuntu)
** Package changed: kubuntu-meta (Ubuntu) => kubuntu-packaging
** Project changed: kubuntu-packaging => kubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same issue here. NFS fails to mount at boot, but logging in and issuing
a manual "mount -a" resolves until the next reboot.
It should also be noted that there's a significant delay on boot with
nfs entries in fstab - need to time it, but ~1 minute.
Why issues with something as old/stable/boring
I should note this is impacting an image built from 16.04.4. Another
image built from 16.04.1 is working fine.
Both have been pulled forward via apt dist-upgrade and their behaviors
differ - concerning in it's own right.
--
You received this bug notification because you are a member of Ubuntu
B
Quick update - switched to autofs as a workaround for this 16.04 issue.
That was fine until I ran 'apt upgrade' today. Now I get the following
error:
root@chi:~# ls -la /vol/home/
ls: cannot access '/vol/home/': Too many levels of symbolic links
root@chi:~#
I'll be opening a new bug for autofs
Public bug reported:
Description:Ubuntu 16.04.6 LTS
Release:16.04
I moved to autofs this week as a workaround for Bug #1577575 failing to
mount NFS entries at boot. This worked file until I ran 'apt upgrade'
today.
Now trying to access /vol/home mount results in the following error:
** Tags added: autofs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
autofs - "Too many levels of symbolic links" after apt upgrade
To manage notifications about this bug go to:
http
Looks like the issue is symlinking to a director prior to autofs
mounting it.
Everything fine...
root@numbersix:/# ssh chi uname -a
Linux chi 4.4.0-146-generic #172-Ubuntu SMP Wed Apr 3 09:00:08 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
root@chi:~# ls -la /home
ls: cannot access '/home': No such f
** Attachment added: "autofs.conf"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261266/+files/autofs.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title
** Attachment added: "master.d_direct1.autofs"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261265/+files/master.d_direct1.autofs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "auto.misc"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261271/+files/auto.misc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
** Attachment added: "auto.smb"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261268/+files/auto.smb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
au
** Attachment added: "auto.net"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261269/+files/auto.net
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title:
au
** Attachment added: "auto.direct1"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261267/+files/auto.direct1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Tit
** Attachment added: "auto.master"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261274/+files/auto.master
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Title
** Attachment added: "chi.packages"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577575/+attachment/5261278/+files/chi.packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
T
** Attachment added: "chi.packages"
https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1827286/+attachment/5261280/+files/chi.packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827286
Tit
I did a little more testing and this looks to be specific to /home.
Even mounting over /home (no linking) with autofs results in the same
issue.
All autofs files as well as the list of packages installed have been
attached.
As a side note, having /home as a link is an artifact of some very old b
Sorry - those last two comments were meant for bug #1827286.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577575
Title:
NFS share does not mount on boot using fstab
To manage notifications about
I did a little more testing and this looks to be specific to /home.
Even mounting over /home (no linking) with autofs results in the same
issue.
All autofs files as well as the list of packages installed have been
attached.
As a side note, having /home as a link is an artifact of some very old b
Public bug reported:
If $HOME is an NFS mount, startkde show a write error and fails to start
ksmserver.
Xsession: X session started for kelleher at Fri Jun 1 20:45:36 EDT 2018
localuser:kelleher being added to access control list
openConnection: connect: No such file or directory
cannot connec
The issue appears larger than just NFS mounted $HOME.
After I used the workaround provided to get the filebot snap to run with
an NFS mounted $HOME, I was unable to use it to manipulate any files in
my NFS mounted media library.
I gave up and just loaded the deb package.
Should this be reported
Public bug reported:
Unable to install/update mysq[common|server]-5.7 on Ubuntu 16.04
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-common 5.7.11-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
Uname: Linux 4.4.0-17-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
A
It appears that this bug has been fixed in the latest Precise update.
The notification disappears quickly now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/958492
Title:
Network disconnected notifi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/958492
Title:
Network disconnected notification doesn't work after clicking "Don't
show this message again"
To manage notifications about this bug go
Public bug reported:
In Gnome Shell when your computer comes out of Suspend mode, there is a
notification that says "Network Disconnected - You are now offline" with
a button that says "Never show this message again". The intended
behavior of this notification is that it will disappear as soon as
This is my experience with this bug. It only happens when I am
disconnected, usually from going into suspend mode when shutting my
laptop lid. When I open the lid and come back into live mode, I get this
notification, and it doesn't disappear until I click it.
But one thing I have noticed is that
I purged and marked snapd hold to prevent reinstall. Get rid of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662552
Title:
snaps don't work with NFS home
To manage notifications about this bu
I've solved my snap challenges problems with the following state entry
in Saltstack
cleanup_snapd:
pkg.purged:
- name: snapd
pkg.held:
- name: snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
56 matches
Mail list logo
