bugs .. Are they really bad?

Sector11 · 2016-05-02 12:53:13

  $ sys
System:    Host: bunsen Kernel: 3.16.0-4-amd64 x86_64 (64 bit) Desktop: Openbox 3.5.2
           Distro: BunsenLabs 8.4 bunsen-hydrogen

Anyone have a clue what this is about?

Fetched 1,490 kB in 4s (304 kB/s)       
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of samba-common-bin (2:4.1.17+dfsg-2+deb8u2 → 2:4.2.10+dfsg-0+deb8u2) <Outstanding>
 b1 - #820965 - [regression]: net usersidlist: Could not malloc sid array Could not get the user/sid list
serious bugs of samba-libs (2:4.1.17+dfsg-2+deb8u2 → 2:4.2.10+dfsg-0+deb8u2) <Outstanding>
 b2 - #821002 - samba: Error upgrading from deb8u1 to deb8u2. Missing Replaces for libsmbd-base.so.0
Summary:
 samba-common-bin(1 bug), samba-libs(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n

Don't understand the

Could not get the user/sid list

... sid part.

Head_on_a_Stick · 2016-05-02 13:05:17

The SID list is the Windows equivalent of GUIDs & UIDs, I think.

See http://pig.made-it.com/uidgid.html

Don't know about those bugs though, it looks like the second one just chokes up dpkg(8) and makes the upgrade fail; can't make any sense of the first one

If you give me a bit, I'll see what happens from the live environment.

pvsage · 2016-05-02 13:16:52

Is there a way to track who "reported" these as bugs? I have a theory as to who it might be.

EDIT: In Debian Stable, I tend to disregard all bug reports except those marked as grave; anything less is usually somebody griping about copyleft or something similarly trivial.

Last edited by pvsage (2016-05-02 13:25:55)

xaos52 · 2016-05-02 13:40:54

Go to Debian bug search page
and enter the bug number in the search field.

@Sector11,
Are you even using those packages? Do you have a samba server or client running?

nobody · 2016-05-02 13:45:33

Sector11 wrote:

  $ sys
System:    Host: bunsen Kernel: 3.16.0-4-amd64 x86_64 (64 bit) Desktop: Openbox 3.5.2
           Distro: BunsenLabs 8.4 bunsen-hydrogen

Anyone have a clue what this is about?

Fetched 1,490 kB in 4s (304 kB/s)       
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
serious bugs of samba-common-bin (2:4.1.17+dfsg-2+deb8u2 → 2:4.2.10+dfsg-0+deb8u2) <Outstanding>
 b1 - #820965 - [regression]: net usersidlist: Could not malloc sid array Could not get the user/sid list
serious bugs of samba-libs (2:4.1.17+dfsg-2+deb8u2 → 2:4.2.10+dfsg-0+deb8u2) <Outstanding>
 b2 - #821002 - samba: Error upgrading from deb8u1 to deb8u2. Missing Replaces for libsmbd-base.so.0
Summary:
 samba-common-bin(1 bug), samba-libs(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n

Don't understand the

Could not get the user/sid list

... sid part.

You can ignore those. Just distupgrade.

the sid list is commonly the list of SessionIDs. A session is a group of process groups. You might have used them in xsession scripts through the comnmand setsid.

Head_on_a_Stick · 2016-05-02 13:46:32

Just installed samba from the live environment and it seemed to go fine:

user@debian:~$ sudo apt install samba
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  attr libaio1 libasn1-8-heimdal libhcrypto4-heimdal libhdb9-heimdal
  libheimbase1-heimdal libhx509-5-heimdal libkrb5-26-heimdal libroken18-heimdal
  libwind0-heimdal python-dnspython python-ldb python-ntdb python-samba
  python-tdb samba-common samba-common-bin samba-dsdb-modules samba-vfs-modules
  tdb-tools
Suggested packages:
  bind9 bind9utils ctdb ldb-tools smbldap-tools winbind heimdal-clients
The following NEW packages will be installed:
  attr libaio1 libasn1-8-heimdal libhcrypto4-heimdal libhdb9-heimdal
  libheimbase1-heimdal libhx509-5-heimdal libkrb5-26-heimdal libroken18-heimdal
  libwind0-heimdal python-dnspython python-ldb python-ntdb python-samba
  python-tdb samba samba-common samba-common-bin samba-dsdb-modules
  samba-vfs-modules tdb-tools
0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,701 kB of archives.
After this operation, 27.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://security.debian.org/ jessie/updates/main python-ldb amd64 2:1.1.20-0+deb8u1 [30.6 kB]
Get:2 http://security.debian.org/ jessie/updates/main python-tdb amd64 1.3.6-0+deb8u1 [14.9 kB]
Get:3 http://security.debian.org/ jessie/updates/main python-samba amd64 2:4.2.10+dfsg-0+deb8u2 [1,013 kB]
Get:4 http://security.debian.org/ jessie/updates/main samba-common all 2:4.2.10+dfsg-0+deb8u2 [238 kB]
Get:5 http://security.debian.org/ jessie/updates/main samba-common-bin amd64 2:4.2.10+dfsg-0+deb8u2 [613 kB]
Get:6 http://security.debian.org/ jessie/updates/main samba-dsdb-modules amd64 2:4.2.10+dfsg-0+deb8u2 [305 kB]
Get:7 http://security.debian.org/ jessie/updates/main tdb-tools amd64 1.3.6-0+deb8u1 [26.3 kB]
Get:8 http://security.debian.org/ jessie/updates/main samba amd64 2:4.2.10+dfsg-0+deb8u2 [1,024 kB]
Get:9 http://security.debian.org/ jessie/updates/main samba-vfs-modules amd64 2:4.2.10+dfsg-0+deb8u2 [326 kB]
Get:10 http://ftp.debian.org/debian/ jessie/main libaio1 amd64 0.3.110-1 [9,312 B]
Get:11 http://ftp.debian.org/debian/ jessie/main libroken18-heimdal amd64 1.6~rc2+dfsg-9 [63.0 kB]
Get:12 http://ftp.debian.org/debian/ jessie/main libasn1-8-heimdal amd64 1.6~rc2+dfsg-9 [205 kB]
Get:13 http://ftp.debian.org/debian/ jessie/main libhcrypto4-heimdal amd64 1.6~rc2+dfsg-9 [110 kB]
Get:14 http://ftp.debian.org/debian/ jessie/main libheimbase1-heimdal amd64 1.6~rc2+dfsg-9 [51.7 kB]
Get:15 http://ftp.debian.org/debian/ jessie/main libwind0-heimdal amd64 1.6~rc2+dfsg-9 [71.7 kB]
Get:16 http://ftp.debian.org/debian/ jessie/main libhx509-5-heimdal amd64 1.6~rc2+dfsg-9 [131 kB]
Get:17 http://ftp.debian.org/debian/ jessie/main libkrb5-26-heimdal amd64 1.6~rc2+dfsg-9 [229 kB]
Get:18 http://ftp.debian.org/debian/ jessie/main libhdb9-heimdal amd64 1.6~rc2+dfsg-9 [86.2 kB]
Get:19 http://ftp.debian.org/debian/ jessie/main python-dnspython all 1.12.0-1 [101 kB]
Get:20 http://ftp.debian.org/debian/ jessie/main python-ntdb amd64 1.0-5 [9,548 B]
Get:21 http://ftp.debian.org/debian/ jessie/main attr amd64 1:2.4.47-2 [42.8 kB]  
Fetched 4,701 kB in 10s (439 kB/s)                                                
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of samba (→ 2:4.2.10+dfsg-0+deb8u2) <Outstanding>
 b1 - #821811 - samba: badlock patch breaks trust relationship
 b2 - #822937 - samba: throws error on atempt to connect
serious bugs of samba-common-bin (→ 2:4.2.10+dfsg-0+deb8u2) <Outstanding>
 b3 - #820965 - [regression]: net usersidlist: Could not malloc sid array Could not get the user/sid list
Summary:
 samba-common-bin(1 bug), samba(2 bugs)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] Y
Preconfiguring packages ...
Selecting previously unselected package libaio1:amd64.
(Reading database ... 93868 files and directories currently installed.)
Preparing to unpack .../libaio1_0.3.110-1_amd64.deb ...
Unpacking libaio1:amd64 (0.3.110-1) ...
Selecting previously unselected package libroken18-heimdal:amd64.
Preparing to unpack .../libroken18-heimdal_1.6~rc2+dfsg-9_amd64.deb ...
Unpacking libroken18-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Selecting previously unselected package libasn1-8-heimdal:amd64.
Preparing to unpack .../libasn1-8-heimdal_1.6~rc2+dfsg-9_amd64.deb ...
Unpacking libasn1-8-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Selecting previously unselected package libhcrypto4-heimdal:amd64.
Preparing to unpack .../libhcrypto4-heimdal_1.6~rc2+dfsg-9_amd64.deb ...
Unpacking libhcrypto4-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Selecting previously unselected package libheimbase1-heimdal:amd64.
Preparing to unpack .../libheimbase1-heimdal_1.6~rc2+dfsg-9_amd64.deb ...
Unpacking libheimbase1-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Selecting previously unselected package libwind0-heimdal:amd64.
Preparing to unpack .../libwind0-heimdal_1.6~rc2+dfsg-9_amd64.deb ...
Unpacking libwind0-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Selecting previously unselected package libhx509-5-heimdal:amd64.
Preparing to unpack .../libhx509-5-heimdal_1.6~rc2+dfsg-9_amd64.deb ...
Unpacking libhx509-5-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Selecting previously unselected package libkrb5-26-heimdal:amd64.
Preparing to unpack .../libkrb5-26-heimdal_1.6~rc2+dfsg-9_amd64.deb ...
Unpacking libkrb5-26-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Selecting previously unselected package libhdb9-heimdal:amd64.
Preparing to unpack .../libhdb9-heimdal_1.6~rc2+dfsg-9_amd64.deb ...
Unpacking libhdb9-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Selecting previously unselected package python-ldb.
Preparing to unpack .../python-ldb_2%3a1.1.20-0+deb8u1_amd64.deb ...
Unpacking python-ldb (2:1.1.20-0+deb8u1) ...
Selecting previously unselected package python-dnspython.
Preparing to unpack .../python-dnspython_1.12.0-1_all.deb ...
Unpacking python-dnspython (1.12.0-1) ...
Selecting previously unselected package python-ntdb.
Preparing to unpack .../python-ntdb_1.0-5_amd64.deb ...
Unpacking python-ntdb (1.0-5) ...
Selecting previously unselected package python-tdb.
Preparing to unpack .../python-tdb_1.3.6-0+deb8u1_amd64.deb ...
Unpacking python-tdb (1.3.6-0+deb8u1) ...
Selecting previously unselected package python-samba.
Preparing to unpack .../python-samba_2%3a4.2.10+dfsg-0+deb8u2_amd64.deb ...
Unpacking python-samba (2:4.2.10+dfsg-0+deb8u2) ...
Selecting previously unselected package samba-common.
Preparing to unpack .../samba-common_2%3a4.2.10+dfsg-0+deb8u2_all.deb ...
Unpacking samba-common (2:4.2.10+dfsg-0+deb8u2) ...
Selecting previously unselected package samba-common-bin.
Preparing to unpack .../samba-common-bin_2%3a4.2.10+dfsg-0+deb8u2_amd64.deb ...
Unpacking samba-common-bin (2:4.2.10+dfsg-0+deb8u2) ...
Selecting previously unselected package samba-dsdb-modules.
Preparing to unpack .../samba-dsdb-modules_2%3a4.2.10+dfsg-0+deb8u2_amd64.deb ...
Unpacking samba-dsdb-modules (2:4.2.10+dfsg-0+deb8u2) ...
Selecting previously unselected package tdb-tools.
Preparing to unpack .../tdb-tools_1.3.6-0+deb8u1_amd64.deb ...
Unpacking tdb-tools (1.3.6-0+deb8u1) ...
Selecting previously unselected package samba.
Preparing to unpack .../samba_2%3a4.2.10+dfsg-0+deb8u2_amd64.deb ...
Unpacking samba (2:4.2.10+dfsg-0+deb8u2) ...
Selecting previously unselected package attr.
Preparing to unpack .../attr_1%3a2.4.47-2_amd64.deb ...
Unpacking attr (1:2.4.47-2) ...
Selecting previously unselected package samba-vfs-modules.
Preparing to unpack .../samba-vfs-modules_2%3a4.2.10+dfsg-0+deb8u2_amd64.deb ...
Unpacking samba-vfs-modules (2:4.2.10+dfsg-0+deb8u2) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u4) ...
Setting up libaio1:amd64 (0.3.110-1) ...
Setting up libroken18-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Setting up libasn1-8-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Setting up libhcrypto4-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Setting up libheimbase1-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Setting up libwind0-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Setting up libhx509-5-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Setting up libkrb5-26-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Setting up libhdb9-heimdal:amd64 (1.6~rc2+dfsg-9) ...
Setting up python-ldb (2:1.1.20-0+deb8u1) ...
Setting up python-dnspython (1.12.0-1) ...
Setting up python-ntdb (1.0-5) ...
Setting up python-tdb (1.3.6-0+deb8u1) ...
Setting up python-samba (2:4.2.10+dfsg-0+deb8u2) ...
Setting up samba-common (2:4.2.10+dfsg-0+deb8u2) ...

Creating config file /etc/samba/smb.conf with new version
Setting up samba-common-bin (2:4.2.10+dfsg-0+deb8u2) ...
Setting up samba-dsdb-modules (2:4.2.10+dfsg-0+deb8u2) ...
Setting up tdb-tools (1.3.6-0+deb8u1) ...
update-alternatives: using /usr/bin/tdbbackup.tdbtools to provide /usr/bin/tdbbackup (tdbbackup) in auto mode
Setting up samba (2:4.2.10+dfsg-0+deb8u2) ...
Adding group `sambashare' (GID 117) ...
Done.
Setting up attr (1:2.4.47-2) ...
Setting up samba-vfs-modules (2:4.2.10+dfsg-0+deb8u2) ...
Processing triggers for libc-bin (2.19-18+deb8u4) ...
Processing triggers for systemd (215-17+deb8u4) ...

I've never used samba and I don't have access to any Windows machines (yay!) so I can't test this.

Sector11 · 2016-05-02 17:04:57

Had to go out ... just got back. Let's see if I can do this in order.

@HoaS

Still don't understand why the SID thing, I have no Windows and haven't for YEARS!
6 USB sticks:

 
 02 May 16 @ 13:15:47 ~
  $ lsusb
Bus 001 Device 022: ID 054c:05b8 Sony Corp.

  $ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sdb1      fuseblk   7.5G  2.7G  4.9G  36% /media/sector11/108D9D5A26297ED9
------------------------
  $ lsusb
Bus 001 Device 023: ID 054c:02a5 Sony Corp. MicroVault Flash Drive

  $ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sdb1      vfat      7.3G   32K  7.3G   1% /media/sector11/Sony_8GM
------------------------
  $ lsusb
Bus 001 Device 024: ID 0781:556b SanDisk Corp.

  $ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sdb1      vfat      3.8G   15M  3.8G   1% /media/sector11/SDC-4GB
------------------------
  $ lsusb
Bus 001 Device 025: ID 0781:5567 SanDisk Corp. Cruzer Blade

  $ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sdb1      vfat      3.8G  4.0K  3.8G   1% /media/sector11/SD-4GB
------------------------
  $ lsusb
Bus 001 Device 026: ID 0781:5567 SanDisk Corp. Cruzer Blade

  $ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sdb1      vfat      7.5G  1.7G  5.8G  23% /media/sector11/SD-8GB

and one old 2gb Datatraveller with #! 11 on it that I can't seem to mount anymore for some reason.

and then there is my external HDD:

  $ lsusb
Bus 001 Device 027: ID 18a5:0225 Verbatim, Ltd 

  $ df -hT
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/sdb1      ext4      230G   56G  162G  26% /media/sector11/disk

@pvsage - out of a world of people you have a theory? Fill me in.

@xaos52 - I'll have to remember (bookmark) the bug search page. Thanks.
First: 820965
Second: 821002
both billed as serious and if I wasn't such a noob I might know what all that means.

xaos52 wrote:

Are you even using those packages? Do you have a samba server or client running?

To the best of my knowledge - NO! but they are here ... showing just what is installed:

 02 May 16 @ 13:45:43 ~
  $ ser samba
alias ser = aptitude search
i A python-samba                                    - Python bindings for Samba                                 
i A samba-common                                    - common files used by both the Samba server and client     
i A samba-common-bin                                - Samba common files used by both the server and the client 
i A samba-libs                                      - Samba core libraries                                      
 
 02 May 16 @ 13:45:52 ~
  $

@nobody

nobody wrote:

You can ignore those. Just distupgrade.
the sid list is commonly the list of SessionIDs. A session is a group of process groups. You might have used them in xsession scripts through the comnmand setsid.

OK .. then how does one know when to ignore serious or grave bugs?
Did the upgrade though ... they came in. Thanks.

and back to @HoaS

Head_on_a_Stick wrote:

I've never used samba and I don't have access to any Windows machines (yay!) so I can't test this.

Yea, neither do I - (sombre: yay) - so now it's

Why is this here? Research time - and of course this all on me now.

Thanks everyone

Sector11 · 2016-05-02 17:08:43

Before I mark this [Solved[ - [Fixed], whatever ... is there a way to find out what is actually using this samba stuff?

Head_on_a_Stick · 2016-05-02 17:10:42

aptitude why samba

Sector11 · 2016-05-02 17:23:15

^

attitude why-not samba

... OK kidding ...

... and here it is - cups

 02 May 16 @ 14:12:39 ~
  $ aptitude why samba
i   cups       Suggests   smbclient                       
p   smbclient  Suggests   cifs-utils                      
p   cifs-utils Recommends winbind                         
p   winbind    Depends    samba (= 2:4.2.10+dfsg-0+deb8u2)
 
 02 May 16 @ 14:12:43 ~
  $

NO ... cups has no dependency on samba. (apt-cache depends cups)

Not even sure I need cups - it's 64bit. My Brother uses a 32bit driver.
EDIT: I need it!

damo · 2016-05-02 17:34:44

Sector11 wrote:

... My Brother uses a 32bit driver.

Sorry, couldn't resist
images?q=tbn:ANd9GcTF65R71Mi5qyZk5cy9O-fY0C88JSlmOLwJ0B4rIz1rYnDWiMs6

Sector11 · 2016-05-02 17:54:16

I think if I was in your situation I'd have a hard time resisting the temptation as well.

OR like you - Resistance is futile.
{still chuckling here} ... gonna dream about the screaming female driver now - one of those "once seen" things.

johnraff · 2016-05-03 06:53:11

Sector11 wrote:

 02 May 16 @ 14:12:39 ~
  $ aptitude why samba
i   cups       Suggests   smbclient                       
p   smbclient  Suggests   cifs-utils                      
p   cifs-utils Recommends winbind                         
p   winbind    Depends    samba (= 2:4.2.10+dfsg-0+deb8u2)
 
 02 May 16 @ 14:12:43 ~
  $

Do you need smbclient, cifs-utils or winbind ? Try uninstalling smbclient and see if it breaks anything. If not, cifs-utils, winbind and samba can probably go too.

pvsage · 2016-05-03 09:02:06

^ If I'm reading that right, those other three packages aren't installed. Aptitude uses "i" to show that a package is installed, "p" for a regular package that isn't installed but available, and "v" for "virtual" packages (e.g. those "provided by" a real package).

Sector11 · 2016-05-03 10:44:46

^ correct. i = installed, p = avaliable and i A = installed Automatic (I think)

Those three are not installed. The really weird thing: "samba" itself is not installed.

 03 May 16 @ 07:16:03 ~
  $ ser samba
alias ser = aptitude search
{snip}
i A python-samba                                    - Python bindings for Samba                                 
↓↓↓ {snip}
p   samba                                           - SMB/CIFS file, print, and login server for Unix           
↑↑↑ {snip}
i A samba-common                                    - common files used by both the Samba server and client     
{snip}
i A samba-common-bin                                - Samba common files used by both the server and the client 
{snip}
i A samba-libs                                      - Samba core libraries

So following HoaS's idea of "why" I followed the cookie crumbs:

 03 May 16 @ 07:25:19 ~
  $ aptitude why python-samba
i   fusesmb          Depends samba-common-bin
i A samba-common-bin Depends python-samba    
 
 03 May 16 @ 07:25:31 ~
  $ aptitude why samba-common
i   fusesmb Depends samba-common
 
 03 May 16 @ 07:26:05 ~
  $ aptitude why samba-common-bin
i   fusesmb Depends samba-common-bin
 
 03 May 16 @ 07:26:33 ~
  $ aptitude why samba-libs
i   fusesmb          Depends samba-common-bin                     
i A samba-common-bin Depends samba-libs (= 2:4.2.10+dfsg-0+deb8u2)
 
 03 May 16 @ 07:27:06 ~
  $ aptitude why fusesmb
Unable to find a reason to install fusesmb.
 
 03 May 16 @ 07:27:28 ~
  $

fusesmb is now GONE!

Would I be correct in 'assuming' these can be deleted safely?

 03 May 16 @ 07:41:42 ~
  $ aptitude why python-samba samba-common
i A python-samba  Depends    samba-libs (= 2:4.2.10+dfsg-0+deb8u2)
i A samba-libs    Depends    libwbclient0 (>= 2:4.0.3+dfsg1)      
i A libwbclient0  PreDepends dpkg (>= 1.15.6~)                    
i   dpkg          Suggests   apt                                  
i   apt           Suggests   python-apt                           
i   python-apt    Suggests   python-vte                           
i A python-vte    Depends    libgtk2.0-0 (>= 2.20.0)              
i A libgtk2.0-0   Suggests   gvfs                                 
i   gvfs          Suggests   gvfs-backends                        
i   gvfs-backends Suggests   samba-common

Head_on_a_Stick · 2016-05-03 17:46:30

For reference:

i - the package is installed and all its dependencies are satisfied.
c - the package was removed, but its configuration files are still present.
p - the package and all its configuration files were removed, or the package was never installed.
v - the package is virtual.
B - the package has broken dependencies.
u - the package has been unpacked but not configured.
C - half-configured: the package's configuration was interrupted.
H - half-installed: the package's installation was interrupted.
W - triggers-awaited: the package awaits trigger processing by another package.
T - triggers-pending: The package has had an update triggered due to changes in another package.

https://www.debian.org/doc/manuals/apti … 02.en.html

I would try:

apt-get -s purge "*samba*"

Or just use:

sudo aptitude -u

Sector11 · 2016-05-03 18:10:07

Don't see the A in there. Thanks for the chart though.

Simulating removal/purging samba wants to remove:

Purg gvfs-backends [1.22.2-1]
Purg libsmbclient [2:4.2.10+dfsg-0+deb8u2]
Purg samba-common-bin [2:4.2.10+dfsg-0+deb8u2]
Purg python-samba [2:4.2.10+dfsg-0+deb8u2]
Purg samba-common [2:4.2.10+dfsg-0+deb8u2]
Purg samba-libs [2:4.2.10+dfsg-0+deb8u2]

so I follow the breab-crumbs:

 03 May 16 @ 15:04:23 ~
  $ aptitude why gvfs-backends
i   gvfs Suggests gvfs-backends
 
 03 May 16 @ 15:05:54 ~
  $ aptitude why gvfs
i   gvfs-fuse Depends gvfs (= 1.22.2-1)
 
 03 May 16 @ 15:06:02 ~
  $ aptitude why gvfs-fuse
i   xorg        Depends    xinit                                                             
i A xinit       Recommends xterm | x-session-manager | x-window-manager | x-terminal-emulator
p   lxsession   Provides   x-session-manager                                                 
p   lxsession   Recommends lxde-common                                                       
p   lxde-common Recommends pcmanfm                                                           
p   pcmanfm     Recommends gvfs-fuse                                                         
 
 03 May 16 @ 15:06:16 ~
  $

so I took the simulate out and removed/purged 'samba*'

Let's see if I broke something.

#1 2016-05-02 12:53:13

bugs .. Are they really bad?

#2 2016-05-02 13:05:17

Re: bugs .. Are they really bad?

#3 2016-05-02 13:16:52

Re: bugs .. Are they really bad?

#4 2016-05-02 13:40:54

Re: bugs .. Are they really bad?

#5 2016-05-02 13:45:33

Re: bugs .. Are they really bad?

#6 2016-05-02 13:46:32

Re: bugs .. Are they really bad?

#7 2016-05-02 17:04:57

Re: bugs .. Are they really bad?

#8 2016-05-02 17:08:43

Re: bugs .. Are they really bad?

#9 2016-05-02 17:10:42

Re: bugs .. Are they really bad?

#10 2016-05-02 17:23:15

Re: bugs .. Are they really bad?

#11 2016-05-02 17:34:44

Re: bugs .. Are they really bad?

#12 2016-05-02 17:54:16

Re: bugs .. Are they really bad?

#13 2016-05-03 06:53:11

Re: bugs .. Are they really bad?

#14 2016-05-03 09:02:06

Re: bugs .. Are they really bad?

#15 2016-05-03 10:44:46

Re: bugs .. Are they really bad?

#16 2016-05-03 17:46:30

Re: bugs .. Are they really bad?

#17 2016-05-03 18:10:07

Re: bugs .. Are they really bad?

Board footer