I've had issues with some hardware on my Lenovo X1 notebook,
particularly with Bluetooth, but when I investigated I found that there
are old reported bugs for exactly these issues on the BTS and fixes
implemented in the git repository of firmware-nonfree some time ago.
Despite this the package
On Fri, 6 Jul 2018 07:58:41 +0200
Thierry Rascle wrote:
> Hi,
>
> I'm using Debian Sid. Gimp does not seem to work any more (the user
> interface does not show up). I've tried in Xmonad and in Openbox.
>
> I have no idea what causes this. I don't see any error message.
>
> Does anyone else hav
On Fri, Jul 6, 2018, 5:57 AM Matthew Crews wrote:
> On 07/05/2018 06:03 PM, Mark Allums wrote:
> > On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote:
> >> Hey all,
> >>
> >> I'm running kernel 4.15 with nvidia-driver 390.48-3 with no
> >> problems. However, recently my kernel was automatically
Hi,
I'm using Debian Sid. Gimp does not seem to work any more (the user
interface does not show up). I've tried in Xmonad and in Openbox.
I have no idea what causes this. I don't see any error message.
Does anyone else have the same problem ?
Thanks!
Thierry
On 18-07-06 08:43:44, Zenaan Harkness wrote:
Default answer to many folks these days⦂
https://puri.sm/
I think they are in the market for a used ThinkPad.
signature.asc
Description: PGP signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 05, 2018 at 11:27:31AM -0500, David Wright wrote:
> On Thu 05 Jul 2018 at 11:11:19 (-0400), Cindy-Sue Causey wrote:
> > On 7/5/18, to...@tuxteam.de wrote:
[...]
> > >> 1. ctrl-alt-F1
> > >
> > > Note: since stretch things have... changed
On 07/05/2018 06:03 PM, Mark Allums wrote:
> On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote:
>> Hey all,
>>
>> I'm running kernel 4.15 with nvidia-driver 390.48-3 with no
>> problems. However, recently my kernel was automatically upgraded to 4.16
>> and it broke the nvidia driver.
>>
>>
Thanks for everyone's help. I looked into what deloptes and tv.debian
suggested. In the course of this I have become convinced that I am afflicted by
bug #902943 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902943 .
So I'll subscribe to the bug and see if there's any way I can help troubles
Sorry,
I failed to read your whole message. Make sure you have installed the
the kbuild and headers for your current running kernel. Then consider
upgrading your nvidia driver to the latest version (in sid, still, I
believe). If you do the latter, be sure and use the kernel parameter I
show
On 07/05/2018 06:43 PM, Zenaan Harkness wrote:
On Mon, Sep 04, 2017 at 09:11:14AM +1000, Zenaan Harkness wrote:
On Sun, Sep 03, 2017 at 12:39:18PM -0400, Dan Ritter wrote:
On Sun, Sep 03, 2017 at 03:38:17PM +0200, Jonas Hedman wrote:
Hello I hope that is not OT for this list.
Basically I'm
On 7/5/18 5:42 PM, Francisco Mariano-Neto wrote:
Hey all,
I'm running kernel 4.15 with nvidia-driver 390.48-3 with no
problems. However, recently my kernel was automatically upgraded to 4.16
and it broke the nvidia driver.
Running 'dkms autoinstall --all' does not help, it compl
On Thu 05 Jul 2018 at 14:08:21 (-0400), Greg Wooledge wrote:
> On Thu, Jul 05, 2018 at 12:57:34PM -0500, David Wright wrote:
> > On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote:
> > > On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote:
> > > > But if you're a sysadmin who has
On Thu 05 Jul 2018 at 16:29:30 (-0500), Nicholas Geovanis wrote:
> On Thu, Jul 5, 2018 at 3:46 PM Greg Wooledge wrote:
> >
> > On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote:
> > > (1) You foolishly relied on the value in /etc/debian_version when
> >
> > It is not a fucking conf
On 05/07/18 19:39, Latif Shaikh wrote:
Hi,
As Nessus scan report, they are suggested to upgrade the kernel/linux
version with *linux-image-3.16.0-4-amd64_3.**16.56-1* but this version is
not available for upgrading on your Debian portal.
Can you please help us to upgrade the linux version *3.16
You sure you have the 4.16 headers installed and not the 4.15 headers?
Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.
Original Message
On Jul 5, 2018, 15:42, Francisco Mariano-Neto wrote:
> Hey all,
>
> I'm running kernel 4.15 with nvidia-driver 39
On Mon, Sep 04, 2017 at 09:11:14AM +1000, Zenaan Harkness wrote:
> On Sun, Sep 03, 2017 at 12:39:18PM -0400, Dan Ritter wrote:
> > On Sun, Sep 03, 2017 at 03:38:17PM +0200, Jonas Hedman wrote:
> > > Hello I hope that is not OT for this list.
> > >
> > > Basically I'm on the hunt for a newish lapto
Hey all,
I'm running kernel 4.15 with nvidia-driver 390.48-3 with no
problems. However, recently my kernel was automatically upgraded to 4.16
and it broke the nvidia driver.
Running 'dkms autoinstall --all' does not help, it complains
about not finding kernel headers (which are i
On Thu, Jul 5, 2018 at 3:46 PM Greg Wooledge wrote:
>
> On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote:
> > (1) You foolishly relied on the value in /etc/debian_version when
>
> It is not a fucking configuration file that you edit.
> It is supposed to be read only.
> Only a craz
On Thu, 5 Jul 2018 10:08:05 +1000
Zenaan Harkness wrote:
> > you might want to have a look at pnmixer.
> > It works with both pulseaudio and plain alsa and should work with any
> > DE's system tray.
>
> Sounds great. By default, it simply starts, in XFCE, in the tray.
>
> The man page needs a p
On Thu, Jul 05, 2018 at 03:27:44PM -0500, Nicholas Geovanis wrote:
> (1) You foolishly relied on the value in /etc/debian_version when
It is not a fucking configuration file that you edit.
It is supposed to be read only.
Only a crazy idiot would manually edit the file that tells you what
version
On Thu, 5 Jul 2018 14:57:03 -0500
Nicholas Geovanis wrote:
> I am rightly accused of relying too heavily on /etc/debian_version to
> detect my running release. But it seems clear
> to me that the "right", canonical way to detect this is to query the
> installed package base to extract a version/r
On Thu, Jul 5, 2018 at 3:16 PM Greg Wooledge wrote:
>
> On Thu, Jul 05, 2018 at 02:57:03PM -0500, Nicholas Geovanis wrote:
> > So surely there is an
> > "approved" tool for doing that. Hopefully OTHER THAN
> > apt, aptitude, synaptic or apt-get; ideally simpler and easier to
> > script than that.
On Thu, Jul 05, 2018 at 02:57:03PM -0500, Nicholas Geovanis wrote:
> I am rightly accused of relying too heavily on /etc/debian_version to
> detect my running release. But it seems clear
> to me that the "right", canonical way to detect this is to query the
> installed package base to extract a ver
I am rightly accused of relying too heavily on /etc/debian_version to
detect my running release. But it seems clear
to me that the "right", canonical way to detect this is to query the
installed package base to extract a version/release
number from a package name and/or version. So surely there is
On Thu, 05 Jul 2018 20:02:15 +0200
Guillaume Clercin wrote:
Hello Guillaume,
>I upgrade nvidia-driver to version 390.67-2 and I can boot without
>option "slab_common.usercopy_fallback".
Thanks for all your input on this, Guillaume. If you hadn't pointed out
the workaround, I'd have been well a
On Thu, Jul 05, 2018 at 12:57:34PM -0500, David Wright wrote:
> On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote:
> > On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote:
> > > But if you're a sysadmin who has a script that wants/needs a version
> > > *number* for any reason, th
Le jeudi 5 juillet 2018, 08:25:15 CEST Ric Moore a écrit :
> On 07/04/2018 09:12 PM, Carl Fink wrote:
> > On 07/02/2018 04:49 AM, Guillaume Clercin wrote:
> >> You need to update "/etc/default/grub" and add parameter to boot with.
> >> In this
> >> file, you need to edit the line starting with GRUB
On Thu 05 Jul 2018 at 12:42:36 (-0400), Greg Wooledge wrote:
> On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote:
> > But if you're a sysadmin who has a script that wants/needs a version
> > *number* for any reason, then /etc/debian_version is the safest file
> > to modify.
>
> I strong
On Thu, Jul 05, 2018 at 11:06:22AM -0500, David Wright wrote:
> But if you're a sysadmin who has a script that wants/needs a version
> *number* for any reason, then /etc/debian_version is the safest file
> to modify.
I strongly disagree. The safest file to modify would be the broken
shell script
On 7/5/18, Dave wrote:
>
> On 7/5/18 9:18 AM, Dan Ritter wrote:
>> On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
>>> after hibernation the terminal will not wake ( apparently, no signal )
>>>
>>> the computer wakes, the keyboard lights up.
>>>
>>> I just installed deb 9.4 amd / the bios wa
On Thu 05 Jul 2018 at 11:11:19 (-0400), Cindy-Sue Causey wrote:
> On 7/5/18, to...@tuxteam.de wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Thu, Jul 05, 2018 at 09:18:38AM -0400, Dan Ritter wrote:
> >> On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
> >> >
> >> > af
On Thu 05 Jul 2018 at 11:53:45 (+0100), Joe wrote:
> On Thu, 5 Jul 2018 10:09:36 + (UTC)
> Curt wrote:
>
>
> >
> > The problem I'm looking at is that the Debian testing/unstable
> > releases do not have a version number and are not going to be
> > receiving one any time soon (the tradition
On 7/5/18, to...@tuxteam.de wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Jul 05, 2018 at 09:18:38AM -0400, Dan Ritter wrote:
>> On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
>> >
>> > after hibernation the terminal will not wake ( apparently, no signal )
>> > the co
On Thu, Jul 05, 2018 at 10:33:52AM -0400, Dave wrote:
>
>
> I cannot SSH in to this sytem.
>
> I have tried Ctrl Alt F1 or F2 does not work.
You'll need to reboot. Ctrl-Alt-Del should work.
-dsr-
On Thu 05 Jul 2018 at 12:58:21 (+1200), Richard Hector wrote:
> On 05/07/18 03:53, David Wright wrote:
> > On Wed 04 Jul 2018 at 13:18:14 (+1200), Richard Hector wrote:
> >> On 02/07/18 05:31, David Wright wrote:
> >>> On Sun 01 Jul 2018 at 22:44:17 (+1200), Richard Hector wrote:
> On 28/06/18
On 7/5/18 10:23 AM, Dan Ritter wrote:
On Thu, Jul 05, 2018 at 09:34:48AM -0400, Dave wrote:
On 7/5/18 9:18 AM, Dan Ritter wrote:
On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
after hibernation the terminal will not wake ( apparently, no signal )
the computer wakes, the keyboard lig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Jul 05, 2018 at 09:18:38AM -0400, Dan Ritter wrote:
> On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
> >
> > after hibernation the terminal will not wake ( apparently, no signal )
> >
> > the computer wakes, the keyboard lights up.
> >
On Thu, Jul 05, 2018 at 09:34:48AM -0400, Dave wrote:
>
> On 7/5/18 9:18 AM, Dan Ritter wrote:
> > On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
> > > after hibernation the terminal will not wake ( apparently, no signal )
> > >
> > > the computer wakes, the keyboard lights up.
> > >
> >
On 7/5/18 9:18 AM, Dan Ritter wrote:
On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
after hibernation the terminal will not wake ( apparently, no signal )
the computer wakes, the keyboard lights up.
I just installed deb 9.4 amd / the bios was just updated.
By terminal, do you mean mo
On Wed, Jul 04, 2018 at 07:33:12PM -0400, Dave wrote:
>
> after hibernation the terminal will not wake ( apparently, no signal )
>
> the computer wakes, the keyboard lights up.
>
> I just installed deb 9.4 amd / the bios was just updated.
By terminal, do you mean monitor?
If so:
1. ctrl-alt-F
Alex Gould wrote:
> On Wed, Jul 4, 2018, at 3:08 PM, deloptes wrote:
>> Alex Gould wrote:
>>
>> > I imagine I will need to fix some settings for initramfs, grub,
>> > crypttab, fstab, or something, but I'm not sure how to proceed.
>>
>> I would compare content of new and old initrd
>>
>> lsinit
On Wed, Jul 04, 2018 at 10:09:29AM -0500, David Wright wrote:
> On Wed 04 Jul 2018 at 09:55:54 (+0900), John Crawley wrote:
> > Sorry, but I thought a "configuration file" was supposed to
> > influence the behaviour of _software_ in some way. Are files which
> > only provide info for humans also co
On 2018-07-05, Joe wrote:
> On Thu, 5 Jul 2018 10:09:36 + (UTC)
> Curt wrote:
>
>
>>
>> The problem I'm looking at is that the Debian testing/unstable
>> releases do not have a version number and are not going to be
>> receiving one any time soon (the tradition of not according a number
>> t
On Thu, 5 Jul 2018 10:09:36 + (UTC)
Curt wrote:
>
> The problem I'm looking at is that the Debian testing/unstable
> releases do not have a version number and are not going to be
> receiving one any time soon (the tradition of not according a number
> to these two releases being of the utmo
On 2018-07-05, Richard Hector wrote:
>
> Equally, if I want to know what the time is, I can ask you.
> If you don't know, I can tell you.
> Then I can ask you, and now you'll know, and I'll find out.
>
> Right?
>
> We must be looking at different problems.
>
> I'm assuming that if you're trying to
45 matches
Mail list logo
