[Bug 1892859] Re: short date is not sent through to app in playinlinux
Turns out this is the version of wine causing the issue, I have logged a bug at https://bugs.winehq.org/show_bug.cgi?id=49827 As far as Ubuntu goes, is it worth setting the default version of wine back to 3.x or are the new features more important than a date? Anyone doing any accounting or other date related things in wine that is not in the en_US locale (anything but MM/dd/yyy) is going to have massive issues with it. ** Bug watch added: Wine Bugzilla #49827 https://bugs.winehq.org/show_bug.cgi?id=49827 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892859 Title: short date is not sent through to app in playinlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/playonlinux/+bug/1892859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892859] Re: short date is not sent through to app in playinlinux
** Description changed: I had Ubuntu 20.04 installed and was using MYOB in Playonlinux to do my accounting and it all ran fine. I had a number of issues in Ubuntu (screens and stability mostly) and when it refused to boot one day and Ubuntu 20.04.1 had just been released, I decided to install it instead. Fixed all my Ubuntu issues, but then had some weird issues in MYOB. The main one is that the date format is MM/d/yy, where in Australia it should be dd/MM/yy. I researched MYOB (this in MYOB 19) and found it gets the date format from the Windows short date. Looking into the date format in wine, I went into the registry setting - for short date, but it was set correctly (not sure, but this may come - from Ubuntu?), so it seems that is not being sent through. I tried - different versions of Wine, but in the end did a total reinstall of - Ubuntu and still had the same issue. So not sure if this is something - that changed in Ubuntu 20.04 > 20.04.1 or if its a different version of - playinlinux and the one in 20.04.1 repository (used the default one in - the repo) has a bug or if its something to do with Wine. + (see answer at https://askubuntu.com/questions/474900/change-date- + format-for-wine-windows-software) for short date, but it was set + correctly (not sure, but this may come from Ubuntu?), so it seems that + is not being sent through. I tried different versions of Wine, but in + the end did a total reinstall of Ubuntu and still had the same issue. So + not sure if this is something that changed in Ubuntu 20.04 > 20.04.1 or + if its a different version of playinlinux and the one in 20.04.1 + repository (used the default one in the repo) has a bug or if its + something to do with Wine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: playonlinux 4.3.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 20:42:05 2020 InstallationDate: Installed on 2020-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: playonlinux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892859 Title: short date is not sent through to app in playinlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/playonlinux/+bug/1892859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892859] Re: short date is not sent through to app in playinlinux
** Description changed: I had Ubuntu 20.04 installed and was using MYOB in Playonlinux to do my accounting and it all ran fine. I had a number of issues in Ubuntu (screens and stability mostly) and when it refused to boot one day and Ubuntu 20.04.1 had just been released, I decided to install it instead. Fixed all my Ubuntu issues, but then had some weird issues in MYOB. The main one is that the date format is MM/d/yy, where in Australia it should be dd/MM/yy. I researched MYOB (this in MYOB 19) and found it gets the date format from the Windows short date. Looking into the date format in wine, I went into the registry setting for short date, but it was set correctly (not sure, but this may come from Ubuntu?), so it seems that is not being sent through. I tried different versions of Wine, but in the end did a total reinstall of Ubuntu and still had the same issue. So not sure if this is something that changed in Ubuntu 20.04 > 20.04.1 or if its a different version of playinlinux and the one in 20.04.1 repository (used the default one in the repo) has a bug or if its something to do with Wine. - I also noticed in the past that I just had a PDF printer available in - MYOB, there is still a print to file in Ubuntu, but MYOB says there are - no printers available now (it used to print to ~/PDF from in MYOB in - Playonlinux). So seems something between Ubuntu 20.04.1 and playonlinux - is not happy! - ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: playonlinux 4.3.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 20:42:05 2020 InstallationDate: Installed on 2020-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: - LANGUAGE=en_AU:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_AU.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_AU:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_AU.UTF-8 + SHELL=/bin/bash SourcePackage: playonlinux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892859 Title: short date is not sent through to app in playinlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/playonlinux/+bug/1892859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892859] [NEW] short date is not sent through to app in playinlinux
Public bug reported: I had Ubuntu 20.04 installed and was using MYOB in Playonlinux to do my accounting and it all ran fine. I had a number of issues in Ubuntu (screens and stability mostly) and when it refused to boot one day and Ubuntu 20.04.1 had just been released, I decided to install it instead. Fixed all my Ubuntu issues, but then had some weird issues in MYOB. The main one is that the date format is MM/d/yy, where in Australia it should be dd/MM/yy. I researched MYOB (this in MYOB 19) and found it gets the date format from the Windows short date. Looking into the date format in wine, I went into the registry setting for short date, but it was set correctly (not sure, but this may come from Ubuntu?), so it seems that is not being sent through. I tried different versions of Wine, but in the end did a total reinstall of Ubuntu and still had the same issue. So not sure if this is something that changed in Ubuntu 20.04 > 20.04.1 or if its a different version of playinlinux and the one in 20.04.1 repository (used the default one in the repo) has a bug or if its something to do with Wine. I also noticed in the past that I just had a PDF printer available in MYOB, there is still a print to file in Ubuntu, but MYOB says there are no printers available now (it used to print to ~/PDF from in MYOB in Playonlinux). So seems something between Ubuntu 20.04.1 and playonlinux is not happy! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: playonlinux 4.3.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 20:42:05 2020 InstallationDate: Installed on 2020-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: playonlinux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: playonlinux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892859 Title: short date is not sent through to app in playinlinux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/playonlinux/+bug/1892859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791283] [NEW] Cannot open files in required application with double click or open with in ftp Nautilus
Public bug reported: For more information, see https://askubuntu.com/questions/964747/cannot- open-text-editor-with-double-click-in-ftp-nautilus/1067423#1067423 When an FTP server is open in Nautilus and a file is either double clicked or right clicked and opened with (and app chosen from the menu), it always downloads the files with the default browser, rather than open in the requested application. One of the times this becomes a massive issue is when you are connected to an ftp web server and want to test changes in code live. This means you now have to download the file, open it, edit it, and re-upload. In the past for minor changes or in a test environment, it has been WAY faster to open the file directly in a txt editor, then just save and see the changes instantly. This is still working in Ubuntu 16.04. I have it failing in 18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 20:57:42 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x541+217+129'" InstallationDate: Installed on 2018-08-25 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791283 Title: Cannot open files in required application with double click or open with in ftp Nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1791283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719500] Re: 17.10 Black screen pre and post login on virtualbox
This can be closed, but I'm not sure how to do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719500 Title: 17.10 Black screen pre and post login on virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1719500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719500] Re: 17.10 Black screen pre and post login on virtualbox
Appears to have been resolved in the latest daily build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719500 Title: 17.10 Black screen pre and post login on virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1719500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719500] Re: 17.10 Black screen pre and post login on virtualbox
Have added 2 packages it may affect, I really am not sure which packages it would affect so if anyone else has any idea please edit as needed. ** Package changed: ubuntu => gdm3 (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719500 Title: 17.10 Black screen pre and post login on virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1719500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
Done https://bugs.launchpad.net/ubuntu/+bug/1719500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719500] [NEW] 17.10 Black screen pre and post login on virtualbox
Public bug reported: I have been testing the daily builds from http://cdimage.ubuntu.com /daily-live/current/HEADER.html on virtualbox (https://www.virtualbox.org/) in a windows host. I originally installed it a few weeks ago, and would do an apt update and apt upgrade every day to get the latest changes. Then when I did an upgrade about a week ago, I ran into these issues. I tried downloading the new image every day since (although it looks like that image has not changed in the past week or so anyhow), and it installs fine, I can log in fine, but once I do the apt update and reboot, I get a black screen where I should see the login. Steps I made to replicate (can someone else verify the same thing happens?): - Install virtual box 5.1.28 - Create a new vm (4GB ram, 10GB hdd) - Insert and install the image daily 17.10 image (from link above) - Boot to login screen, log in and load to desktop - Do a sudo apt update and a sudo apt upgrade - At this point it sometimes comes up with the prompt to reboot, either way, reboot - You will find a black screen when you should see the login screen (if you move your mouse over or click you can see random white pixels around) - Before moving the mouse or pressing any keys, press enter, enter password, press enter again (as you would do normally to log in) - For a second the console screen (sometimes purple background, sometimes black background) shows some feedback - Once booted into desktop, all is black again (with random white pixels sometimes) I do not have a PC available at the moment to test on, and haven't had a chance to test in a vm with a Ubuntu host (or any other host). Ubuntu 16.04 has been working in another vm on the same machine for ages, and 17.10 was working until recently. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719500 Title: 17.10 Black screen pre and post login on virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1719500/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705369] Re: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
I have installed 17.10 in a virtual box (have an nvidia card in my pc, not sure what virtual box detects as, in a windows host), and been updating it daily to check out the 17.10 progression. It was fine for a few weeks, but then about a week ago I would install, and then boot - all good, and then I would do an apt update and upgrade. Once I reboot after an upgrade, I get a black login, then if I press enter, enter my password and press enter again, I get the brief screen with text (like when it worked) and then black again. I'm thinking this is the same issue? Or in this issue is everyone booting to black immediately after install? I have been downloading the daily builds, so it's not an old image I am installing from. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321421] Re: 8086:8ca0 Sound output distorted/unusable with Intel Z97/H97
@daniel, thanks for that. I think even though there are fixes, its not a simple procedure (especially for new ubuntu users) as some fixes work for some people but not others. @dogmatic do this in terminal: Sudo gedit /etc/modprobe.d/alsa-base.conf And add the line: options snd-hda-intel vid=8086 pid=8ca0 snoop=0 Save, exit, reboot. That fixed it for me. Fixed starcraft and everything! The reason it took me a while to update what fixes it is the sound stopped working all together. Took me a while (and a total reinstall) to realise it was the duel boot to windows (2 seperate hdds). Windows wont give anything else access to the soundcard! So for anyone with this chipset duel booting, simple solution, dont restart from windows to boot into ubuntu, shut down and power up again. If this still fails, unplug the computer (or if a laptop take the battery out) for 15sec, plug it back in AND WAIT 15SEC, then boot into ubuntu and see if it works. This is for if the sound doesn't work at all, for the skipping and scratchy sound, add the line to alsa-base.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321421 Title: 8086:8ca0 Sound output distorted/unusable with Intel Z97/H97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321421] Re: 8086:8ca0 Sound output distorted/unusable with Intel Z97/H97
I forgot to add, why is this bug of low importance?? This is a pretty common codec, so it would be affecting a lot of users to the extent where they can't use their sound! I think this needs a higher priority, mainly because of the number of users affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321421 Title: 8086:8ca0 Sound output distorted/unusable with Intel Z97/H97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321421] Re: 8086:8ca0 Sound output distorted/unusable with Intel Z97/H97
I have a Gigabyte H97-D3H motherboard (http://www.gigabyte.com.au/products/product-page.aspx?pid=4962#sp) that says it has the Realtek® ALC1150 codec. I get this same issue. It seems random, sometimes working for a while and sometimes skipping constantly and going scratchy. I installed starcraft 2 through playonlinux and the entire audio seemed stuffed (seemingly the same problem but a lot worse) except for a few small bits that got through. My problem seems to get worse the more that the computer is doing (which would also explain why a game under wine would have more issues). I have not tried the above solutions yet, however, as soon as I boot back into Ubuntu (14.04LTS) I will give them a go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321421 Title: 8086:8ca0 Sound output distorted/unusable with Intel Z97/H97 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329201] [NEW] Onboard graphics takes priority over card
Public bug reported: When I went to install ubuntu 14.04 on my new system (and tested 13.10 and 12.04), it seemed to be failing (black screen or flashing cursor). I did a few things, but ended up discovering that it was loading on the onboard video, not the card I was plugged into. In the BIOS, the Nvidia GTX750 was selected as default, for some reason, Ubuntu is not following this. Once I disabled the onboard card, everything worked as expected! This could be a headache for a lot of people, and I think it could be solved easily with an option of what video card is to be used (this would be done at the same place nomodeset is done, but not have to press any key to bring it up), or to be able to detect BIOS settings. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329201 Title: Onboard graphics takes priority over card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1329201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007508] Re: [Gigabyte GA-870A-USB3] Unable to boot without workarounds
Can you try a disk for 12.04.3? (http://old- releases.ubuntu.com/releases/precise/) I had a similar issue, and found it happened on Ubuntu 12.04.4 and later, as well as new versions of Lubuntu, but not on Lubuntu 12.04. Tested Ubuntu 12.04.3, and it seems to work. Im guessing it is something in the kernel upgrade that happened 12.04.3 - 12.04.4. Hope this can help, I would love to get the supported version of 12.04 running on my old sony vaio. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007508 Title: [Gigabyte GA-870A-USB3] Unable to boot without workarounds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1007508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
