https://bugs.winehq.org/show_bug.cgi?id=39596
Bug ID: 39596
Summary: "make distclean" does not work
Product: Wine
Version: 1.7.55
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wylda(a)volny.cz
Distribution: ---
I wanted to build wine from git source as out-of-tree build. But configure
says:
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
configure: error: you are building out of the source tree, but the source tree
contains object files.
You need to run 'make distclean' in the source tree first.
But running "make distclean" inside git tree fails:
$ make distclean
make: *** No rule to make target 'Make.vars.in', needed by 'Makefile'. Stop.
IIRC this used to work. Work arounded in git tree by:
$ rm -rf *
$ git checkout -f wine-1.7.55
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34561
Bug #: 34561
Summary: regression: Finale/Finale Notepad 2012 crashes if
Pulseaudio is disabled
Product: Wine
Version: 1.7.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dsound
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: s_chriscollins(a)hotmail.com
Classification: Unclassified
Created attachment 46013
--> http://bugs.winehq.org/attachment.cgi?id=46013
Finale NotePad 2012's dying breath
If Pulseaudio is disabled, Finale Notepad 2012 crashes on startup after
clicking past the initial screen. The error is "Unhandled exception: divide by
zero in 32-bit code (0xf66ec401)." The backtrace is attached to this bug
report. This bug also affects the full retail version of Finale 2012.
I couldn't do a regression test on this because the crash only happens when I
am using the biarch wine version from the Wine Team PPA for Ubuntu. I have only
figured out how to compile 32-bit Wine using an lxc container, and this bug
does not happen with my compiled 32-bit Wine binaries.
This bug does not happen with Wine 1.4.1, but does happen with 1.7.2. I think
it happened with 1.6 as well, but that version is no longer available from the
repository, so I can't verify.
If there isn't enough info from the backtrace, then I might just have to learn
to do a biarch regression test. Looks a bit daunting, though...
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=22315
Summary: Notification tray icons using solid rather than
transparent background colors
Product: Wine
Version: 1.1.42
Platform: x86
URL: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug
/403135?comments=all
OS/Version: Linux
Status: NEW
Keywords: integration
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
>From a large bug report on launchpad affecting many apps:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/403135?comments=all
Essentially, tray icons are being drawn with non-transparent backgrounds. This
is usually from setting their (not always correct) color to bg_color rather
than just transparent.
http://launchpadlibrarian.net/41246531/screen.png is a screenshot showing
Spotify (and a few other, non-Wine apps) using the wrong background in the
system tray.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=7146
super_man(a)post.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |super_man(a)post.com
--- Comment #15 from super_man(a)post.com ---
Running the program is no issue, but it feels to missing some content.
Definitely not fixed/has issues at current form.
wine 1.7.55
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=8712
Nikolay Sivov <bunglehead(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |39597
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=8712
Nikolay Sivov <bunglehead(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks|39597 |
--- Comment #57 from Nikolay Sivov <bunglehead(a)gmail.com> ---
Sure, I don't like it either, reports should be as targeted as possible. But
when report is closed while it still demonstrates valid reproducible issue, I'd
like to keep this information, and I know you usually do exactly that.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=8712
Nikolay Sivov <bunglehead(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |39597
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=8712
--- Comment #56 from Anastasius Focht <focht(a)gmx.net> ---
Hello Nikolay,
--- quote ---
It still doesn't work, so I'm not sure if it make sense to close this. Unless
someone will open next one.
--- quote ---
well, I'm sure you know how it should be.
Meta bugs dealing with multiple underlying issues (missing
infrastructure/interfaces, stubs, method implementations) just for the sake of
"make my app work" should be avoided.
If people don't follow-up then let it be.
At one point the missing infrastructure will be implemented and apps
"magically" start to work - the progress will be untracked though.
If you are personally interested on tracking the progress in detail, create
follow-ups as needed (as I do).
Reading the history ... unfortunately even long timers have a different opinion
on this:
Austin:
--- quote ---
I would disagree. The original bug says the video demo doesn't work. This bug
may be fixed, or it could be hidden by a new bug. I'd say leave this open until
the demo works, then close it out.
--- quote ---
But do as you want, reopen. I personally don't like this "meta" approach.
Just imagine if everyone takes this approach - you end up with potentially
thousands of "make my app/game X to work" tickets which results in a mess
(overlapping underlying/individual issues, regressing each other).
Regards
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=8712
--- Comment #55 from Nikolay Sivov <bunglehead(a)gmail.com> ---
It still doesn't work, so I'm not sure if it make sense to close this. Unless
someone will open next one.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.