[Bug 1934616] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1934616/+attachment/5509443/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1934616/+attachment/5509442/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] Re: qterminal doesn't use correct .bashrc
apport information ** Tags added: apport-collected ** Description changed: Ubuntu 20.04.2 LTS mate-terminal 1.24.0-2ubuntu1 I'm in the process of cleaning up my $HOME. Part of this process was to move all of bash's "junk" into XDG BaseDir compliant locations by specifying in .profile to look at $XDG_CONFIG_HOME/bash/ for the .bashrc file, etc. bash itself is handling the move just fine (e.g. it outputs its history to ~/.local/share/bash/history as commanded). I can go into a TTY and use aliases I specifically put into the new .bashrc (located at ~/.config/bash/.bashrc), etc. The problem is when I try to use said aliases in qterminal, it refuses to recognize this change and use the proper .bashrc. Attached is my ~/.profile for reference. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: MATE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2018-12-05 (944 days ago) + InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + NonfreeKernelModules: nvidia_modeset nvidia + Package: qterminal + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-77.86-lowlatency 5.4.119 + Tags: focal + Uname: Linux 5.4.0-77-lowlatency x86_64 + UpgradeStatus: Upgraded to focal on 2021-06-18 (17 days ago) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1934616/+attachment/5509441/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] Re: qterminal doesn't use correct .bashrc
I added mate-terminal as being affected as well, as I just attempted it there, and have the same issue. ** Description changed: Ubuntu 20.04.2 LTS - qterminal 0.14.1-0ubuntu2 (universe, amd64) + mate-terminal 1.24.0-2ubuntu1 I'm in the process of cleaning up my $HOME. Part of this process was to move all of bash's "junk" into XDG BaseDir compliant locations by specifying in .profile to look at $XDG_CONFIG_HOME/bash/ for the .bashrc file, etc. bash itself is handling the move just fine (e.g. it outputs its history to ~/.local/share/bash/history as commanded). I can go into a TTY and use aliases I specifically put into the new .bashrc (located at ~/.config/bash/.bashrc), etc. The problem is when I try to use said aliases in qterminal, it refuses to recognize this change and use the proper .bashrc. I'm sure this is an "upstream" issue, but their GitHub issue tracker essentially tells Ubuntu users to file issues here instead. Attached is my ~/.profile for reference. ** Description changed: Ubuntu 20.04.2 LTS mate-terminal 1.24.0-2ubuntu1 I'm in the process of cleaning up my $HOME. Part of this process was to move all of bash's "junk" into XDG BaseDir compliant locations by specifying in .profile to look at $XDG_CONFIG_HOME/bash/ for the .bashrc file, etc. bash itself is handling the move just fine (e.g. it outputs its history to ~/.local/share/bash/history as commanded). I can go into a TTY and use aliases I specifically put into the new .bashrc (located at ~/.config/bash/.bashrc), etc. The problem is when I try to use said aliases in qterminal, it refuses to recognize this change and use the proper .bashrc. - I'm sure this is an "upstream" issue, but their GitHub issue tracker - essentially tells Ubuntu users to file issues here instead. - Attached is my ~/.profile for reference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934616] [NEW] qterminal doesn't use correct .bashrc
Public bug reported: Ubuntu 20.04.2 LTS mate-terminal 1.24.0-2ubuntu1 I'm in the process of cleaning up my $HOME. Part of this process was to move all of bash's "junk" into XDG BaseDir compliant locations by specifying in .profile to look at $XDG_CONFIG_HOME/bash/ for the .bashrc file, etc. bash itself is handling the move just fine (e.g. it outputs its history to ~/.local/share/bash/history as commanded). I can go into a TTY and use aliases I specifically put into the new .bashrc (located at ~/.config/bash/.bashrc), etc. The problem is when I try to use said aliases in qterminal, it refuses to recognize this change and use the proper .bashrc. Attached is my ~/.profile for reference. ** Affects: mate-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: qterminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "profile-copy" https://bugs.launchpad.net/bugs/1934616/+attachment/5509031/+files/profile-copy ** Also affects: mate-terminal (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/1934616 Title: qterminal doesn't use correct .bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1934616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808882] [NEW] false positive on tcpd
Public bug reported: This has apparently been a thing since at least 16.04 Install a clean version of Ubuntu, install chkrootkit, run a check. tcpd will report as infected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chkrootkit 0.52-1 ProcVersionSignature: Ubuntu 4.15.0-42.45-lowlatency 4.15.18 Uname: Linux 4.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Mon Dec 17 18:30:29 2018 InstallationDate: Installed on 2018-12-05 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: chkrootkit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chkrootkit (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/1808882 Title: false positive on tcpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/1808882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807617] [NEW] w3m won't use feh to open images
Public bug reported: It seems that, even though the option is set to use feh to open images, w3m will use just about any application *but* feh to do so. When I set the option to "feh", it originally used my DE's image viewer (eye of MATE). I specifically set my "Preferred Applications" to use feh as its image viewer, and no change. I then uninstalled eom completely, and now w3m opens Firefox (a private window) or sometimes GIMP (GIMP for some png files - but not always, apparently), instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: w3m 0.5.3-36build1 ProcVersionSignature: Ubuntu 4.15.0-42.45-lowlatency 4.15.18 Uname: Linux 4.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 9 16:46:09 2018 InstallationDate: Installed on 2018-12-05 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: w3m UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: w3m (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic feh w3m ** Description changed: It seems that, even though the option is set to use feh to open images, w3m will use just about any application *but* feh to do so. When I set the option to "feh", it originally used my DE's image viewer (eye of MATE). I specifically set my "Preferred Applications" to use feh as its image viewer, and no change. I then uninstalled eom completely, and now - w3m opens Firefox of GIMP (GIMP for png files, apparently), instead. + w3m opens Firefox (a private window) of GIMP (GIMP for png files, + apparently), instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: w3m 0.5.3-36build1 ProcVersionSignature: Ubuntu 4.15.0-42.45-lowlatency 4.15.18 Uname: Linux 4.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 9 16:46:09 2018 InstallationDate: Installed on 2018-12-05 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: w3m UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: It seems that, even though the option is set to use feh to open images, w3m will use just about any application *but* feh to do so. When I set the option to "feh", it originally used my DE's image viewer (eye of MATE). I specifically set my "Preferred Applications" to use feh as its image viewer, and no change. I then uninstalled eom completely, and now - w3m opens Firefox (a private window) of GIMP (GIMP for png files, - apparently), instead. + w3m opens Firefox (a private window) or sometimes GIMP (GIMP for some + png files - but not always, apparently), instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: w3m 0.5.3-36build1 ProcVersionSignature: Ubuntu 4.15.0-42.45-lowlatency 4.15.18 Uname: Linux 4.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 9 16:46:09 2018 InstallationDate: Installed on 2018-12-05 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: w3m 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/1807617 Title: w3m won't use feh to open images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/w3m/+bug/1807617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768669] Re: multiverse package steam recommends nvidia-driver-lib-i386:i386 which is not in repositories
** Description changed: Running Ubuntu Studio 18.04 - When running sudo apt install steam, it - recommends installing nvidia-driver-lib-i386:i386, which is not in the + recommends installing nvidia-driver-libS-i386:i386, which is not in the repositories. The steam version being attempted is 1.0.0.54+repack-5ubuntu1 from the multiverse repos. Terminal output is below: ryan@tesla:~$ sudo apt install steam Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following additional packages will be installed: - libgl1-mesa-glx:i386 libglx-mesa0:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxdamage1:i386 libxshmfence1:i386 libxss1:i386 + libgl1-mesa-glx:i386 libglx-mesa0:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxdamage1:i386 libxshmfence1:i386 libxss1:i386 Suggested packages: - steam-devices:i386 + steam-devices:i386 Recommended packages: - nvidia-driver-libs-i386:i386 + nvidia-driver-libs-i386:i386 The following NEW packages will be installed: - libgl1-mesa-glx:i386 libglx-mesa0:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxdamage1:i386 libxshmfence1:i386 libxss1:i386 - steam:i386 + libgl1-mesa-glx:i386 libglx-mesa0:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxdamage1:i386 libxshmfence1:i386 libxss1:i386 + steam:i386 0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 1,539 kB of archives. After this operation, 5,252 kB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. ryan@tesla:~$ sudo apt install steam nvidia-driver-libs-i386:i386 Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done Package nvidia-driver-libs-i386:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'nvidia-driver-libs-i386:i386' has no installation candidate ryan@tesla:~$ sudo apt install steam nvidia-driver-libs-i386 Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done Package nvidia-driver-libs-i386:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'nvidia-driver-libs-i386:i386' has no installation candidate ** Description changed: Running Ubuntu Studio 18.04 - When running sudo apt install steam, it - recommends installing nvidia-driver-libS-i386:i386, which is not in the + recommends installing nvidia-driver-libs-i386:i386, which is not in the repositories. The steam version being attempted is 1.0.0.54+repack-5ubuntu1 from the multiverse repos. Terminal output is below: ryan@tesla:~$ sudo apt install steam Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libgl1-mesa-glx:i386 libglx-mesa0:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxdamage1:i386 libxshmfence1:i386 libxss1:i386 Suggested packages: steam-devices:i386 Recommended packages: nvidia-driver-libs-i386:i386 The following NEW packages will be installed: libgl1-mesa-glx:i386 libglx-mesa0:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxdamage1:i386 libxshmfence1:i386 libxss1:i386 steam:i386 0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 1,539 kB of archives. After this operation, 5,252 kB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. ryan@tesla:~$ sudo apt install steam nvidia-driver-libs-i386:i386 Reading package lists... Done Building dependency tree Reading state information... Done Package nvidia-driver-libs-i386:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'nvidia-driver-libs-i386:i386' has no installation candidate ryan@tesla:~$ sudo apt install steam nvidia-driver-libs-i386 Reading package lists... Done Building dependency tree Reading state information... Done Package nvidia-driver-libs-i386:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from
[Bug 1768669] [NEW] multiverse package steam recommends nvidia-driver-lib-i386:i386 which is not in repositories
Public bug reported: Running Ubuntu Studio 18.04 - When running sudo apt install steam, it recommends installing nvidia-driver-lib-i386:i386, which is not in the repositories. The steam version being attempted is 1.0.0.54+repack-5ubuntu1 from the multiverse repos. Terminal output is below: ryan@tesla:~$ sudo apt install steam Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libgl1-mesa-glx:i386 libglx-mesa0:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxdamage1:i386 libxshmfence1:i386 libxss1:i386 Suggested packages: steam-devices:i386 Recommended packages: nvidia-driver-libs-i386:i386 The following NEW packages will be installed: libgl1-mesa-glx:i386 libglx-mesa0:i386 libx11-xcb1:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxdamage1:i386 libxshmfence1:i386 libxss1:i386 steam:i386 0 upgraded, 12 newly installed, 0 to remove and 0 not upgraded. Need to get 1,539 kB of archives. After this operation, 5,252 kB of additional disk space will be used. Do you want to continue? [Y/n] n Abort. ryan@tesla:~$ sudo apt install steam nvidia-driver-libs-i386:i386 Reading package lists... Done Building dependency tree Reading state information... Done Package nvidia-driver-libs-i386:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'nvidia-driver-libs-i386:i386' has no installation candidate ryan@tesla:~$ sudo apt install steam nvidia-driver-libs-i386 Reading package lists... Done Building dependency tree Reading state information... Done Package nvidia-driver-libs-i386:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'nvidia-driver-libs-i386:i386' has no installation candidate ** Affects: steam (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/1768669 Title: multiverse package steam recommends nvidia-driver-lib-i386:i386 which is not in repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1768669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768603] [NEW] All review score averages are 5 Stars - 1 Star reviews show as 5 Star
Public bug reported: OS: Ubuntu Studio 18.04 Bionic Beaver (Comes with: DE - XFCE4 Version of application: 3.28.1-0ubuntu4) Looking in the Gnome Software application, all applications with any ratings show as 5-star. One-star reviews show as 5-star in the reviews section. An easy example to demonstrate this issue is to look at the entry for WINE. 5 Star Reviews (x24) 4 Star Reviews (x9) 3 Star Reviews (x5) 2 Star Reviews (x11) 1 Star Reviews (x45) Overall average - 5 Stars. Scrolling down to read individual reviews shows five stars for obviously negative reviews: (5 Star Rating) Title: Doesn't work (5 Star Rating) Title: Garbage ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768603 Title: All review score averages are 5 Stars - 1 Star reviews show as 5 Star To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1768603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762360] Re: EVGA GeForce GTX 1060 - nouveau symbol lookup error causes X failure
** Tags added: ubuntustudio-beta ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762360 Title: EVGA GeForce GTX 1060 - nouveau symbol lookup error causes X failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1762360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762360] [NEW] EVGA GeForce GTX 1060 - nouveau symbol lookup error causes X failure
Public bug reported: Fresh install of Ubuntu Studio 18.04 - xorg crashes just after login and returns to lightdm. Moving to a TTY and attempting to startx returns the following: /usr/lib/Xorg: symbol lookup error: /usr/lib/xorg/modules/drivers/nouveau_drv.so: undefined symbol: exaGetPixmapDriverPrivate Installing nvidia-driver-390 and rebooting resolves the issue. apt update && apt full-upgrade performed @ 03:54 EDT (I didn't think to check which versions the updates were at, as there were something like 145 of them) GPU:EVGA Nvidia GeForce GTX 1060 6GB Kernel: 4.15.0-13-lowlatency OS: Ubuntu Studio 18.04 Bionic CPU:Intel Core i5-4690K @ 3.5GHz ** Affects: xserver-xorg-video-nouveau (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/1762360 Title: EVGA GeForce GTX 1060 - nouveau symbol lookup error causes X failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1762360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696844] Re: Calendar sync with google - time zone data is incorrect
I do not believe this is an Ubuntu issue, or a bug, for that matter. I had the same problem with my Google/Evolution calendar sync. This is what fixed the problem for me: -Edit > Preferences > Calendar and Tasks -Uncheck "Use system time zone (UTC)" -Select your time zone in the next field (Click the Select button to the right) This solved the issue for me. If I misunderstood your post, however, please let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696844 Title: Calendar sync with google - time zone data is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/696844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 406626] Re: Deleted Items Folder inconsistently named in en_GB localization
Bryant, It was sent to the Docs team in general -- not you specifically. I'm new also and was just as confused when I first got the email :) On Sat, Jul 31, 2010 at 1:48 PM, Bryant Lippert wrote: > Vish, > > I'm new to the Ubuntu Docs group. I was just assigned this new task with > you > guys, but I'm not sure how to get this started, or where to log in. I was > trying to find someone under the Ubuntu mentoring program. Any information > you could off I would appreciate! > > - Bryant > > On Fri, Jul 30, 2010 at 8:00 AM, Vish wrote: > > > @Phil , I had emailed Martin Meredith, a couple of weeks ago, to take a > > decision on this bug. > > But haven't heard back from him yet. > > > > There seems to be no consensus on this. Let's just pick one and get this > > fixed for Maverick :-) > > > > Assigning to docs team as per Phil's suggestion > > > > ** Changed in: ubuntu > > Importance: Undecided => Low > > > > -- > > Deleted Items Folder inconsistently named in en_GB localization > > https://bugs.launchpad.net/bugs/406626 > > You received this bug notification because you are a member of Ubuntu > > Documentation Project Team, which is a bug assignee. > > > > Status in GNOME Common Scripts: Unknown > > Status in One Hundred Paper Cuts: Triaged > > Status in Ubuntu: Triaged > > > > Bug description: > > The deleted items folder is inconsistently named and is referred to as > both > > Wastebasket and Deleted items, Ubuntu offers to 'Empty Deleted Items' but > > the window is headed Wastebasket. The URL to deleted items is also > trash:/// > > in nautilus but this is possibly a seperate issue. An effect of this can > be > > seen in #115661 also. > > > > This could confuse new users and it should be a simple enough fix simply > > changing strings, so I believe it is a papercut. > > > > - > > Quoting MPT , see comment #15 for more details: > > "trash" is, in UK English, far and away more common than "rubbish bin", > > "wastebin", or "wastebasket". > > - > > (The accuracy of this statement is questioned, see comment #28 onwards > and > > https://wiki.ubuntu.com/EnglishTranslation/WordSubstitution given in > > comment #8.) > > > > > > > > > > -- > Deleted Items Folder inconsistently named in en_GB localization > https://bugs.launchpad.net/bugs/406626 > You received this bug notification because you are a member of Ubuntu > Documentation Project Team, which is a bug assignee. > > Status in GNOME Common Scripts: Unknown > Status in One Hundred Paper Cuts: Triaged > Status in Ubuntu: Triaged > > Bug description: > The deleted items folder is inconsistently named and is referred to as both > Wastebasket and Deleted items, Ubuntu offers to 'Empty Deleted Items' but > the window is headed Wastebasket. The URL to deleted items is also trash:/// > in nautilus but this is possibly a seperate issue. An effect of this can be > seen in #115661 also. > > This could confuse new users and it should be a simple enough fix simply > changing strings, so I believe it is a papercut. > > - > Quoting MPT , see comment #15 for more details: > "trash" is, in UK English, far and away more common than "rubbish bin", > "wastebin", or "wastebasket". > - > (The accuracy of this statement is questioned, see comment #28 onwards and > https://wiki.ubuntu.com/EnglishTranslation/WordSubstitution given in > comment #8.) > > > > -- Deleted Items Folder inconsistently named in en_GB localization https://bugs.launchpad.net/bugs/406626 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
