Public bug reported:
An unresolvable problem occurred while initializing the package
information.
Please report this bug against the 'update-manager' package and include the
following error message:
E:can not open
/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_jammy-backports_InRelease
*** This bug is a duplicate of bug 2061954 ***
https://bugs.launchpad.net/bugs/2061954
Confirm after 'upgrade' (total disaster) it also affects Kubuntu 24.04.
Identical symptoms to other posters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Public bug reported:
After complete removal of firewalld service package (using sudo
systemctl disable firewalld.service, sudo apt remove firewalld), a
firewalld service authorization login prompt continues to pop up after
system startup, immediately after regular login. This is after
systemctl a
I upgraded 21.10 to 22.04 and openssl 3 "broke" globalprotect 6.0.0.44.
I was able to follow suoko's solution as-is until step #5, it would never
return a value, I couldn't successfully finish authenticating. I installed
gpclient and had the same issue (authentication error), ultimately I went t
I have this problem.
Chromium Version 97.0.4692.71 (Official Build) snap (64-bit)
Ubuntu 20.04.3 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956888
Title:
can't manually sort bookmarks anymor
https://j.mp/3anxFOh
=
I care about the job, but mostly I want to be inspired. - Jerry Maguire
The soundtrack to \'Indecent Exposure\' is a romantic mix of music that I know
most women love to hear, so I never keep it far from me when women are nearby.
- Fabio
A ch
https://bitly.com/32cZkPg?whole=garden
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
http://bit.do/fHkGr
-- Forwarded message -
From: margaretanneke...@hotmail.com
Date: Monday, August 10, 2020 05:21:21 AM
Subject:
To: <263...@bugs.launchpad.net>
https://search.yahoo.com/search?p=&fr=qtptaxdf1wx0fgbw
--
You received this bug notification because you are a
https://bitly.com/3e4Lpx7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnogosear
��
��
��
https://bit.ly/3dVg7c8
��
��
��
��
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
��
��
https://clck.ru/PA6S4
��
��
��
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sour
I attempted to get a bisect going but failed. These commit logs look
promising though as to where the fix lies.
~/git/mainline-crack$ git log --oneline v5.6.6..v5.6.7 --
./drivers/gpu/drm/nouveau/
360aba644f1f drm/nouveau/gr/gp107,gp108: implement workaround for HW hanging
during init
dd4a3179e0
I've been testing various previous releases of Linux from the mainline
repo. 5.6.2 still fails, 5.6.18 works fine. 5.6.0 and 5.6.1 both have
busted wifi so I didn't test them beyond realizing my wifi didn't work.
Looking through the CHANGES files I see 5.6.6 and 5.6.7 both reference
nouveau change
�� �� �� �� �� �� https://v.ht/Z89Z �� �� �� �� ��
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net
I heavily used the laptop over the course of another day and half. Zero
crashes! I did everything in my power to induce the failure mode I was
previously seeing and nada. I closed the lid with wreckless abandon,
left it open, locked it, plugged in, on battery, etc. So far so good.
kern.log is clean
Tested lightly yesterday as I didn't get much time to use my laptop,
however I went through several sleep/wake cycles, some with power
plugged in lid left open, on battery lid left open, on battery lid down
to lid up several hours later. Whenever I walked past it I did
"something" to wake it up, un
Signed and installed 5.7.0-050700-generic from mainline. I will test it
out and see what I get, thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881828
Title:
Lenovo X1 Extreme screen never
0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: kelly 2328 F pulseaudio
/dev/snd/controlC0: kelly 2328 F pulseaudio
CasperMD5CheckResult: skip
Date: Tue Jun 2 17:53:19 2020
InstallationDate: Installed on 2019-12-07 (179 days
https://j.mp/2X2lOhU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnogosearch/+b
I agree with Timo: It'd be great to be able to set font size per
screen! I might actually prefer that to screen scaling :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870736
Title:
[nvidia] Scr
Public bug reported:
New install of ubuntu 20. Ran update and received errors.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs
��
��
https://j.mp/35pgl8A
��
��
��
��
��
��
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubun
*** This bug is a duplicate of bug 1874567 ***
https://bugs.launchpad.net/bugs/1874567
Setting the orientation of my second monitor in `nvidia-settings` works
correctly (panning and tracking are not enabled).
Here's the output of `xrandr` after rotating my second monitor in
`nvidia-settings`:
*** This bug is a duplicate of bug 1874567 ***
https://bugs.launchpad.net/bugs/1874567
I agree with Chris: This current bug (#1875017) is not a duplicate of
bug #1874567 :)
Since updating from 19.10 to 20.20, I'm getting the same issue as Chris:
I have two monitors, both connected to an Nvi
http://tiny.cc/ow4onz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnogosearch/+
��
https://j.mp/3cm0ASn
��
��
��
��
��
��
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
Public bug reported:
Experiencing intermittent system freezes. The screen displays repeated
diagonal pattern. Sometimes I can reboot via REISUB but typically no
mouse or keyboard input is recognised and reset button required to
reboot.
Problem appears to occur with nouveau rendering using graphic
��
https://clck.ru/M8Tu9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnogosea
https://u.to/6CpTFw
From: [mailto:margaretannekel...@hotmail.com]
Sent: Monday, January 27, 2020 05:18:30 PM
To: 263...@bugs.launchpad.net
Subject:
http://www.bing.com/search?q=&form=UAVKNNEMGEBSPRT&cvid=NZCRADFCCBGCPCC
--
You received this bug notification because you are a member
�� �� �� https://clck.ru/Lotx6 �� �� ��
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
https://clck.ru/LZCLJ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnogosearch/+
http://bit.do/fkVBJ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnogosearch/+bu
http://bit.ly/2op6hvx
From: [mailto:margaretannekel...@hotmail.com]
Sent: Tuesday, October 29, 2019 03:03:54 AM
To: 263...@bugs.launchpad.net
Subject:
http://www.bing.com/search?q=&form=SYMCKXTRVEGADQU&cvid=KYXPSMYMRBBKHDM
--
You received this bug notification because you are a membe
�� ��
https://clck.ru/JVW6U
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnogo
I don't see a "Closed" status. The closest thing I see to make it go
away is "Invalid", but I would say that you can close it, unless the
thing to do is add Crash to the config by default so it isn't a manual
step.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Adding Crash to the config file seems to have done the trick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814174
Title:
Xorg crash report after resume
To manage notifications about this bug go t
>From that bug report I followed this step:
"It works to edit /etc/apport/crashdb.conf and add 'Crash' to the
'problem_types': ['Bug', 'Package', 'Crash'], or to make that change in
a separate file and run".
So I'll see how that fares.
--
You received this bug notification because you are a mem
Output of ls -l
total 2320
-rw-r- 1 root whoopsie 2373147 Feb 1 13:35 _usr_lib_xorg_Xorg.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814174
Title:
Xorg crash report after resume
To
1. I'm not sure what you mean by the ID of the bug.
The file is owned by root, group whoopsie
2. The contents of the file whoopsie-id are:
ad2a60d37ef07a75f5bb69241962893c2ee51bf68be6d93a3b37992aaf2d45370ac7a5094e472b57985c4979bd5355af775f1d483c51977972fa4f743003d70c
3. didn't do this part
--
Public bug reported:
Crash Report when resuming from sleep.
Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223
This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M,
driver 390.77
The crash log doesn't have much info in it IMO, but I uploaded here
htt
��
https://goo.gl/B4mNgM
��
��
��
��
��
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
This (keyboard shortcuts not working) happened to me, specifically
CTRL+ALT+T not giving me the terminal. I experimented and found that the
ALT key was at fault - it wasn't registering. I then found a reference
on line (sorry don't have the URL) to this being a keyboard Language
issue. I then tried
changed to local repository utex.edu
Failed to download repository information
-check internet connection (connection status: good)
-details
_Bionic Beaver_ - Release amd64 (20180725) bionic Release' does not have a
Release file., W:Updating from such a repository can't be done securely, and i
Public bug reported:
failed to update, failed repository ubuntu 18.04 tls
http://mirror.lstn.net/ubuntu
_im a new user and moving from windows to Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: samba 2:4.7.6+dfsg~ubuntu-
I have a similar issue (dns server running on a DSL router). The router
assigns hostnames ending in .home
Seems to break resolution for the systemd-resolved as well (only working
sometimes).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
Crashed during installation from USB ISO over windows 10 home
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubiquity 18.10.12
ProcVersionSignature: Ubuntu 4.18.0-10.11-lowlatency 4.18.12
Uname: Linux 4.18.0-10-lowlatency x86_64
ApportVersion: 2.20.10-0ubuntu13
Archite
https://goo.gl/wh8sao
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/263063
Title:
pops up often
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mnogosearch/+
Public bug reported:
I have an Intel NUC8i7HNK and none of the Ubuntu or Debian images that I have
tried get past GRUB. I have tried Ubuntu Server 18.04.1 as well as the latest
Ubuntu 18.10 nightly. After selecting any installation method in GRUB the
screen goes black. Things that I have tried
Public bug reported:
DRM package needed this lib, I installed it and DRM install proceeded
successfuly
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdrm-common 2.4.91-2~16.04.1
Uname: Linux 4.14.0-041400-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.18
Public bug reported:
Windows 10 bootloader is not installer properly.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVe
It was merged and will appear in byobu 5.126
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers after updates
To manage notifications about this bug go t
Hi,
Awesome. I submitted a pull request for this on GitHub:
https://github.com/dustinkirkland/byobu/pull/26
Perhaps Dustin will see it and use it, or make another fix/change in his
own words.
thx so much for byobu and everyone's help,
-mark
--
You received this bug notification because you a
Hi,
I have not seen the problem for a while now.
Is it still ok with you ?
take care,
-mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers after updat
Hi,
Any update ? I have not had the problem now for about a month.
I hope its ok with you also ?
-mark
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers
** Also 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/1714667
Title:
please add old hungarian letters
To manage notifications about this
Hi,
Attached is another update. This one adds an additional time check to run the
update_cache once an hour. Save it to /usr/lib/byobu/updates_available, and
make sure it is executable, just like before.
a). cd /usr/lib/byobu
b). cp/save the new updates_available file you downloaded in
** Attachment removed: "updates_available"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5043276/+files/updates_available
** Attachment removed: "updates_available"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5043277/+files/updates_available
** Patch removed: "up
ok, attached is a new, complete updates_available script. Save it to
/usr/lib/byobu/updates_available, and make sure it is executable, just like
before.
a). cd /usr/lib/byobu
b). cp/save the new updates_available file you downloaded into this dir
c). sudo chmod 755 updates_available
Hi,
I've got a fix :-)
Let me test it more tomorrow and then I'll post a new updates_available
script
-mark
On Sat, Feb 10, 2018 at 9:00 AM M Kelly wrote:
> Hi,
>
> Yes it helped thanks. Thinking on it.
>
> -mark
>
> On Sat, Feb 10, 2018, 8:54 AM jokrebel <
Hi,
Yes it helped thanks. Thinking on it.
-mark
On Sat, Feb 10, 2018, 8:54 AM jokrebel <1604...@bugs.launchpad.net>
wrote:
> Just confirmed the same issue at an other machine with actual siduction
>
> after "update && full-upgrade" still got red "93!" in the byobu panel
>
> update once more di
Hi,
Just to be complete, for example, my system shows a 4! in red this morning.
My cache file shows 4 1
I do an:
sudo apt-get update
sudo apt-get upgrade
and then for about 5 seconds my cache file still shows 4 1 and the red 4!,
but after 5 seconds it automatically changes to 0 0 and the Red 4! go
Hi,
I would just cat that file, as in:
cat $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
On my system this is what it I do:
% cat $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
0 0
So I can see the file has just "0 0" in it at this moment.
You could also use less, more, nano, v
Hi,
Can you verify you have this file ?
/usr/lib/update-notifier/apt-check
The extra logic I added was only for when this file is on your system and I
just want to confirm if this is true for you.
thanks,
-mark
On Mon, Feb 5, 2018 at 7:31 PM M Kelly wrote:
> Hi,
>
> Yes, the cach
Hi,
Yes, the cache file is at:
$BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
-mark
On Mon, Feb 5, 2018 at 1:29 AM jokrebel <1604...@bugs.launchpad.net>
wrote:
> Hi again,
>
> "Next time it happens, before you issue the --reinstall command, can you
> check the cache file and tell me if
Hi,
It's ok - I learned something from this and I will keep going and
eventually solve :-)
Next time it happens, before you issue the --reinstall command, can you
check the cache file and tell
me if it has the 2 2 (or whatever the number your status shows) or a 0 0 in
it ?
I want to see if the sta
Hi,
The patch method expects the updates_available file is in its original
condition and to be the same as mine. Have you modified it before this or
perhaps its older or from a different version of byobu/Ubuntu ? If so that is
probably the reason it failed.
Which is why I also posted the compl
Hi.
Either of 1). or 2) will do it -
1). save complete updates_available file in post #50 then do:
a). cd /usr/lib/byobu
b). sudo cp updates_available updates_available.orig
c). save the new updates_available file from post #50 here
d). sudo chmod 755 updates_available
or using pa
Scratch, that, previous upload was a just diff file, here is a correct patch
file:
thx
** Patch added: "updates_available.patch"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5045007/+files/updates_available.patch
--
You received this bug notification because you are a member o
I also uploaded a patch file for this if that is easier to apply
Just curious if the small difference in update method and time window solves
the problem.
thx
** Patch added: "updates_available.patch"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5045005/+files/updates_available.p
I attached my modified updates_available file here.
** Attachment added: "updates_available"
https://bugs.launchpad.net/byobu/+bug/1604750/+attachment/5043277/+files/updates_available
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
through this code path -
if [ -x /usr/lib/update-notifier/apt-check ]; then
But if not we can add the new logic to the other code paths.
thx,
-mark
On Thu, Jan 25, 2018 at 9:43 PM M Kelly wrote:
> Hi,
>
> Yes, good idea, thanks for that info.
>
> -mark
>
> On Thu, Jan 25
Hi,
Yes, good idea, thanks for that info.
-mark
On Thu, Jan 25, 2018 at 1:05 PM bsy wrote:
> for apt, why not use something like apt list --upgradeable | wc -l to
> determine whether updates are needed / the number of upgradeable
> packages? apt list output is not stable yet, but should be so
On Fri, Jan 19, 2018 at 8:37 PM M Kelly wrote:
> Hi,
>
> I think the easiest work-around is to remove the cache file -
>
> rm -f $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
>
> -mark
>
> On Sun, Jan 7, 2018 at 8:54 AM M Kelly wrote:
>
>> Hi,
>>
Hi,
I think the easiest work-around is to remove the cache file -
rm -f $BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available
-mark
On Sun, Jan 7, 2018 at 8:54 AM M Kelly wrote:
> Hi,
>
> Happy New Year to you.
> Yes, thx, I agree, I have seen it happen a few times myself and som
Hi,
Happy New Year to you.
Yes, thx, I agree, I have seen it happen a few times myself and some apt
cmds get it to resolve.
If I find some time I will try to look at it more, it is annoying.
take care,
On Sun, Jan 7, 2018 at 4:55 AM jokrebel <1604...@bugs.launchpad.net>
wrote:
> Hi again,
>
> e
This also affects me running 1:3.1.4-9Ubuntu on 16.04.3 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702879
Title:
crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
Hi,
Thanks. I have had it happen only two times in a few months after that
patch fix, so like you it still happens but I put up with it and didn't
bother to spend time to fix for sure.
But yes it is a 'timing' issue and the script should do something like loop
and re-check for when dpkg.log does
Public bug reported:
I was trying to update my system and got the error
Unpacking grub-common (2.02~beta2-36ubuntu3.14) over (2.02~beta2-36ubuntu3.12)
...
dpkg: error processing archive
/var/cache/apt/archives/grub-common_2.02~beta2-36ubuntu3.14_amd64.deb
(--unpack):
unable to sync file '/usr/
I have the same problem too
HP Pavilion - 17-ab201na
CPU Intel® Core™ i5-7300HQ
Chipset Intel® HM175
Wireless connectivity Intel® 802.11ac (2x2)
lspci |grep -i network
04:00.0 Network controller: Intel Corporation Wireless 7265 (rev 61)
nmcli --version
nmcli tool, version 1.2.6
uname -r
4.10.0-
I guess you are right! testparm showed a malformed line in [global]
client min protocol = SMB1
After uncommenting it or changing it to
client min protocol = NT1
I wasn't able to reproduce the above error.
I guess you can close this Bug - thanks for taking care!
--
You received this bug notif
: enabled)
+ Active: failed (Result: exit-code) since Fr 2017-09-01 09:19:46 CEST; 7ms
ago
+ Docs: man:systemd-sysv-generator(8)
+ Process: 7304 ExecStart=/etc/init.d/smbd start (code=exited,
status=1/FAILURE)
- Sep 01 09:19:46 kelly systemd[1]: Starting LSB: start Samba S...
- Sep 01
Public bug reported:
Description:Ubuntu 16.04.3 LTS
Release:16.04
What I did/expected:
Updating samba from version
2:4.3.11+dfsg-0ubuntu0.16.04.9
to
2:4.3.11+dfsg-0ubuntu0.16.04.10
What happened:
Update process threw error messages.
Steps to reproduce:
1. sudo apt update && sudo apt
With the proposed fix, today my status bar showed a 1! and after an
update && upgrade, for the first time in a while the 1! is still
present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Titl
After a few weeks of use, I have to say the fix -
[ "/var/lib/apt" -nt "$mycache" ] || [ "/var/lib/apt/lists" -nt
"$mycache" ] || [ "/var/log/dpkg.log" -nt "$mycache" ]
to the /usr/lib/byobu/updates_available script has worked well for me on two
different systems (both Ubuntu 16.04 with HWE)
PS - I set my status interval with a setting in my ~/.byobu/.tmux.conf
file -
set -g status-interval 10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update number
@jokrebel, hi
What is your status-interval set to (how many seconds between status bar
updates) ?
When you still have a red 3! (or whatever the number) after an upgrade - can
you press the F5 key a few times to see if the red 3! update goes away ?
The additional check for if the cache file is new
Public bug reported:
1) ubuntu 14.04 with current updates (like you auto-gathered)
2) rhythmbox 3.0.2
3) expected audio when click on song in youtube
(like it worked a week ago, and has worked since Oct2014)
4) no audio from youtube (.mp3 files on hard disk play OK)
I've read that youtube uses
@jokrebel, hi
Just to confirm, do you have this file on your system ?
/usr/lib/update-notifier/apt-check
-thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing upd
@jokrebel, hi
ok, sorry. I will post another patch soon and we can see if that helps fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604750
Title:
Byobu not clearing update numbers after upd
@jokrebel, hi
The patch I used is this: (changing one line)
# orig:
# [ "/var/lib/apt" -nt "$mycache" ] || [ "/var/lib/apt/lists" -nt
"$mycache" ]
# new:
[ "/var/lib/apt" -nt "$mycache" ] || [ "/var/lib/apt/lists" -nt
"$mycache" ] || [ "/var/log/dpkg.log" -nt "$mycache" ]
So far
Maybe this dbg output from updates_available helps reveal the issue:
___update_needed() entr 2017-04-19 17:57:22:332517641
___update_needed(): mycache= 2017-04-19 17:56:55:299087230
___update_needed(): /var/lib/apt = 2017-04-19 17:57:20:275457556
___update_needed(): /var/lib/apt/
I will confirm this happens to me sometimes also on 16.04 on several different
machines.
I have debugged as well and will also confirm it has to do with the file dates
and how long an update takes, so it is not easily reproducible. But the logic
flow shows how it can happen.
I have patched the
nickleplated, Thanks you I missed the link somehow. 4.10.0.-25 from
proposed solved the issue for me with the Gigabyte AB350 Gaming 3 with
bios 7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671360
I'm using: 4.10.0-24-generic and only able to use Ubuntu with acp=off
nickleplated.
I'm unclear about how to fetch the versions that people are mentioning
in the last few posts. Can someone clue me in on how to fetch `linux-
generic-hwe-16.04-edge=4.10.0.23.16.10.0` or `4.10.0-25 from -proposed`
w
Public bug reported:
pass
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.18-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-80.101-generic 4.4.70
Uname: Linux 4.4.0-80-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun Jun 18 19:49:11
Hi
Just a report I was thrilled to hear this was fixed in 16.10 I ran
17.04 and was going to install it to my hard drive in place of the
MX-16 on there and get my beloved Mate back but the same panel
notification came up. This happened when I was in Mate tweek and was
switching desktop looks
cheers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/19167
Title:
Update Manager and unresolved dependencies
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
I too removed the references from /usr/local/lib and also from
/usr/local/bin and ran the 'sudo apt-get -f install' and it fixed
everything, including re-installing and configuring Python 3.5.
I suspect I caused the problem by manually installing Python to get
around the missing library problem
Public bug reported:
SETUP
* Ubuntu 17.04 using Unity 7.
* Multi-monitor setup, where the vertical resolutions of the
monitors are different.
* compiz version 1:0.9.13.1+17.04.20170109-0ubuntu1
PROBLEM
Dialog boxes are positioned in the "invisible space" above the smaller
monitor. Hence the
Errors were encountered while processing:
python3.5-minimal
python3-minimal
E: Sub-process /usr/bin/dpkg returned an error code (1)
brian@VideoEd-Linux:~$
I hope this is helpful. I have not tried removing python references from
/usr/local as Dave Kuhlman tried but unles
1 - 100 of 587 matches
Mail list logo
