[Touch-packages] [Bug 2057943] [NEW] Can't disable or modify snap package apparmor rules
Public bug reported:
On Ubuntu 20.04 (and probably 22.04 and greater), it is impossible to
disable snap chromium apparmor rules:
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure
Can't find chromium.hook.configure in the system path list. If the name of the
application
is correct, please run 'which snap.chromium.hook.configure' as a user with
correct PATH
environment set up in order to find the fully-qualified path and
use the full path as parameter.
root@{HOSTNAME}:~# aa-complain snap.chromium.chromedriver -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.chromium -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not
found
It seems like no one has an answer on how these overly restricted rules
can be disabled:
https://askubuntu.com/questions/1267980/how-to-disable-apparmor-for-chromium-snap-ubuntu-20-04
https://ubuntuforums.org/showthread.php?t=2410550
https://ubuntuforums.org/showthread.php?t=2449022
https://answers.launchpad.net/ubuntu/+source/apparmor/+question/701036
So I just got rid of apparmor which doesn't seem like the solution I was
after, but it works great now:
sudo systemctl stop apparmor
sudo systemctl disable apparmor
Please give us a way to modify (and keep the rules permanently modified
even after snap updates) snap apparmor rules.
Thank you!
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2057943
Title:
Can't disable or modify snap package apparmor rules
Status in apparmor package in Ubuntu:
New
Bug description:
On Ubuntu 20.04 (and probably 22.04 and greater), it is impossible to
disable snap chromium apparmor rules:
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure
Can't find chromium.hook.configure in the system path list. If the name of
the application
is correct, please run 'which snap.chromium.hook.configure' as a user with
correct PATH
environment set up in order to find the fully-qualified path and
use the full path as parameter.
root@{HOSTNAME}:~# aa-complain snap.chromium.chromedriver -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.chromium -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global not found
root@{HOSTNAME}:~# aa-complain snap.chromium.hook.configure -d
/var/lib/snapd/apparmor/profiles
ERROR: Include file /var/lib/snapd/apparmor/profiles/tunables/global
not found
It seems like no one has an answer on how these overly restricted
rules can be disabled:
https://askubuntu.com/questions/1267980/how-to-disable-apparmor-for-chromium-snap-ubuntu-20-04
https://ubuntuforums.org/showthread.php?t=2410550
https://ubuntuforums.org/showthread.php?t=2449022
https://answers.launchpad.net/ubuntu/+source/apparmor/+question/701036
So I just got rid of apparmor which doesn't seem like the solution I
was after, but it works great now:
sudo systemctl stop apparmor
sudo systemctl disable apparmor
Please give us a way to modify (and keep the rules permanently
modified even after snap updates) snap apparmor rules.
Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057943/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004432] Re: GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-menu-bar background-image: -gtk-gradient
Jan 31 13:17:41 -VirtualBox kernel: [ 3549.055408] traps: mate-
panel[3931] general protection fault ip:7f486e9721dc sp:7ffe38388ac8
error:0 in libcairo.so.2.11600.0[7f486e90d000+d3000]
** Also affects: mate-panel (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: gtk+3.0 (Ubuntu)
** Description changed:
I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
- the latest version of GTK3 in Ubuntu 22.04, my theme no longer works due
- to a segfault caused by this rule:
+ the latest version of GTK3, Mate, and mate-panel in Ubuntu 22.04, my
+ theme no longer works due to a segfault caused by this rule:
.mate-panel-menu-bar {
- background-image: -gtk-gradient (linear,
- left top,
- left bottom,
- from (#3168d5),
- color-stop (0.15, #4490e6),
- color-stop (0.30, #235bd9),
- color-stop (0.90, #2562de),
- to (#1941a5));
- background-color: @selected_bg_color_top_menu;
- padding: 0px;
- color: @bg_color;
- text-shadow: none;
+ background-image: -gtk-gradient (linear,
+ left top,
+ left bottom,
+ from (#3168d5),
+ color-stop (0.15, #4490e6),
+ color-stop (0.30, #235bd9),
+ color-stop (0.90, #2562de),
+ to (#1941a5));
+ background-color: @selected_bg_color_top_menu;
+ padding: 0px;
+ color: @bg_color;
+ text-shadow: none;
}
If I remove the background-image property, the theme works and the
segfault doesn't happen. It appears that any -gtk-gradient set on
background-image for .mate-panel-menu-bar doesn't work and causes Mate
to segfault. I have to change the theme and restart to get things to
work again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004432
Title:
GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-
menu-bar background-image: -gtk-gradient
Status in mate-panel package in Ubuntu:
New
Bug description:
I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
the latest version of GTK3, Mate, and mate-panel in Ubuntu 22.04, my
theme no longer works due to a segfault caused by this rule:
.mate-panel-menu-bar {
background-image: -gtk-gradient (linear,
left top,
left bottom,
from (#3168d5),
color-stop (0.15, #4490e6),
color-stop (0.30, #235bd9),
color-stop (0.90, #2562de),
to (#1941a5));
background-color: @selected_bg_color_top_menu;
padding: 0px;
color: @bg_color;
text-shadow: none;
}
If I remove the background-image property, the theme works and the
segfault doesn't happen. It appears that any -gtk-gradient set on
background-image for .mate-panel-menu-bar doesn't work and causes Mate
to segfault. I have to change the theme and restart to get things to
work again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/2004432/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004432] Re: GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-menu-bar background-image: -gtk-gradient
Jan 31 13:17:41 -VirtualBox kernel: [ 3548.322902] mate-panel[1703]: segfault
at 7f32e0027552 ip 7f32dfc671eb sp 7ffc063f08f8 error 7 in
libcairo.so.2.11600.0[7f32dfc02000+d3000]
Jan 31 13:17:41 -VirtualBox kernel: [ 3548.322912] Code: 52 07 00 e8 87 c9 f9
ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 89 f8 48 85 ff 74 14 8b 57 18 83 fa ff
74 0c 8b 57 18 85 d2 7e 06 83 47 18 01 c3 50 48 8d 0d 17 56 07 00 ba a2 03
00 00 48 8d 35
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004432
Title:
GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-
menu-bar background-image: -gtk-gradient
Status in mate-panel package in Ubuntu:
New
Bug description:
I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
the latest version of GTK3, Mate, and mate-panel in Ubuntu 22.04, my
theme no longer works due to a segfault caused by this rule:
.mate-panel-menu-bar {
background-image: -gtk-gradient (linear,
left top,
left bottom,
from (#3168d5),
color-stop (0.15, #4490e6),
color-stop (0.30, #235bd9),
color-stop (0.90, #2562de),
to (#1941a5));
background-color: @selected_bg_color_top_menu;
padding: 0px;
color: @bg_color;
text-shadow: none;
}
If I remove the background-image property, the theme works and the
segfault doesn't happen. It appears that any -gtk-gradient set on
background-image for .mate-panel-menu-bar doesn't work and causes Mate
to segfault. I have to change the theme and restart to get things to
work again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/2004432/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2004432] [NEW] GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-menu-bar background-image: -gtk-gradient
Public bug reported:
I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
the latest version of GTK3 in Ubuntu 22.04, my theme no longer works due
to a segfault caused by this rule:
.mate-panel-menu-bar {
background-image: -gtk-gradient (linear,
left top,
left bottom,
from (#3168d5),
color-stop (0.15, #4490e6),
color-stop (0.30, #235bd9),
color-stop (0.90, #2562de),
to (#1941a5));
background-color: @selected_bg_color_top_menu;
padding: 0px;
color: @bg_color;
text-shadow: none;
}
If I remove the background-image property, the theme works and the
segfault doesn't happen. It appears that any -gtk-gradient set on
background-image for .mate-panel-menu-bar doesn't work and causes Mate
to segfault. I have to change the theme and restart to get things to
work again.
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004432
Title:
GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-
menu-bar background-image: -gtk-gradient
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
the latest version of GTK3 in Ubuntu 22.04, my theme no longer works
due to a segfault caused by this rule:
.mate-panel-menu-bar {
background-image: -gtk-gradient (linear,
left top,
left bottom,
from (#3168d5),
color-stop (0.15, #4490e6),
color-stop (0.30, #235bd9),
color-stop (0.90, #2562de),
to (#1941a5));
background-color: @selected_bg_color_top_menu;
padding: 0px;
color: @bg_color;
text-shadow: none;
}
If I remove the background-image property, the theme works and the
segfault doesn't happen. It appears that any -gtk-gradient set on
background-image for .mate-panel-menu-bar doesn't work and causes Mate
to segfault. I have to change the theme and restart to get things to
work again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2004432/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869115] Re: python sys.path different per user account - ImportError no module named (Focal, Bionic Beaver, and Xenial)
Bug is now prevalent in Ubuntu 16.04 Xenial. Looks like whatever change has broken this has made it all the way to Ubuntu 16.04. How come this hasn't been fixed yet? This is such a breaking and critical bug! For it to be in three major versions of Ubuntu is embarrassing. ** Summary changed: - python sys.path different per user account - ImportError no module named (Focal and Bionic Beaver) + python sys.path different per user account - ImportError no module named (Focal, Bionic Beaver, and Xenial) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869115 Title: python sys.path different per user account - ImportError no module named (Focal, Bionic Beaver, and Xenial) Status in python2.7 package in Ubuntu: New Bug description: In Ubuntu 20.04, python scripts executed by other users or users that cannot log in (/usr/sbin/nologin as their shell) do NOT work when importing modules that have been installed via python packages via apt or pip due to sys.path returning different values. For example, I have a PAM python script that is used for authentication, and when it is run, it fails because it cannot find some of the modules it needs. Further investigation shows that my current logged in user (running the script via the terminal) has a sys.path value of: /current/directory/user/is/in /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages When I run the same script with another user: /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload Two critical paths are missing for this user! They are: /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages Why are these two paths not included for this particular user? I don't have this problem in older versions of Ubuntu. The same python script works in 18.04, but fails in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869115] Re: python sys.path different per user account - ImportError no module named (Focal and Bionic Beaver)
** Summary changed: - python sys.path different per user account - ImportError no module named (Focal) + python sys.path different per user account - ImportError no module named (Focal and Bionic Beaver) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869115 Title: python sys.path different per user account - ImportError no module named (Focal and Bionic Beaver) Status in python2.7 package in Ubuntu: New Bug description: In Ubuntu 20.04, python scripts executed by other users or users that cannot log in (/usr/sbin/nologin as their shell) do NOT work when importing modules that have been installed via python packages via apt or pip due to sys.path returning different values. For example, I have a PAM python script that is used for authentication, and when it is run, it fails because it cannot find some of the modules it needs. Further investigation shows that my current logged in user (running the script via the terminal) has a sys.path value of: /current/directory/user/is/in /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages When I run the same script with another user: /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload Two critical paths are missing for this user! They are: /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages Why are these two paths not included for this particular user? I don't have this problem in older versions of Ubuntu. The same python script works in 18.04, but fails in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869115] Re: python sys.path different per user account - ImportError no module named (Focal)
This is now an issue in Ubuntu 18.04 as well. I'm guessing whatever broke was backported into 18.04 as well. See these scripts as examples: Version for 18.04 and 20.04: https://raw.githubusercontent.com/earnolmartin/EHCP-Force- Edition/master/ehcp/etc/pam/pam_dbauth_vsftpd_ubuntu_20_plus.py Version for 16.04: https://raw.githubusercontent.com/earnolmartin/EHCP-Force- Edition/master/ehcp/etc/pam/pam_dbauth_vsftpd.py Difference is that in 18.04 and 20.04, I must set the path in the script: sys.path.insert(0, '/usr/local/lib/python2.7/dist-packages') sys.path.insert(0, '/usr/lib/python2.7/dist-packages') If I do not, I get this error: Sep 26 19:10:41 host /etc/security/pam_dbauth_smtp.py[9965]: Traceback (most recent call last): Sep 26 19:10:41 host /etc/security/pam_dbauth_smtp.py[9965]: File "/etc/security/pam_dbauth_smtp.py", line 64, in Sep 26 19:10:41 host /etc/security/pam_dbauth_smtp.py[9965]: from passlib.hash import mysql41 Sep 26 19:10:41 host /etc/security/pam_dbauth_smtp.py[9965]: ImportError: No module named passlib.hash Sep 26 19:10:41 host saslauthd[9965]: DEBUG: auth_pam: pam_authenticate failed: Error in service module -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869115 Title: python sys.path different per user account - ImportError no module named (Focal) Status in python2.7 package in Ubuntu: New Bug description: In Ubuntu 20.04, python scripts executed by other users or users that cannot log in (/usr/sbin/nologin as their shell) do NOT work when importing modules that have been installed via python packages via apt or pip due to sys.path returning different values. For example, I have a PAM python script that is used for authentication, and when it is run, it fails because it cannot find some of the modules it needs. Further investigation shows that my current logged in user (running the script via the terminal) has a sys.path value of: /current/directory/user/is/in /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages When I run the same script with another user: /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload Two critical paths are missing for this user! They are: /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages Why are these two paths not included for this particular user? I don't have this problem in older versions of Ubuntu. The same python script works in 18.04, but fails in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869115] [NEW] python sys.path different per user account - ImportError no module named (Focal)
Public bug reported: In Ubuntu 20.04, python scripts executed by other users or users that cannot log in (/usr/sbin/nologin as their shell) do NOT work when importing modules that have been installed via python packages via apt or pip due to sys.path returning different values. For example, I have a PAM python script that is used for authentication, and when it is run, it fails because it cannot find some of the modules it needs. Further investigation shows that my current logged in user (running the script via the terminal) has a sys.path value of: /current/directory/user/is/in /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages When I run the same script with another user: /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload Two critical paths are missing for this user! They are: /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages Why are these two paths not included for this particular user? I don't have this problem in older versions of Ubuntu. The same python script works in 18.04, but fails in 20.04. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Tags: path python sys ** Summary changed: - python sys.path different per user account - no module named + python sys.path different per user account - ImportError no module named ** Summary changed: - python sys.path different per user account - ImportError no module named + python sys.path different per user account - ImportError no module named (Focal) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869115 Title: python sys.path different per user account - ImportError no module named (Focal) Status in python2.7 package in Ubuntu: New Bug description: In Ubuntu 20.04, python scripts executed by other users or users that cannot log in (/usr/sbin/nologin as their shell) do NOT work when importing modules that have been installed via python packages via apt or pip due to sys.path returning different values. For example, I have a PAM python script that is used for authentication, and when it is run, it fails because it cannot find some of the modules it needs. Further investigation shows that my current logged in user (running the script via the terminal) has a sys.path value of: /current/directory/user/is/in /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages When I run the same script with another user: /usr/lib/python2.7 /usr/lib/python2.7/plat-x86_64-linux-gnu /usr/lib/python2.7/lib-tk /usr/lib/python2.7/lib-old /usr/lib/python2.7/lib-dynload Two critical paths are missing for this user! They are: /usr/local/lib/python2.7/dist-packages /usr/lib/python2.7/dist-packages Why are these two paths not included for this particular user? I don't have this problem in older versions of Ubuntu. The same python script works in 18.04, but fails in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869117] [NEW] python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)
Public bug reported: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1869117 Title: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal) Status in python2.7 package in Ubuntu: New Bug description: apt-get install python-pip fails in Ubuntu 20.04: The following packages have unmet dependencies: python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be installed Recommends: python-all-dev (>= 2.6) but it is not going to be installed Recommends: python-wheel but it is not going to be installed E: Unable to correct problems, you have held broken packages. The python-pip package needs to be updated to accept newer versions of python-pip-whl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1869117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1263317] Re: Not working on GTK 3 undecorated windows
You can fix the resize issue by doing the following on Ubuntu 16.10: http://askubuntu.com/questions/733466/cant-resize-nautilus-window-in- gnome-flashback-using-ambiance-theme/884230#884230 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1263317 Title: Not working on GTK 3 undecorated windows Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Gnome-shell 3.10.2 Fedora 20 There appears to be no window decorations for any gtk3 windows. Nautilus, gnome control panel, gnome tweak tools etc There are no resize handles, shadows, borders, rounded corners etc This afftects Gnome-Shell 3.10 to 3.11, on both Fedora 19,&20 and Ubuntu 13.10 up I've tested the Ambiance and Radiance themes and both these aren't playing nicely. I hope this is still being maintained becuase this is my favourite gtk theme :P To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1263317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
