[PATCH] doc: improve tr --help

* src/tr.c (usage): Remove ungrammatical comma from documentation of --squeeze-repeats option. Explain that SET2 is only extended to the length of SET1 when -t option is not given. --- src/tr.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/src/tr.c b/src/tr.c

bug#40929: go-sctp build failure: "protocol not supported"

This now builds fine (in fact, it was substituted when I checked just now, but `guix build --check` works with no errors). -- Josh Holland

Bundler 2

packages for both Bundler 1 and Bundler 2, or would just Bundler 2 be sufficient? I'll still write a definition for the new version, but I'll hold off submitting a patch until I've had some feedback. [0]: https://bundler.io/blog/2019/01/03/announcing-bundler-2.html Thanks, -- Josh Holland

bug#40929: go-sctp build failure: "protocol not supported"

7;t essential to me. If it is fixed, then presumably this bug can be closed? Thanks, -- Josh Holland

bug#40929: go-sctp build failure: "protocol not supported"

v' failed with exit code 1 build of /gnu/store/bc4sd2819gmy22dda1nhd179cacw7ny6-go-sctp-0.0.0-1.07191f8.drv failed View build log at '/var/log/guix/drvs/bc/4sd2819gmy22dda1nhd179cacw7ny6-go-sctp-0.0.0-1.07191f8.drv.bz2'. guix build: error: build of `/gnu/store/bc4sd2819gmy22dda1nhd179cacw7ny6-go-sctp-0.0.0-1.07191f8.drv' failed I am running Guix on top of a foreign distro (Arch); I looked up some recent builds of go-sctp on the CI server, with rather mixed results. Some have succeeded, some failed, some never attempted (due to missing dependencies, I assume), and most seem to have the output cut off. -- Josh Holland

bug#40388: Reported upstream to Calibre

oid in this case. -- Josh Holland

bug#40388: Calibre test suite fails

on-msgpack was updated to version 1.0.0. [0]: e.g. http://ci.guix.gnu.org/build/2485977/details -- Josh Holland

Re: Redshift and Geoclue

Hi Guix! Pierre Neidhardt writes: > Anyone using redshift on Guix? I am, but I hadn't got round to investigating geoclue yet so I'm just using -l and a hardcoded lat/long pair. -- Josh Holland

[issue39090] Document various options for getting the absolute path from pathlib.Path objects

Change by Josh Holland : -- nosy: +anowlcalledjosh ___ Python tracker <https://bugs.python.org/issue39090> ___ ___ Python-bugs-list mailing list Unsubscribe:

bug#36675: [PATCH] gnu: kodi: Disable intermittently failing test.

As reported in , occasionally the TestMassEvent.General test in kodi crashes with a mutex error. * gnu/packages/patches/kodi-skip-testmasseventgeneral.patch: New file. * gnu/packages/kodi.scm (kodi)[source]: Use it. * gnu/local.mk: (dist_patch_DATA): Add it

[Bug 1853609] [NEW] jpnevulator uses 100% cpu after resume

Public bug reported: If jpnevulator is left running while the system is suspended, it begins to consume 100% of CPU time on one core upon resume. The specific command line I'm using is: jpnevulator -r -a --tty /dev/ttyACM0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: jpnevulator 2.

[Desktop-packages] [Bug 1851997] [NEW] Typo in im-launch(1) man page

Public bug reported: im-launch(1) says: im-launch - launch input method end execute session program but should say: im-launch - launch input method and execute session program (s/end/and/) This is an upstream bug[1] which should be reported to Debian, but frankly I'm not up to dealing

[Bug 1851997] [NEW] Typo in im-launch(1) man page

Public bug reported: im-launch(1) says: im-launch - launch input method end execute session program but should say: im-launch - launch input method and execute session program (s/end/and/) This is an upstream bug[1] which should be reported to Debian, but frankly I'm not up to dealing

bug#38005: Acknowledgement (org.gtk.Settings.FileChooser glib schema missing "show-type-column" key)

I just checked, and in fact staging already has 3.24.12, which contains the missing key. So I suppose this will be resolved when staging gets merged. Thanks, -- Josh Holland

bug#38005: org.gtk.Settings.FileChooser glib schema missing "show-type-column" key

le update of the gtk+ package would solve this, especially as presumably it would trigger a lot of rebuilds. -- Josh Holland

bug#37989: python2-numpy v0.17.3 fails to build

e the upstream commit badf2901: https://github.com/numpy/numpy/commit/badf2901ea040aa89dbb3c19e53c6b1b692cb489 Lots of packages including libreoffice transitively depend on python2-numpy, so this needs some sort of resolution — perhaps simply pinning python2-numpy to a previous version? However, P

bug#37662: substitution failure of nss-certs

profile/lib/locale/*/en_GB.UTF-8 LC_ADDRESS LC_CTYPE LC_MEASUREMENT LC_MONETARY LC_NUMERIC LC_TELEPHONE LC_COLLATE LC_IDENTIFICATION LC_MESSAGES LC_NAME LC_PAPERLC_TIME --8< -- Josh Holland

bug#37662: substitution failure of nss-certs

ale GUIX=/gnu/store/f2zvgl9zz13r6rp89y0jjfj9f4jk5h9s-guix-command GUIX_STATE_DIRECTORY=/var/guix GUIX_CONFIGURATION_DIRECTORY=/etc/guix NIX_STORE_DIR=/gnu/store -- Josh Holland

bug#37662: substitution failure of nss-certs

Hi Arun, Arun Isaac writes: > I install glibc-locales as a system-wide package in my operating-system > configuration. Perhaps that's what Ludo meant to say. I probably should have mentioned in my initial report that this is Guix running on top of a foreign distro (Arch). -- Josh Holland

bug#37662: substitution failure of nss-certs

;s possible - I rarely do anything with the root profile, and wasn't even aware that I had to keep it up to date. Should I have to `guix pull` and `guix upgrade` it regularly, as well as my user profile? -- Josh Holland

bug#36965: Streamlink now works fine

Hi, Streamlink got updated recently and it now works fine, so this bug can be closed (not sure if I can do it or how to do it myself through debbugs). -- Josh Holland

bug#37662: substitution failure of nss-certs

mand did then complete successfully, I assume building nss-certs locally instead, though I can't see any further references to it in the output. I'm currently trying the same thing on my other computer. -- Josh Holland

bug#37437: hash mismatch for emacs-elixir-mode

e built guix install: error: build of `/gnu/store/xqdxvb7xy4ydpwkqgp3jd985qb4vw8k2-emacs-elixir-mode-2.3.1.drv' failed Is something nefarious going on, or have upstream just changed their tarballs? Thanks, -- Josh Holland

[issue37814] typing module: empty tuple syntax is undocumented

Change by Josh Holland : -- pull_requests: +14981 pull_request: https://github.com/python/cpython/pull/15262 ___ Python tracker <https://bugs.python.org/issue37

[issue37814] typing module: empty tuple syntax is undocumented

Josh Holland added the comment: PEP 586 doesn't currently allow Literal to contain tuples, so Tuple[()] is the only option. -- ___ Python tracker <https://bugs.python.org/is

[issue37814] typing module: empty tuple syntax is undocumented

Change by Josh Holland : -- keywords: +patch pull_requests: +14937 stage: -> patch review pull_request: https://github.com/python/cpython/pull/15208 ___ Python tracker <https://bugs.python.org/issu

[issue37814] typing module: empty tuple syntax is undocumented

New submission from Josh Holland : The empty tuple syntax in type annotations, `Tuple[()]`, is not obvious from the examples given in the documentation (I naively expected `Tuple[]` to work); it has been documented in PEP 484[1] and in mypy[2], but not in the documentation for the typing

[Touch-packages] [Bug 1839533] [NEW] .whl/.egg support in lesspipe is undocumented

Public bug reported: Support for .whl/.egg files (used in Python packaging) was added to lesspipe in version 487-0.1 of less[1], but the lesspipe(1) manual page was apparently not updated at the time, and does not currenly list .whl/.egg as supported file types. This looks like a Debian bug, sinc

[Bug 1839533] [NEW] .whl/.egg support in lesspipe is undocumented

Public bug reported: Support for .whl/.egg files (used in Python packaging) was added to lesspipe in version 487-0.1 of less[1], but the lesspipe(1) manual page was apparently not updated at the time, and does not currenly list .whl/.egg as supported file types. This looks like a Debian bug, sinc

bug#36965: streamlink fails to run

ach a patch for the former if required, but I'd rather get to the bottom of this error before making any changes. -- Josh Holland

bug#36675: Same build failure with kodi 18.3

...and just to confirm that this is some annoyingly unreproducible race condition, the very next try to build that same z1zswg derivation completed fine. -- Josh Holland

bug#36675: Same build failure with kodi 18.3

; exe="/tmp/guix-build-kodi-18.3.drv-0/build/kodi-test" sig=6 res=1 --8<-- -- Josh Holland

Re: A 'guix pull' option for 'manifest.scm' to be used in the next update

Hi Hubert, hub.lomb...@free.fr writes: > So maybe (I'm not sure) I can try, considering the path of my manifest.scm: > > $ guix pull && guix package -m ~/.config/guix/manifest.scm -u Yep, if that's the right path to where you saved your manifest file. (Note that the -u option, upgrade, takes a

Re: A 'guix pull' option for 'manifest.scm' to be used in the next update

Hi Hubert, hub.lomb...@free.fr writes: > In order for 'manifest.scm' to be used in the next update, should I do > something like this: > > $ guix pull -p, --profile=PROFILE > > (using PROFILE instead of ~/.config/guix/current) `guix pull` is not the command that you should

guix upgrade: packages to upgrade, but nothing to be done

ormed in the end? Thanks, Josh -- Josh Holland

bug#36675: Acknowledgement (kodi 18.2 fails to build)

I tried again just now, and: successfully built /gnu/store/pmq2jv9j9snmyzbdngmklghn9bpzrxig-kodi-18.2.drv /gnu/store/qzc0j7v4b4ylgqrk5n8h2dj5q5bp8qbf-kodi-18.2 It's definitely failed before a bunch of times when I've tried to do `guix upgrade`, so not sure what to make of it really

bug#36675: kodi 18.2 fails to build

from 1 test case ran. (276 ms total) [ PASSED ] 1 test. Clean shutdown of TestGlobalPattern1 kodi-test: ../nptl/pthread_mutex_lock.c:434: __pthread_mutex_lock_full: Assertion `robust || (oldval & FUTEX_OWNER_DIED) == 0' failed. --8<---------- -- Josh Holland

Re: bug#35780: [PATCH] attempt to fix polyglossia

to my surprise no polyglossia.sty is produced! There's no actual build instructions in the README or the polyglossia.pdf, so I'm rather lost here. Thanks, -- Josh Holland

bug#35780: [PATCH] attempt to fix polyglossia

to my surprise no polyglossia.sty is produced! There's no actual build instructions in the README or the polyglossia.pdf, so I'm rather lost here. Thanks, -- Josh Holland

[Bug 1832153] [NEW] game-data-packager fails to download wolf3d data

Public bug reported: As reported upstream at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=911788, game-data-packager version 58 attempts to download data for Wolfenstein 3D from http://pkg-games.alioth.debian.org /game-data/1wolf14.zip, which is no longer available since Alioth was shut down

Re: warning: setlocale: LC_ALL: cannot change locale on foreign distro

t appeared to be fixed just by installing glibc-utf8-profiles. > > I'll open bugs for each of these issues. Glad that these won't be a problem any more; thanks a lot! -- Josh Holland

setlocale: LC_ALL: cannot change locale (en_US.utf8)

on either of the two other machines I've installed Guix on, and not before I reinstalled. Does anybody have any ideas? -- Josh Holland

bug#35780: [PATCH] attempt to fix polyglossia

--- I had a quick look into fixing this myself, and made a little bit of progress. Not being that familiar with how things work yet, I'm going on what I can guess by looking at gnu/packages/tex.scm, guix/build-system/texlive.scm and guix/build/texlive-build-system.scm so I may well be misinterpret

bug#35780: texlive-latex-polyglossia package empty

Steps to reproduce: $ guix build texlive-latex-polyglossia $ tree /gnu/store/d9nndb33yd22pay1yyg76nb0i56qdmkq-texlive-latex-polyglossia-49435 Expected results: Something containing the file polyglossia.sty Actual results: Only an empty directory share/texmf-dist/tex/latex/polyglossia exists.

[Kernel-packages] [Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card

For anyone experiencing this issue with a Realtek RTL8411 card reader: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01) Subsystem: CLEVO/KAPOK Computer RTL8411B PCI Express Card Reader Flags: bus master, fast devsel, latenc

[Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card

For anyone experiencing this issue with a Realtek RTL8411 card reader: 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 01) Subsystem: CLEVO/KAPOK Computer RTL8411B PCI Express Card Reader Flags: bus master, fast devsel, latenc

[Kernel-packages] [Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card

Same issue here, also with a SanDisk Extreme microSD card (128GB). Possibly relevant: https://bugzilla.kernel.org/show_bug.cgi?id=202473 ** Bug watch added: Linux Kernel Bug Tracker #202473 https://bugzilla.kernel.org/show_bug.cgi?id=202473 -- You received this bug notification because you a

[Bug 1810416] Re: SD card error mmc0: error -110 whilst initialising SD card

Same issue here, also with a SanDisk Extreme microSD card (128GB). Possibly relevant: https://bugzilla.kernel.org/show_bug.cgi?id=202473 ** Bug watch added: Linux Kernel Bug Tracker #202473 https://bugzilla.kernel.org/show_bug.cgi?id=202473 -- You received this bug notification because you a

Re: termguicolors and xterm

On Saturday, 19 January 2019 22:43:30 UTC, Chris Jones wrote: > Has anyone been able to get the 'termguicolors' option to work on xterm > or does xterm altogether lack the capability? termguicolor works for me in xterm 330 on Ubuntu 18.04 (as in, I can see colours with it set; I think they are q

[Touch-packages] [Bug 1813400] [NEW] systemctl doesn't respect --dry-run

Public bug reported: [Expected behaviour] When I use the --dry-run flag with systemctl, I would expect it not to take any action, but instead print what it is going to do. [Actual behaviour] Passing --dry-run doesn't affect the behaviour of systemctl. [Test case] $ systemctl --dry-run reboot

[Bug 1813400] [NEW] systemctl doesn't respect --dry-run

Public bug reported: [Expected behaviour] When I use the --dry-run flag with systemctl, I would expect it not to take any action, but instead print what it is going to do. [Actual behaviour] Passing --dry-run doesn't affect the behaviour of systemctl. [Test case] $ systemctl --dry-run reboot

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using i3wm

Ok, thanks; I guess I'll live with the tearing for now, then. I agree that it seems a bit pointless/unlikely to spend time fixing this given most people won't run into it now that compositors are so common. Maybe I'll get around to configuring one at some point :) -- You received this bug notifi

[Bug 1811808] Re: Tearing and/or flickering when using i3wm

Ok, thanks; I guess I'll live with the tearing for now, then. I agree that it seems a bit pointless/unlikely to spend time fixing this given most people won't run into it now that compositors are so common. Maybe I'll get around to configuring one at some point :) -- You received this bug notifi

[Bug 1811808] Re: Tearing and/or flickering when using i3wm

Ok, thanks; I guess I'll live with the tearing for now, then. I agree that it seems a bit pointless/unlikely to spend time fixing this given most people won't run into it now that compositors are so common. Maybe I'll get around to configuring one at some point :) -- You received this bug notifi

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

> Does using a Wayland session avoid the bug? Yes, I see no tearing in Totem (or Chrome) when using Wayland. (Note: after uninstalling the Nvidia drivers (`apt purge nvidia-driver-410 && apt autoremove --purge`), I have to boot with `nouveau.modeset=0`, otherwise boot hangs at Plymouth after enter

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

> Does using a Wayland session avoid the bug? Yes, I see no tearing in Totem (or Chrome) when using Wayland. (Note: after uninstalling the Nvidia drivers (`apt purge nvidia-driver-410 && apt autoremove --purge`), I have to boot with `nouveau.modeset=0`, otherwise boot hangs at Plymouth after enter

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

> Does using a Wayland session avoid the bug? Yes, I see no tearing in Totem (or Chrome) when using Wayland. (Note: after uninstalling the Nvidia drivers (`apt purge nvidia-driver-410 && apt autoremove --purge`), I have to boot with `nouveau.modeset=0`, otherwise boot hangs at Plymouth after enter

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Tearing in Totem with modesetting driver" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230257/+files/totem-tearing.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Tearing in Totem with modesetting driver" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230257/+files/totem-tearing.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu.

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

I'm using only one monitor (the one built-in to the laptop), at times I use an external monitor as well, but this problem persists without it plugged in. After removing that block (i.e. using the modesetting driver), I get jagged tearing almost everywhere. Both Chrome and Totem tear very noticeabl

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Tearing in Totem with modesetting driver" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230257/+files/totem-tearing.jpg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubun

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

I'm using only one monitor (the one built-in to the laptop), at times I use an external monitor as well, but this problem persists without it plugged in. After removing that block (i.e. using the modesetting driver), I get jagged tearing almost everywhere. Both Chrome and Totem tear very noticeabl

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

I'm using only one monitor (the one built-in to the laptop), at times I use an external monitor as well, but this problem persists without it plugged in. After removing that block (i.e. using the modesetting driver), I get jagged tearing almost everywhere. Both Chrome and Totem tear very noticeabl

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230058/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1811

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

This Xorg.1.log was last modified in November, so I'm unsure if it's relevant. ** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230059/+files/Xorg.1.log -- You received this bug notification because you are a member of Desktop Packag

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

I don't have an /etc/X11/xorg.conf, but I do have (along with the various distribution-provided files) a /usr/share/X11/xorg.conf.d/99-custom.conf. ** Attachment added: "99-custom.conf" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230057/+files/99-custom.conf --

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

I don't have an /etc/X11/xorg.conf, but I do have (along with the various distribution-provided files) a /usr/share/X11/xorg.conf.d/99-custom.conf. ** Attachment added: "99-custom.conf" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230057/+files/99-custom.conf --

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

This Xorg.1.log was last modified in November, so I'm unsure if it's relevant. ** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230059/+files/Xorg.1.log -- You received this bug notification because you are a member of Ubuntu Desktop

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230058/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title:

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

This Xorg.1.log was last modified in November, so I'm unsure if it's relevant. ** Attachment added: "Xorg.1.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230059/+files/Xorg.1.log -- You received this bug notification because you are a member of Ubuntu Bugs, w

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230058/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

I don't have an /etc/X11/xorg.conf, but I do have (along with the various distribution-provided files) a /usr/share/X11/xorg.conf.d/99-custom.conf. ** Attachment added: "99-custom.conf" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230057/+files/99-custom.conf --

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

Unfortunately, the BIOS doesn't have an option to disable the Nvidia GPU. ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230056/+files/allpackages.txt -- You received this bug notification because you are a member of Ubuntu De

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

Unfortunately, the BIOS doesn't have an option to disable the Nvidia GPU. ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230056/+files/allpackages.txt -- You received this bug notification because you are a member of Desktop P

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

Unfortunately, the BIOS doesn't have an option to disable the Nvidia GPU. ** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5230056/+files/allpackages.txt -- You received this bug notification because you are a member of Ubuntu Bu

[Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

@Alberto: would you be open to adding it again? I need to enable TearFree and select the Intel driver when using my integrated GPU (but if I have `Driver "intel"` in my config when using the Nvidia GPU, I get a black screen on login), so it would be nice to have a way to automatically put a file in

[Desktop-packages] [Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

@Alberto: would you be open to adding it again? I need to enable TearFree and select the Intel driver when using my integrated GPU (but if I have `Driver "intel"` in my config when using the Nvidia GPU, I get a black screen on login), so it would be nice to have a way to automatically put a file in

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

Removing gstreamer1.0-vaapi doesn't appear to help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics Status in totem pa

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `vainfo`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229623/+files/vainfo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `lspci -k`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229624/+files/lspci -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

Removing gstreamer1.0-vaapi doesn't appear to help. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notif

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `vainfo`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229623/+files/vainfo -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bu

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `vainfo`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229623/+files/vainfo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `lscpu`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229622/+files/lscpu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title:

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

Removing gstreamer1.0-vaapi doesn't appear to help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Title: Tearing and/or flickering when using Intel graphics To manage notifications about th

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `lspci -k`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229624/+files/lspci -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/b

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `lspci -k`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229624/+files/lspci -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811808 Titl

[Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `lscpu`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229622/+files/lscpu -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs

[Desktop-packages] [Bug 1811808] Re: Tearing and/or flickering when using Intel graphics

** Attachment added: "Output of `lscpu`" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1811808/+attachment/5229622/+files/lscpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/18

[Desktop-packages] [Bug 1811808] [NEW] Tearing and/or flickering when using Intel graphics

Public bug reported: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if

[Bug 1811808] [NEW] Tearing and/or flickering when using Intel graphics

Public bug reported: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if

[Bug 1811808] [NEW] Tearing and/or flickering when using Intel graphics

Public bug reported: When using Intel graphics on my hybrid Nvidia laptop, videos in Totem have awful tearing/flickering which makes them essentially unwatchable. With default X settings, I get tearing across the top of the screen (but I also get very noticeable tearing in other applications); if

[Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

This is no longer found in Bionic, since ubuntu-drivers-common 1:0.5 (see [1]). Was this feature intentionally removed? [1]: https://git.launchpad.net/ubuntu/+source/ubuntu-drivers- common/commit/share/hybrid/gpu- manager.c?id=fb450c8eddf9290225e198ce92123e4fff346589 -- You received this bug not

[Desktop-packages] [Bug 1667198] Re: gpu-manager should also support using custom xorg.conf files for Nvidia

This is no longer found in Bionic, since ubuntu-drivers-common 1:0.5 (see [1]). Was this feature intentionally removed? [1]: https://git.launchpad.net/ubuntu/+source/ubuntu-drivers- common/commit/share/hybrid/gpu- manager.c?id=fb450c8eddf9290225e198ce92123e4fff346589 -- You received this bug not

[Desktop-packages] [Bug 1514057] Re: Incorrect(?) reporting of freeness of third-party nVidia drivers from graphic-drivers PPA

I believe this is due to a simplistic handling of "freeness" in UbuntuDrivers.detect._is_package_free() – any package not from restricted or multiverse is considered free: # it would be better to check the actual license, as we do not have # the component for third-party packages; but this

[Bug 1514057] Re: Incorrect(?) reporting of freeness of third-party nVidia drivers from graphic-drivers PPA

I believe this is due to a simplistic handling of "freeness" in UbuntuDrivers.detect._is_package_free() – any package not from restricted or multiverse is considered free: # it would be better to check the actual license, as we do not have # the component for third-party packages; but this

Re: Checksum errors

Thanks for the response. I've got network back now, and I'm working from a separate partition without having wiped the old one yet. I also seem to get a few errors on another LVM volume (root partition); not sure if that was happening before too, but it's mounting and (mostly) running OK now. Th

Checksum errors

Hi, My btrfs partition will not mount. I spent some time in the IRC, where darkling said it was due to checksum errors, but we couldn't find a solution. The kernel version is 4.19.12 and btrfsprogs are at 4.19.1. Unfortunately I wasn't able to get a network connection on the computer in questio

Bug#916458: Typo in libinput10 description

Package: libinput10 Version: 1.12.1-1 Severity: minor The description for the libinput10 package has two typos: "so minimize" should be "to minimize", and "need to provide" should probably be "needs to provide" (as in "needs in order to provide").

[Desktop-packages] [Bug 1797147] Re: Backport PRIME switching fixes to Ubuntu 18.04

I tested with LightDM, ubuntu-drivers-common 1:0.5.2.2, and nvidia-prime 0.8.8.2, doing various combinations of `prime-select intel` and `prime- select nvidia`; everything seems to work as described in the original description. Thank you Alberto for your work on this! ** Tags removed: verificatio

  1   2   3   4   5   6   7   >