On Wed, Oct 21, 2015 at 05:34:32PM +0100, Luca Boccassi wrote:
> default by upstream (and by udev) with 666 permissions, so world
I hate such gys. They want more: 777. They say: "give me 777 and
everything will work. They don't need any other user than root. This
is microsoft heritage in mind. No
On 21 October 2015 at 17:15, Vladimir Stavrinov wrote:
> OK, but what happened recently with 0.6.x version? Do You want to
> say, that ordinary user always had had write access to nvidia device?
Yes. That is what we were trying to fix: device nodes are created by
default by upstream (and by udev)
On Wed, Oct 21, 2015 at 05:50:22PM +0200, Andreas Beckmann wrote:
> The driver is a non-free blob. I have no clue how it works :-)
Kicks nvidia ass. Non-free blob is always headache. Will it be
sensitive for nvida if all Linux user will boycott them not buying
their hardware?
OK, but what happen
On 2015-10-21 17:39, Vladimir Stavrinov wrote:
> explains nothing about this. There are no answer to the question:
> what for glx requires write access to video device for normal live
> user? This is something new in world fashion. Why only glx require
> this? How do other video works without such
On Tue, Oct 20, 2015 at 11:31:05PM +0100, Luca Boccassi wrote:
> Could you please make sure that both your user and your DM user (sddm I
> believe?) are in the video group and try again and report the result?
Yes, this solves the problem, but it is ridiculous.
First of all it is security issue
On Oct 21, 2015 08:54, "Miguel A. Rojas" wrote:
>
> On 10/21/2015 12:22 AM, Luca Boccassi wrote:
>>>
>>> Hi Miguel,
>>>
>>> The reason I'm asking is because I can't reproduce any problems on GDM,
>>> with any software that uses GLX or other libraries, after adding the
>>> workaround.
>>>
>>> But I
On 10/21/2015 12:22 AM, Luca Boccassi wrote:
Hi Miguel,
The reason I'm asking is because I can't reproduce any problems on GDM,
with any software that uses GLX or other libraries, after adding the
workaround.
But I noticed something looking again at the system info you forwarded,
the only user
On Tue, 2015-10-20 at 12:16 +0300, Vladimir Stavrinov wrote:
> On Mon, Oct 19, 2015 at 10:11:45PM +0100, Luca Boccassi wrote:
>
> > Maybe there's some context I'm missing. Forgive me for asking, but are
> > you sure this is due to the Nvidia driver packages or glx-alternatives?
>
> Absolutely. Th
On Tue, 2015-10-20 at 11:56 +0200, Miguel Angel Rojas wrote:
>
> I must first say that I am absolutely not familiar with KDE,
> the QT
> environment and how it works. But the thread that raises the
> abort
> doesn't look like it's in the GL libraries
>
>
> I must first say that I am absolutely not familiar with KDE, the QT
> environment and how it works. But the thread that raises the abort
> doesn't look like it's in the GL libraries code:
>
> Maybe there's some context I'm missing. Forgive me for asking, but are
> you sure this is due to the
On Mon, Oct 19, 2015 at 10:11:45PM +0100, Luca Boccassi wrote:
> Maybe there's some context I'm missing. Forgive me for asking, but are
> you sure this is due to the Nvidia driver packages or glx-alternatives?
Absolutely. This is Nvidia driver problem. Few days ago I conducted
specific experiment
On Tue, Oct 20, 2015 at 09:25:16AM +0300, Vladimir Stavrinov wrote:
> what I am doing to get it working:
>
> dpkg -P nvidia-kernel-support
> dpkg -i glx-alternative-mesa_0.5.1_amd64.deb
> glx-alternative-nvidia_0.5.1_amd64.deb glx-diversions_0.5.1_amd64.deb
> libegl1-nvidia_340.93-1_amd64.deb l
On Mon, Oct 19, 2015 at 10:05:12PM +0100, Luca Boccassi wrote:
> In your case it looks like it certainly is. Your glx alternative is
No, it is not. I never touched setup. As I wrote before more then
once, the problem arises after upgrade, not as result of setup changing.
> configured to Mesa in
On 19 October 2015 at 23:42, Andreas Beckmann wrote:
> On 2015-10-19 23:05, Luca Boccassi wrote:
>> In your case it looks like it certainly is. Your glx alternative is
>> configured to Mesa instead of Nvidia:
>>
>> diversion of /usr/lib/libGL.so to /usr/lib/mesa-diverted/libGL.so by
>> glx-divers
On Mon, 2015-10-19 at 11:38 +0200, Miguel Angel Rojas wrote:
> Hi Luca,
>
>
> Here you have the report you asked about the plasmashell. I do not
> know if it could be related to a configuration issue, but again very
> easy to reproduce. Here you have 2 reports (same error in 2
> consecutive log
On Mon, 2015-10-19 at 08:24 +0300, Vladimir Stavrinov wrote:
> On Sun, Oct 18, 2015 at 11:03:35PM +0100, Luca Boccassi wrote:
>
> > Nothing seems wrong in the setup.
>
> The problem is not about setup.
Hi Vladimir,
In your case it looks like it certainly is. Your glx alternative is
configured t
Hi Luca,
Here you have the report you asked about the plasmashell. I do not know if
it could be related to a configuration issue, but again very easy to
reproduce. Here you have 2 reports (same error in 2 consecutive log on
sessions).
These crashes are related to the plasmashell (I manually fixe
On Sun, Oct 18, 2015 at 11:03:35PM +0100, Luca Boccassi wrote:
> Nothing seems wrong in the setup.
The problem is not about setup.
> What is the exact error you get with plasma?
The problem is not about "exact error".
The problem is about GLX, that doesn't works with any software.
Errors may b
On Sun, Oct 18, 2015 at 08:43:50PM +0100, Luca Boccassi wrote:
> Could you please attach the output of:
>
> reportbug --template glx-alternative-nvidia
> reportbug --template nvidia-driver
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (includ
On 18 October 2015 at 22:23, Miguel Angel Rojas wrote:
> Hi Luca,
>
> Thanks for the quick answer!
>
> Here you have both report you asked for. Hopefully it will help us to know
> where the issue is.
Nothing seems wrong in the setup.
What is the exact error you get with plasma?
Kind regards,
Lu
Hi Luca,
Thanks for the quick answer!
Here you have both report you asked for. Hopefully it will help us to know
where the issue is.
Regards
On Sun, Oct 18, 2015 at 9:43 PM, Luca Boccassi
wrote:
> On Sun, 2015-10-18 at 20:16 +0200, Miguel Angel Rojas wrote:
> > Hi all,
> >
> >
> > Vladimir is
On Sun, 2015-10-18 at 20:16 +0200, Miguel Angel Rojas wrote:
> Hi all,
>
>
> Vladimir is right, same issue here. Indeed, It is weird to me not so
> many people is currently reporting on it, but it is affecting a lot of
> programs. Something happens when upgrading to version 0.6.x (I agree
> at th
On Sun, Oct 18, 2015 at 08:16:39PM +0200, Miguel Angel Rojas wrote:
>Vladimir is right, same issue here. Indeed, It is weird to me not so
>many people is currently reporting on it, but it is affecting a lot of
And even more weird is practice to close an issue without
confirmation from use
Hi all,
Vladimir is right, same issue here. Indeed, It is weird to me not so many
people is currently reporting on it, but it is affecting a lot of programs.
Something happens when upgrading to version 0.6.x (I agree at this point)
plasma-desktop is also unable to start and panic (black screen).I
24 matches
Mail list logo
