[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#885860: marked as done (wine registers mime handlers with too high priority)

Your message dated Tue, 9 Jan 2018 20:04:17 +0100
with message-id <69a3c4ba-4378-28fa-6cf0-a67ee9d99e5d@gmail.com>
and subject line Re: [pkg-wine-party] Bug#885860: wine registers mime handlers with too high priority
has caused the Debian Bug report #885860,
regarding wine registers mime handlers with too high priority
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
885860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885860
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wine
Version: 1.8.7-2
Severity: important

Hello,

once you install wine text files open in notepad, pictures, PDFs and
HTML files in winebrowser.

This breaks the desktop integration.

It is fine to install these alternatives as very low priority but the
priority for thes slow-starting nearly useless applications in the
highest. Higher than gedit, evince, gqview, imagemagick, ..

This is broken

Please fix the priority of wine pre-installed applicatins to work with
the rest of the distribution.

Thanks

-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

-- System Information:
Debian Release: 9.3
  APT prefers stable
  APT policy: (900, 'stable'), (505, 'oldstable'), (500, 'oldoldstable'), (500, 'testing'), (171, 'unstable'), (151, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.14.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wine depends on:
ii  wine32  1.8.7-2
ii  wine64  1.8.7-2

wine recommends no packages.

Versions of packages wine suggests:
ii  dosbox       0.74-4.2+b2
pn  playonlinux  <none>
pn  winbind      <none>
ii  wine-binfmt  1.8.7-2
ii  winetricks   0.0+20170101-1

Versions of packages wine is related to:
ii  fonts-wine               1.8.7-2
ii  wine                     1.8.7-2
ii  wine-development [wine]  3.0~rc1-1
ii  wine32                   1.8.7-2
ii  wine64                   1.8.7-2

-- no debconf information

--- End Message ---
--- Begin Message --- 
On 01/03/2018 01:13 AM, Michal Suchanek wrote:
> indeed removing files previously created by wine I can no longer
> reproduce the problem. I used many older versions of wine so one of them
> created these files.

Thanks, so I'll close this report.  If this ever shows up again with the
new packages please tell us.


> It is unfortunate that winemenubuilder cannot identify the old files and
> remove them when updating the associations but this should not reappear
> on new systems at least.

The problem is that these files are in $HOME.  We (packagers) can't
change/delete files in there, because we don't know if a user put them
there on purpose.

Greets
jre

--- End Message ---
Reply to: