--
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/1031376
Title:
Unity/LightDM session crashes - login screen appears
Status in “lightdm” package in Ubuntu:
New
Bug description:
Public bug reported:
Almost each time I login to Unity using LightDM after some time (from 5
min to about 2-3 hours) my session crashes and I am taken to the login
lightdm screen again. It does not matter what applications are running -
sometimes I get it when I have only the browser running,
After it happened again I was able to observe that the process which
exited was /usr/bin/X.
--
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/1031376
Title:
Unity/LightDM session
The fix has been pulled in by the upstream:
https://git.gnome.org/browse/gtk+/commit/?id=15dbadf38992aa09364f0dd06a71a51b99b6e800
And the upstream bug (https://bugzilla.gnome.org/show_bug.cgi?id=73)
has been marked as resolved fixed.
--
You received this bug notification because you are a
/linux-mst.
I will appreciate any feedback.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: (unassigned) = Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu
Vincent, what you could do is to take a look at this instruction:
https://01.org/linuxgraphics/node/358
Based on this you could:
sudo add-apt-repository ppa:dgadomski/linux-mst
sudo add-apt-repository ppa:xorg-edgers/ppa
sudo apt-get update
sudo apt-get install linux-image-3.16.0-19-generic #
Thanks Vincent.
Would you mind giving the patched kernel from ppa:dgadomski/linux-mst a
try? That would allow us to confirm whether the cherry-pick works for
the trusty backport of utopic kernel.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which
Thanks for giving that a try Vincent. I believe that the intel driver
needs to be reinstalled for this to work.
Regarding the source code:
Please not that if you uncomment the following line in your
/etc/apt/sources.list.d/dgadomski-linux-mst-trusty.list file
# deb-src
** Tags added: cts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.2 MST support is missing in the Intel driver
Status in
** Tags added: cts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/445333
Title:
remember password on printing to windows printers does not work
Status in GTK+ GUI Toolkit:
Fix
Vincent, I missed the setup you use in one of your comments. The kernels
that I have prepared add only one feature: the Multi Stream Transport
(MST) feature of the displayport 1.2, nothing else.
So basically for this to work you need a displayport 1.2 capable device
and a displayport 1.2 monitors
Hi Vincent,
If I understand correctly your docking station performs the role of a dp
mst hub (can you please confirm this with the documentation of your
docking station or provide its model to verify this online?), so it
should be a good setup to test.
Ideally to make this working you would need
Hi Elvis,
Looks like you have the perfect setup to test this case.
Please make sure you have ppa-purge installed so you can revert the
package updates if anything goes wrong.
Please follow these steps:
1. sudo add-apt-repository -y ppa:dgadomski/linux-mst
2. sudo add-apt-repository -y
VIncent, according to [1] this hardware is displayport 1.2 compatible.
Plus, the Display Port 1.2 adds the ability to daisy chain displays (4
displays via 1 connector).
However, I have not been able to determine whether this works in such a
way that it takes MST output from your laptop's
Hi Elvis, unfortunately I do not know that. Please consult your user's
manual. I haven't got access to those monitors. Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Thank you guys for testing this. Unfortunately I do not know the cause
with the wireless network problems. I was doing sanity tests of those
kernels on my trusty desktop (with a USB WiFi dongle) and my utopic
laptop (with built-in wifi). In both cases I was able to use my network.
This kernel is
Thanks Vincent. This confirm that probably what I have backported is not
enough to have full MST support. I will try to prepare an updated build
after reviewing David Airlie tree.
I will work on providing an update next week.
Thank you all for testing.
--
You received this bug notification
Hello Elvis,
I have came across something that may interest you, here [1]. The Dell
support person there states that you should have the DSP 1.2 enabled
only on the primary monitor, on the secondary it should be disabled.
[1] http://en.community.dell.com/support-
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: (unassigned) = Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Hello Robert,
Thank you for working on this issue. I want you to know that we have a
customer waiting for a fix to this bug.
Please let me know if I could provide you help in development and/or
testing.
Regards,
Dariusz
--
You received this bug notification because you are a member of Desktop
SRU proposal for utopic (gtk+2.0)
** Description changed:
- i am printing from my ubuntu karmic to a windows box. everytime i print
- i get asked to input username and password to windows box, then the
- document gets printed. there is a remember password checkbox, but it
- keeps asking me when
SRU proposal for utopic (gtk+3.0)
** Patch added: gtk+3.0_3.12.2-0ubuntu8.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4214816/+files/gtk%2B3.0_3.12.2-0ubuntu8.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Dariusz Gadomski (dgadomski) = (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
While I was working on a packport of this feature I have discovered a
bug in the gtk printing backends (affects series 2 and 3) that may cause
random crashes due to buffer overflow.
I have reported the issue upstream and am working on backports to utopic
and trusty (gtk2 and gtk3).
SRU proposal for Utopic
(https://bugzilla.gnome.org/show_bug.cgi?id=73)
** Patch added: utopic_gtk+3.0_3.12.2-0ubuntu11.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4222403/+files/utopic_gtk%2B3.0_3.12.2-0ubuntu11.debdiff
--
You received this bug
SRU proposal for utopic
Contains the feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: utopic_gtk+2.0_2.24.24-0ubuntu2.debdiff
SRU proposal for trusty.
Contains feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: trusty_gtk+2.0_2.24.23-0ubuntu1.2.debdiff
SRU proposal for trusty.
Contains feature backport along with a fix for
https://bugzilla.gnome.org/show_bug.cgi?id=73.
** Patch added: trusty_gtk+3.0_3.10.8-0ubuntu1.3.debdiff
Krzysztof, looks like you installed the kernel correctly, you are simply
booting into a newer kernel without the feature.
Please make sure you boot using 3.13.0-39.
To do so please choose kernel 3.13.0-39 from the GRUB menu during the
boot of your computer.
You can find more information how do
Krzysztof, you should be using 3.13.0-39 patched by me (the newer
version is the vanilla Ubuntu kernel which does not support MST).
Regarding your question about cables: you should not worry about that.
According to [1]:
Despite what you may read, there is no such thing as a
DisplayPort 1.1
Sorry Krzysztof, this bug is dedicated only to supporting Intel VGAs, so
none of the packages here would solve your problem.
Since you use the proprietary AMD drivers you should examine the
features their driver support and follow their instructions.
Sorry, I have missed the AMD VGA part in the
Krzysztof, you don't have to downgrade the kernel. This is only
necessary with the open-source Intel drivers.
I'm not sure if AMD drivers support Displayport 1.2 MST feature, but I
know that NVIDIA drivers do support it and it does not require anything
special about the kernel.
Please browse
Ben, are you able to compare this behaviour with the 3.17 kernel (e.g.
from debs available at [1])?
If the behavior is consistent between the two kernel version - it's another
issue.
If 3.17 behaves better than the 3.16 you were using - this is the right place
to handle the problem.
[1]
@Ben: if you were using an official Utopic 3.16.0-28-generic kernel,
please note that it does NOT contain support for multiple displays using
MST, so it will not be possible to have non-mirroring displays.
If it is not from the official Utopic repository, please share the
origin of this kernel.
Ben, I have updated the kernel version in my ppa. Could you please test
version 3.16.0-28.37hf73386v20141212b2 and compare the supsend/resume
behavior with what you observer using 3.17?
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi guys, there is an updated kernel version in my ppa (should become available
any minute):
* trusty: 3.16.0-23.31~14.04.2hf73386v20141028b1
* utopic: 3.16.0-23.31hf73386v20141028b1
I would really appreciate giving any of those a try. The procedure
should be as previously:
1. install the
Thanks Mike. If your docking station is the same as Elvis mentioned
above then this feature should (eventually) make it working.
Can you please double-check:
$ apt-cache policy linux-image-3.16.0-23-generic
whether the installed version you use is:
Installed:
Thanks Matthew.
All the changes from David's backport for 3.16 branch has been cherry
picked to the kernel in my ppa, so I would appreciate any feedback from
using a build from his sources.
If it works with his version then something in Ubuntu kernel may be
blocking this feature.
If anyone is
Elvis, thank you for checking this. I assume that the multi-display
configuration did not work for you as well as the network?
Have you tried running utopic kernel backport on trusty before? Maybe just this
backport does not work.
Does anybody (with the hardware) have utopic (14.10)
Matthew, can you please confirm that you don't have 'mirroring'
parameter anywhere on the kernel commandline?
# grep mirror /proc/cmdline
Can you please also post output of:
# find /sys/kernel/debug -name i915_dp_mst_info -exec cat {} \;
Thanks!
--
You received this bug notification because
aexl, as long as the docking station uses your intel card via a
displayport 1.2 then this may be the case.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Thanks Matthew!
I will review the changes to trusty and try to backport this feature to
3.13 (to avoid network problems).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Wouter, I would appreciate anyone with a suitable hardware to stay with
trusty for a couple of days more until we have a working solution.
But if you need the MST feature please move to utopic and give a try the
same build Matthew found working.
There is a new 3.13 build for trusty ongoing in my
That's a good point Matthew. I should have been more clear about it.
Thank you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.2 MST
Hello everyone,
The last build was successful so there is a trusty kernel
(3.13.0-39.66hf73386v20141030b1) to be tested in my ppa.
I will appreciate your feedback.
Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Matthew, did you make any investigation why it was not working for you
on your first laptop?
Please share any observation that may help other people here.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel
Thank you Elvis.
Can you please post your output of:
# find /sys/kernel/debug -name i915_dp_mst_info -exec cat {} \;
Have you tried installing the linux-image-extra package for the kernel
you previously tested (3.0.16 - the one that left you without a
network)? If not, I would appreciate
What I was referring above was the output of:
# find /sys/kernel/debug -name i915_dp_mst_info -exec cat {} \;
on my system.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Thank you for the information Matthew.
I didn't notice that because for me without the necessary hardware those
files are empty all the time.
Elvis, did you get any results after installing linux-image-extra?
Thanks!
--
You received this bug notification because you are a member of Desktop
Hello Elvis,
Was it any different for you with the 3.13 kernel?
Thanks,
Dariusz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.2 MST
** Description changed:
+ SRU Justification:
+
+ Impact: Many users expect the possibility to use the DP1.2 MST feature which
+ enables them to use a number of different display setups: daisy-chaining
+ DP1.2 displays, some 4K displays appearing as 2 separate displays, 3D
displays.
+ This
** Tags added: cts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1386170
Title:
Libreoffice startup center shorcut broken
Status in “libreoffice” package in Ubuntu:
Confirmed
Hi Vincent,
There is a 3.13.0-39.66hf73386v20141030b1 version available for trusty. You
should be able to install it with:
sudo add-apt-repository ppa:dgadomski/linux-mst
sudo apt-get update
sudo apt-get install linux-image-3.13.0-39-generic
linux-image-extra-3.13.0-39-generic
And
apt-cache
Here are my observations after looking into this issue:
* Using the version 4.3 available in the ppa the symlinks are created correctly
(they point to correct launchers in /usr/share/applications)
* However, for Unity to launch them from the desktop they are required to be
executable (which is
Things look a little different when using gnome fallback session:
1. For applications that have shortcuts in /usr/share/applications
drag'n'dropping creates a *copy* of the launcher on the desktop. The copy has a
default access rights of 755 which allow execution.
2. For
This fixes the issue for utopic.
Bjoern: would debdiffs for trusty and precise be of any use to you? Or
will the backporting be done in another way?
** Patch added: utopic_libreoffice_4.3.3-0ubuntu2.debdiff
** Patch removed: utopic_libreoffice_4.3.3-0ubuntu2.debdiff
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1386170/+attachment/4260582/+files/utopic_libreoffice_4.3.3-0ubuntu2.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is
Sorry about the previous patch Björn.
Please find a fixed version for Utopic attached.
** Patch added: utopic_libreoffice_4.3.3-0ubuntu2.debdiff
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1386170/+attachment/4262868/+files/utopic_libreoffice_4.3.3-0ubuntu2.debdiff
--
You
Thank you Ben, I will review your logs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1104230
Title:
DisplayPort 1.2 MST support is missing in the Intel driver
Thank you Björn, I will ask the user to give it a try.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1386170
Title:
Libreoffice startup center shorcut broken
Status in
SRU proposal for utopic (gtk2)
** Patch removed: utopic_gtk+2.0_2.24.24-0ubuntu2.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4222404/+files/utopic_gtk%2B2.0_2.24.24-0ubuntu2.debdiff
** Patch removed: trusty_gtk+2.0_2.24.23-0ubuntu1.2.debdiff
Sebastien, please find the attached debdiffs with the
gtk_print_backend_set_password version bumped.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/445333
Title:
remember
SRU proposal for trusty (gtk3).
** Patch added: trusty_gtk+3.0_3.10.8-0ubuntu1.3.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4265155/+files/trusty_gtk%2B3.0_3.10.8-0ubuntu1.3.debdiff
--
You received this bug notification because you are a member of
SRU proposal for trusty (gtk2).
** Patch added: trusty_gtk+2.0_2.24.23-0ubuntu1.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4265156/+files/trusty_gtk%2B2.0_2.24.23-0ubuntu1.2.debdiff
--
You received this bug notification because you are a member of
Sebastien, I have prepared a debdiff for gtk2 vivid. I hope it will be
of any use for you. Thanks!
** Patch added: vivid_gtk+2.0_2.24.25-0ubuntu2.debdiff
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4266693/+files/vivid_gtk%2B2.0_2.24.25-0ubuntu2.debdiff
--
You
Hi Ben,
I have uploaded new kernel build (version:
3.16.0-26.34hf73386v20141126b1). Could you please give it a try?
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Ben, according to your logs:
[ 11.322] Current Operating System: Linux dib 3.16.0-25-generic
#33hf73386v20141106b1-Ubuntu SMP Thu Nov 6 14:20:03 UTC 2014 x86_64
you have used the previous kernel again. Maybe you made your attempt
right before the packages were published in my ppa.
Looks like
I'm glad it works for you Ben.
To everyone: if we want to get this to the Ubuntu kernel we need more
feedback from people testing this.
Please give the Utopic kernel (3.16.0-26.34hf73386v20141126b1) a try and
leave a comment here. This is a big feature and it would help us to have
it tested.
Elvis, no, sorry, not yet. I was focusing on Utopic as it is the first
step to get it accepted to Ubuntu.
What worries me is that the current build for trusty 3.13 worked for
Wouter (comment #78) and does not work for you. That makes me wonder if
your configuration is even supported by this
Elvis, the only thing I was able to do for you right now is to build you
an Utopic kernel for Trusty (the same that was working for Ben).
Please find it in my ppa. The version number is
3.16.0-26.34~14.04.1hf73386v20141127b1.
Please remember to use also the extras package.
--
You received this
@Björn: my tests show that it fixes the issue, however I still did not
get any feedback from the reporter.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1386170
Title:
The upstream gtk is considering backporting this change to gtk2: [1]
What I find most important in the description is:
With regards to the importance of having this only fixed in GTK 3. To be
honest, as long as firefox still uses GTK 2 in most distributions this fix is
more important for our
Ben, could you paste the output of:
$ apt-cache policy linux-image-$(uname -r)
We need to be sure that you are using the patched version of the kernel
and not the standard Ubuntu kernel.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is
Ben, unfortunately this is the default Ubuntu kernel without this
feature.
You need to use version 3.16.0-28.37hf73386v20141212b2 to be able to
benefit from it.
Do install this version you should do:
sudo apt-get install
linux-image-3.16.0-28-generic=3.16.0-28.37hf73386v20141212b2
and then
Hey Bjoern. Please treat this as fixed, there was no feedback from the
users so most probably it was working for them as it was for me in my
tests.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Hey Björn. Please treat this as fixed, there was no feedback from the
users so most probably it was working for them as it was for me in my
tests.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Public bug reported:
1) Release: affects Trusty and Utopic (at least)
2) Affected version: 0.9.8.8-0ubuntu7
Steps to reproduce:
1. Logout to the lightdm greeter.
2. Using the network manager applet try to connect to a new network (not
connected before).
Expected result:
New network connection
The current status of this bug is as follows:
- The current xorg stack with intel drivers from ppa:xorg-edgers/ppa is not
compatible with the kernel part backported to 3.13 and 3.16
- This feature seems to work seamlessly on my test hardware with Vivid
- It seems that the best solution will be to
** Tags added: sts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1421259
Title:
Can't add new WiFi network from lightdm greeter
Status in network-manager-applet
Public bug reported:
While accessing samba shares mounted with GVFS (using nautilus, but that
probably does not matted) ACL rules are not respected.
Those shares should be mounted using user_xattr,acl options and by
default they aren't.
Ideally the problem would be solved by a way to append
** Description changed:
+ [Impact]
+
+ * It's impossible to use ACL-configured smb shares via gvfs (e.g.
+ nautilus) as it logs in as an anonymous user by default.
+
+ [Test Case]
+
+ 1. LDAP authentication for client server.
+ 2. SMB server with a share accessible to a certain ACL group or
) = Dariusz Gadomski (dgadomski)
** No longer affects: samba
** Patch added: trusty-gvfs_1.20.3-0ubuntu1.2.debdiff
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1464645/+attachment/4439595/+files/trusty-gvfs_1.20.3-0ubuntu1.2.debdiff
--
You received this bug notification because you
** Bug watch added: Debian Bug tracker #781007
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781007
** Also affects: network-manager (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781007
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Bug watch added: Samba Bugzilla #11407
https://bugzilla.samba.org/show_bug.cgi?id=11407
** Project changed: gvfs = samba
** Changed in: samba
Importance: Medium = Unknown
** Changed in: samba
Remote watch: GNOME Bug Tracker #752067 = Samba Bugzilla #11407
--
You received this bug
** Bug watch added: GNOME Bug Tracker #752067
https://bugzilla.gnome.org/show_bug.cgi?id=752067
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=752067
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
** Bug watch added: GNOME Bug Tracker #752481
https://bugzilla.gnome.org/show_bug.cgi?id=752481
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=752481
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Description changed:
- While accessing samba shares mounted with GVFS (using nautilus, but that
- probably does not matted) ACL rules are not respected.
+ Looks like the SMB backend does not support ACL rules while accessing
+ remote shares.
- Those shares should be mounted using
** Description changed:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela Authentication Services by Dell) in
a disconnected mode (using cached authentication).
Steps to reproduce:
1. Configure pam_vas client authenticating to a
Public bug reported:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela Authentication Services by Dell) in
a disconnected mode (using cached authentication).
Steps to reproduce:
1. Configure pam_vas client authenticating to a remote server.
2.
** Changed in: policykit-1 (Ubuntu)
Assignee: (unassigned) => Dariusz Gadomski (dgadomski)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Title:
PolkitAgentSess
** Bug watch added: freedesktop.org Bugzilla #92886
https://bugs.freedesktop.org/show_bug.cgi?id=92886
** Also affects: policykit-1 via
https://bugs.freedesktop.org/show_bug.cgi?id=92886
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Summary changed:
- PolkitAgentSession ignores multiline output (with pam_vas)
+ PolkitAgentSession incorrectly handles multiline output (with pam_vas)
** Description changed:
There is an error observed when Ubuntu is configured to perform
authentication via pam_vas (Vintela
Miroslav, thanks for taking a look.
Sure, I can improve the patch. I'll attach the new version as soon as
it's done.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Title:
Created attachment 119643
Refactoring to use send_to_helper
I have refactored the code to make use of send_to_helper instead of
duplicating the code.
I've chosen to apply it on top of the previous change to keep 2
different actions (escaping PAM_TEXT_INFO and refactoring) on the same
step.
I
Typo, what I've meant in the above comment is that I wanted to avoid
doing 2 different actions in the same commit.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1510824
Title:
I have been playing with copying some limit values from
/etc/dbus-1/session.conf to system.conf and by bisection I found out that
adding the following settings:
limit name=max_replies_per_connection5/limit
makes the problem disappear.
--
You received this bug notification because you are a
Public bug reported:
If a large number of networks is configured it may be impossible to
connect to some of them as a regular user, because they are not listed.
It affects all the versions I tested: trusty, utopic, vivid and wily.
Steps to reproduce:
1. Configure a large number of networks (in
I have debugged the network-manager daemon (src/settings/nm-
settings.c:234 impl_settings_list_connections) and nmcli
(cli/src/connections.c:8633 get_connections_cb).
It looks that a correct number of connections is sent from the daemon
and a limited number is received in the nmcli. Maybe it's
After updating the client machine with the -proposed version of gvfs the
problem is fixed. Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
** Tags added: sts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
I have prepared a 'broken' pam_unix version printing a multiline text info if
it detects the PAM_SERVICE name is polkit-1.
This allows to reproduce the issue and verify the fix.
I've made this broken version available for Vivid and Wily in
ppa:dgadomski/lp1510824 and performed the verification
1 - 100 of 310 matches
Mail list logo
