Re: Finding image file underlying an icon on Mate desktop

[Frank M]

On 03/14/2018 06:30 PM, Liam O'Toole wrote:

On 2018-03-14, Richard Owlett  wrote:

Several months ago I needed a fully custom desktop icon for a shortcut.
I had no trouble creating an appropriate png file and having it display.
Now I need a similar icon. I went to the properties of the shortcut
expecting to be able to discover the location of the image used.

I could not. Clicking on the icon's image allows replacing it but no
apparent way to discover its location.

Is there a way?
[for current application creating a new icon will be simple]
[finding the old icon would be convenient]

TIA


Examine the .desktop file in your ~/Desktop directory. Look for a line
beginning with "Icon".




   Most of them just have the name of the icon with no path.

   Why doesn't the OP just do a locate  ?

Re: minissdpd failure in update

[Frank M]

On 02/01/2018 03:57 PM, Sven Hartge wrote:

Sven Joachim <svenj...@gmx.de> wrote:

On 2018-02-01 19:55 +0100, Sven Hartge wrote:

Frank M <debianl...@videotron.ca> wrote:

Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN
network interface by name instead of IPv4 address : 0.0.0.0
Feb 01 13:39:07 franklin minissdpd[9152]: can't parse "0.0.0.0" as a
valid address or interface name

Your configuration is broken/wrong. You need to edit
/etc/default/minissdpd and put the correct IP or device name into the
variable "MiniSSDPd_INTERFACE_ADDRESS".

There is no /etc/default/minissdpd in the package anymore.

No?

See:

# dpkg -L minissdpd | grep "/etc/default/minissdpd"
/etc/default/minissdpd

# dpkg -l minissdpd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture   Description
+++-===-==-==-===
ii  minissdpd:amd64 1.5.20161216-1 amd64  keep memory of all UPnP 
devices that announ


See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889028.

Interesting.

Also the /lib/systemd/system/minissdpd.service requires
/etc/default/minissdpd because this file is not marked as optional.

So the file must exist or the unit itself would fail.

Which it will when installed on a system where it has never been
installed before:

,
| Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed to load 
environment files: No such file or directory
| Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed to run 'start' 
task: No such file or directory
| Feb 01 21:51:37 HOST systemd[1]: minissdpd.service: Failed with result 
'resources'.
| Feb 01 21:51:37 HOST systemd[1]: Failed to start keep memory of all UPnP 
devices that announced themselves.
`

But if installed on a system where the older version was installed,
/etc/default/minissdpd still exists:

,
| # MiniSSDPd default configuration
|
| # Set this to 1 if you want to start the daemon
| START_DAEMON=1
|
| # Set this to the IP of the interface you want the demon to run on
| MiniSSDPd_INTERFACE_ADDRESS=0.0.0.0
`

Note the wrong "MiniSSDPd_INTERFACE_ADDRESS". Version
1.2.20130907-4.1 doesn't seem to mind the "0.0.0.0" here and starts
without problems.

Only after upgrading to 1.5.20161216-1 it barfs and fails.

There are really two errors at play here, depending on from where you
come:

a) 1.2.20130907-4.1 was upgraded to 1.5.20161216-1:
Error because 0.0.0.0 is no longer correct.

b) 1.5.20161216-1 is the first version
unit fails, because /etc/default/minissdpd does not exist.

Solution in all cases is: Create a correct /etc/default/minissdpd.

Grüße,
Sven.




  How about aptitude purge minissdpd.

That's how I fixed it.

It only got installed as a recommend of transmission-gtk.

minissdpd failure in update

[Frank M]

Updating my Sid installation this morning.


Setting up minissdpd (1.5.20161216-1) ...
Installing new version of config file /etc/init.d/minissdpd ...
Job for minissdpd.service failed because the control process exited with 
error code.

See "systemctl status minissdpd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript minissdpd, action "restart" failed.
● minissdpd.service - keep memory of all UPnP devices that announced 
themselves
   Loaded: loaded (/lib/systemd/system/minissdpd.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Thu 2018-02-01 13:39:07 
EST; 13ms ago

 Docs: man:minissdpd(1)
  Process: 9152 ExecStart=/usr/sbin/minissdpd -i 
$MiniSSDPd_INTERFACE_ADDRESS $MiniSSDPd_OTHER_OPTIONS (code=exited, 
status=1/FAILURE)

 Main PID: 814 (code=exited, status=0/SUCCESS)

Feb 01 13:39:07 franklin minissdpd[9152]: Error: please specify LAN 
network interface by name instead of IPv4 address : 0.0.0.0
Feb 01 13:39:07 franklin minissdpd[9152]: can't parse "0.0.0.0" as a 
valid address or interface name
Feb 01 13:39:07 franklin minissdpd[9152]: Usage: /usr/sbin/minissdpd 
[-d] [-6] [-s socket] [-p pidfile] [-t TTL] [-f device] -i  
[-i ] ...
Feb 01 13:39:07 franklin minissdpd[9152]:    is either an 
IPv4 address with mask such as
Feb 01 13:39:07 franklin minissdpd[9152]: 192.168.1.42/255.255.255.0, or 
an interface name such as eth0.
Feb 01 13:39:07 franklin minissdpd[9152]:   By default, socket will be 
open as /var/run/minissdpd.sock
Feb 01 13:39:07 franklin minissdpd[9152]:   and pid written to file 
/var/run/minissdpd.pid
Feb 01 13:39:07 franklin systemd[1]: minissdpd.service: Control process 
exited, code=exited status=1
Feb 01 13:39:07 franklin systemd[1]: minissdpd.service: Failed with 
result 'exit-code'.
Feb 01 13:39:07 franklin systemd[1]: Failed to start keep memory of all 
UPnP devices that announced themselves.

dpkg: error processing package minissdpd (--configure):
 installed minissdpd package post-installation script subprocess 
returned error exit status 1

Processing triggers for mime-support (3.60) ...

What went wrong ??

Re: Update warning.

[Frank M]

On 01/23/2018 05:31 PM, Richard Hector wrote:

On 24/01/18 11:08, Frank M wrote:

Just a warning for Debian Sid users - this one caught me today and

now a bunch of necessary things ( mostly systemd related ) won't run and

things like apt . aptitude, dpkg, etc are useless.


I don't know at this point how I am going to repair this system. Had to

boot Mint Mate to send this.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888180

Looks like symlinking /bin/sh to /bin/bash (or maybe /usr/bin/dash?)
instead of /bin/dash might get you going?

Richard




Well after looking again at the bug report, I copied DASH from /usr/bin 
to /bin and
that did it. It's just a temporary fix, but it got the system going for 
now. A repackaged

DASH is apparently on the way.
I'll undo my fix after the new package gets installed.

Update warning.

[Frank M]

Just a warning for Debian Sid users - this one caught me today and

now a bunch of necessary things ( mostly systemd related ) won't run and

things like apt . aptitude, dpkg, etc are useless.


I don't know at this point how I am going to repair this system. Had to

boot Mint Mate to send this.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888180

Re: pavucontrol fails to start

[Frank M]

On 06/26/2017 04:29 PM, Thomas George wrote:

The command pavucontrol returns an error message:

error while loading shared libraries: libgtkmm-3.0.so-1: cannot open 
object file: No such file or directory.


Where can I find this missing file?

I checked apt-get install libgtkmm-3.0-1 The response was latest 
version installed.


I tried apt-cache search libgtkmm-3.0.so.1 Nothing was found.




   This is available for 64 bit. libgtkmm-3.0-1v5
   sudo apt install libgtkmm-3.0-1v5

Re: switching flavors

[Frank M]

On 06/04/2017 01:44 PM, Joe wrote:

On Sun, 4 Jun 2017 12:20:51 -0400
SDA  wrote:


On Sun, Jun 04, 2017 at 04:20:02PM +1000, Davor Balder wrote:

Yes - and based on some work I did earlier in the week if you keep
the things simple I would say your upgrade should be uneventful.

I  changed the repo to unstable

Then I did:

apt-get update

apt-get upgrade

That was it.

Nope, not done yet. You still need to do a full upgrade. In apt it's
'apt full-upgrade' in aptitude it's 'aptitude dist-upgrade'. Not sure
what the eqivalent command is in apt-get.


Other way around, aptitude is safe-upgrade and full-upgrade, it's
apt-get which has upgrade and dist-upgrade. apt mixes the two, with
upgrade and full-upgrade.



Did an apt full-upgrade. Now running Sid. No problems.
Thanks guys.

Re: switching flavors

[Frank M]

On 06/04/2017 02:20 AM, Davor Balder wrote:

Yes - and based on some work I did earlier in the week if you keep the
things simple I would say your upgrade should be uneventful.

I  changed the repo to unstable

Then I did:

apt-get update

apt-get upgrade

That was it.


Cheers


D

On 04/06/17 13:11, Gary Dale wrote:

On 03/06/17 08:59 PM, Frank M wrote:

I am running Debian Stretch, and like to change to Sid.

Can I just change my sources.list to unstable and upgrade?

I have run Sid before and am prepared to deal with some breakage

Yes, although I'd do a dist-upgrade (or full-upgrade if using aptitude).

Based on some earlier problems with Stretch and the discussions around
it, I'm not sure that sid is necessarily less stable. Apparently they
dump stuff into Stretch without anyone actually checking to see that
it can work with other Stretch libraries.





Great. Thanks very much. We'll see how it goes.

Re: switching flavors

[Frank M]

On 06/03/2017 11:11 PM, Gary Dale wrote:

On 03/06/17 08:59 PM, Frank M wrote:

I am running Debian Stretch, and like to change to Sid.

Can I just change my sources.list to unstable and upgrade?

I have run Sid before and am prepared to deal with some breakage


Yes, although I'd do a dist-upgrade (or full-upgrade if using aptitude).

Based on some earlier problems with Stretch and the discussions around 
it, I'm not sure that sid is necessarily less stable. Apparently they 
dump stuff into Stretch without anyone actually checking to see that 
it can work with other Stretch libraries.




Thanks Gary. Will do later today.

switching flavors

[Frank M]

I am running Debian Stretch, and like to change to Sid.

Can I just change my sources.list to unstable and upgrade?

I have run Sid before and am prepared to deal with some breakage.

Re: bugs in reportbug ?

[Frank M]

On 30/01/17 12:59 AM, Andreas Ronnquist wrote:

On Mon, 30 Jan 2017 00:37:42 -0500,
Frank M<debianl...@videotron.ca> wrote:


Tried to file a bug today using reportbug but it crashed:


Traceback (most recent call last):
   File "/usr/bin/reportbug", line 2233, in 
 main()
   File "/usr/bin/reportbug", line 1084, in main
 if newui.initialize():
   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line
1580, in initialize gi.require_version('Vte', '2.91')
   File "/usr/lib/python3/dist-packages/gi/__init__.py", line 118, in
require_version raise ValueError('Namespace %s not available' %
namespace)
ValueError: Namespace Vte not available

Does this look familiar to anyone ?

I am running 64 bit stretch and reportbug is the latest version.


See #851968 [1] - you will need to install the packages gir1.2-vte-2.91
and python3-gi-cairo for the GTK+ interface to work.

1 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851968

-- Andreas Rönnquist
mailingli...@gusnan.se
gus...@openmailbox.org

  That solved it. I had python3-gi-cairo but was missing the second 
package.


  Thank you.

bugs in reportbug ?

[Frank M]

Tried to file a bug today using reportbug but it crashed:


Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2233, in 
main()
  File "/usr/bin/reportbug", line 1084, in main
if newui.initialize():
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 
1580, in initialize

gi.require_version('Vte', '2.91')
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 118, in 
require_version

raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Vte not available

Does this look familiar to anyone ?

I am running 64 bit stretch and reportbug is the latest version.

Re: missing firmware ??

[Frank M]

On 28/01/17 07:49 PM, Felix Miata wrote:

Jimmy Johnson composed on 2017-01-28 16:21 (UTC-0800):


Frank M wrote:


   I installed firmware-linuxit pulled in several packages 
including

one I need (intel-microcode)  but I still
get :
Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for
module i915
Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for
module i915
when init is updated.



Do you have 'xserver-xorg-video-intel' installed?  If not install it and
see if your missing firmware goes away.


xserver-xorg-video-intel might actually be a problem. If installed, 
Xorg uses it if you don't explicitly override. It's no longer the 
driver of choice for most Intel gfxchips. If you're not using an 
antique Intel gfxchip, you probably prefer the modesetting driver that 
is integral to the server:


http://www.phoronix.com/scan.php?page=news_item=Fedora-Xorg-Intel-DDX-Switch 

http://www.phoronix.com/scan.php?page=article=intel-modesetting-2017=1 

http://www.phoronix.com/scan.php?page=news_item=Ubuntu-Debian-Abandon-Intel-DDX 



Modesetting was causing me problemsthe image viewer feh was 
segfaulting so I had to

create an xorg.conf file to go back to the old way.
I was going to report a bug on xserver-xorg ( as the docs suggest) but 
report bug on
my machine won't run because of python problems and I haven't found the 
time to

figure out reporting bug via email.

Re: missing firmware ??

[Frank M]

On 28/01/17 07:21 PM, Jimmy Johnson wrote:

On 01/28/2017 02:00 PM, Frank M wrote:

On 28/01/17 04:17 PM, Jimmy Johnson wrote:


On 01/28/2017 09:58 AM, Frank M wrote:

On 28/01/17 12:55 PM, Frank M wrote:




On 28/01/17 12:52 PM, Joe wrote:

On Sat, 28 Jan 2017 12:20:00 -0500
Frank M <debianl...@videotron.ca> wrote:


Updating my Stretch installation today I first noticed this:

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_26.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6_1.bin
for module i915


A search using apt-file didn't turn up any packages.


What am I missing here ?



https://packages.debian.org/sid/firmware-misc-nonfree

Do you have non-free configured in your sources.list?



  I didn't...but I have now. :)  Thanks



 Dl'ed and installed...but I still get this :

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin 
for

module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for
module i915


Hi Frank, now that you have added 'non-free sources', apt or apt-get
and install 'firmware-linux' it's a 'meta package' and will pull in
your missing firmware. Another meta package is firmware-linux-nonfree,
but firmware-linux should pull that in too.

regards,


   I installed firmware-linuxit pulled in several packages including
one I need (intel-microcode)  but I still
get :
Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for
module i915
Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for
module i915

when init is updated.


Do you have 'xserver-xorg-video-intel' installed?  If not install it 
and see if your missing firmware goes away.


   Yes, it's installed.

Re: missing firmware ??

[Frank M]

On 28/01/17 05:45 PM, Sven Hartge wrote:

Frank M <debianl...@videotron.ca> wrote:

On 28/01/17 01:18 PM, Sven Hartge wrote:

Frank M <debianl...@videotron.ca> wrote:

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

Do you have a Intel Kaby Lake or Intel Broxton (discontinued SoC) based
system? If not, then the missing firmware is no problem for you.

This is what cpuinfo says:
model name: Intel(R) Core(TM) i5 CPU 660  @ 3.33GHz

"Kaby Lake" is one of the newest Intel CPU-models. If you have not
bought your system in the last 2 month, then it will not be a "Kaby
Lake"-based one.

Your CPU is this one
<http://ark.intel.com/de/products/43550/Intel-Core-i5-660-Processor-4M-Cache-3_33-GHz>
from 2010 of the "Clarkdale" family.

Grüße,
Sven.



   So the missing firmware is no problem. Good to know.
Thanks Sven

Re: missing firmware ??

[Frank M]

On 28/01/17 01:18 PM, Sven Hartge wrote:

Frank M <debianl...@videotron.ca> wrote:


update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module 
i915

Do you have a Intel Kaby Lake or Intel Broxton (discontinued SoC) based
system? If not, then the missing firmware is no problem for you.

Grüße,
Sven.


This is what cpuinfo says:


processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 37
model name: Intel(R) Core(TM) i5 CPU 660  @ 3.33GHz
stepping: 2
microcode: 0x9
cpu MHz: 1197.000
cache size: 4096 KB
physical id: 0
siblings: 4
core id: 0
cpu cores: 2
apicid: 0
initial apicid: 0
fpu: yes
fpu_exception: yes
cpuid level: 11
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 
smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_lm 
tpr_shadow vnmi flexpriority ept vpid dtherm ida arat

bugs:
bogomips: 6650.08
clflush size: 64
cache_alignment: 64
address sizes: 36 bits physical, 48 bits virtual
power management:

processor: 1
vendor_id: GenuineIntel
cpu family: 6
model: 37
model name: Intel(R) Core(TM) i5 CPU 660  @ 3.33GHz
stepping: 2
microcode: 0x9
cpu MHz: 1197.000
cache size: 4096 KB
physical id: 0
siblings: 4
core id: 2
cpu cores: 2
apicid: 4
initial apicid: 4
fpu: yes
fpu_exception: yes
cpuid level: 11
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 
smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_lm 
tpr_shadow vnmi flexpriority ept vpid dtherm ida arat

bugs:
bogomips: 6649.86
clflush size: 64
cache_alignment: 64
address sizes: 36 bits physical, 48 bits virtual
power management:

processor: 2
vendor_id: GenuineIntel
cpu family: 6
model: 37
model name: Intel(R) Core(TM) i5 CPU 660  @ 3.33GHz
stepping: 2
microcode: 0x9
cpu MHz: 1197.000
cache size: 4096 KB
physical id: 0
siblings: 4
core id: 0
cpu cores: 2
apicid: 1
initial apicid: 1
fpu: yes
fpu_exception: yes
cpuid level: 11
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 
smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_lm 
tpr_shadow vnmi flexpriority ept vpid dtherm ida arat

bugs:
bogomips: 6649.85
clflush size: 64
cache_alignment: 64
address sizes: 36 bits physical, 48 bits virtual
power management:

processor: 3
vendor_id: GenuineIntel
cpu family: 6
model: 37
model name: Intel(R) Core(TM) i5 CPU 660  @ 3.33GHz
stepping: 2
microcode: 0x9
cpu MHz: 1197.000
cache size: 4096 KB
physical id: 0
siblings: 4
core id: 2
cpu cores: 2
apicid: 5
initial apicid: 5
fpu: yes
fpu_exception: yes
cpuid level: 11
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx 
smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt aes lahf_lm 
tpr_shadow vnmi flexpriority ept vpid dtherm ida arat

bugs:
bogomips: 6649.83
clflush size: 64
cache_alignment: 64
address sizes: 36 bits physical, 48 bits virtual
power management:

I have no idea what this means in terms of branding ...


Thanks
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 37
model name  : Intel(R) Core(TM) i5 CPU 660  @ 3.33GHz
stepping: 2
microcode   : 0x9
cpu MHz : 1197.000
cache size  : 4096 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 11
wp  : yes
flags   : fpu vme de pse t

Re: missing firmware ??

[Frank M]

On 28/01/17 04:17 PM, Jimmy Johnson wrote:


On 01/28/2017 09:58 AM, Frank M wrote:

On 28/01/17 12:55 PM, Frank M wrote:




On 28/01/17 12:52 PM, Joe wrote:

On Sat, 28 Jan 2017 12:20:00 -0500
Frank M <debianl...@videotron.ca> wrote:


Updating my Stretch installation today I first noticed this:

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_26.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6_1.bin
for module i915


A search using apt-file didn't turn up any packages.


What am I missing here ?



https://packages.debian.org/sid/firmware-misc-nonfree

Do you have non-free configured in your sources.list?



  I didn't...but I have now. :)  Thanks



 Dl'ed and installed...but I still get this :

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for
module i915


Hi Frank, now that you have added 'non-free sources', apt or apt-get 
and install 'firmware-linux' it's a 'meta package' and will pull in 
your missing firmware. Another meta package is firmware-linux-nonfree, 
but firmware-linux should pull that in too.


regards,


   I installed firmware-linuxit pulled in several packages 
including one I need (intel-microcode)  but I still

get :
Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for 
module i915


when init is updated.

Re: missing firmware ??

[Frank M]

On 28/01/17 12:55 PM, Frank M wrote:




On 28/01/17 12:52 PM, Joe wrote:

On Sat, 28 Jan 2017 12:20:00 -0500
Frank M <debianl...@videotron.ca> wrote:


Updating my Stretch installation today I first noticed this:

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_26.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6_1.bin
for module i915


A search using apt-file didn't turn up any packages.


What am I missing here ?



https://packages.debian.org/sid/firmware-misc-nonfree

Do you have non-free configured in your sources.list?



  I didn't...but I have now. :)  Thanks



 Dl'ed and installed...but I still get this :

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for 
module i915

Re: missing firmware ??

[Frank M]

On 28/01/17 12:52 PM, Joe wrote:

On Sat, 28 Jan 2017 12:20:00 -0500
Frank M <debianl...@videotron.ca> wrote:


Updating my Stretch installation today I first noticed this:

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_26.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin
for module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6_1.bin
for module i915


A search using apt-file didn't turn up any packages.


What am I missing here ?



https://packages.debian.org/sid/firmware-misc-nonfree

Do you have non-free configured in your sources.list?



  I didn't...but I have now. :)  Thanks

missing firmware ??

[Frank M]

Updating my Stretch installation today I first noticed this:

update-initramfs: Generating /boot/initrd.img-4.9.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/bxt_dmc_ver1_07.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/skl_dmc_ver1_26.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/skl_guc_ver6_1.bin for 
module i915



A search using apt-file didn't turn up any packages.


What am I missing here ?


Thanks

Re: Cannot autostart apps after boot

[Frank M]

On 2017-01-13 02:23 PM, Вадим Колчев wrote:
Thanks for reply. I have managed to solve the issue today. Tried to 
create desktop file again and managed to succeed. Not sure now why it 
had not worked for me for the first time.


Thanks to everyone who did their best to help.


 This will help you next time you want to create a desktop file:

http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#basic-format

Each field is important in the file.





13 Янв 2017 г. 9:14 PM пользователь "Michael Milliman" 
> 
написал:


It would help quite a bit if you would let us know which version
of debian you are using (i.e. wheezy, jessie, stretch, etc.).
Personally, I have not had this problem at all running jessie.
Also, check your log files to see if there is anything in them
that might explain the problem.



On 01/12/2017 03:41 PM, Вадим Колчев wrote:

Hello,

Cannot autostart apps after boot. Tried 3 methods:

1) used gnome-tweak-tool and added app to autostart there - no
luck;
2) used /etc/rc.local to provide path to app I need to
autostart - no luck;
3) used .config/autostart - put myprogram.destop file there -
still no luck.

What could I be doing wrong?

Best regards,
Vadim


-- 
73's de Mike, WB5VQX

Howto to get more UBE

[Frank M.]

I plaing around with mail filters. I like to get more spam. 
(Not to download. Real traffic on port 25)

I create thousands of accounts on my honeypot, but how I distribute they on 
the web?

Any nice ideas howto get more UBE?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201104231554.28995.fran...@slidx.com