How to know which package broke something after updating?

matcharles · 2015-10-18 11:18:28

Good day all,

I am still learning a LOT on this beautiful system, but sometimes I cannot find the answer on my own and have to come here for help. My question is two fold.

1) If a program/device or something doesn't work like it was before I did pacman -Syu, how do I know which package broke it? Do I just go through the list and try to pinpoint?

2) I am asking this because I was away for about 3 weeks and when I came back I did a system update, and obviously there were quite a few to do. Once it finished, I noticed that my middle mouse button (Logitech M560)'s wouldn't go "backward/forward" a page when clicked sideways. Now if somethings breaks with thunar, it's easy so pinpoint where it went wrong, but how do I do this for a device (mouse in this case)?

I went through the pacman log while searching on the net and found that maybe it was the package "gpm" causing trouble so I downgraded and it's still not working. It's not a big deal, just annoying.

Thanks very much!

Trilby · 2015-10-18 11:38:06

matcharles wrote:

Do I just go through the list and try to pinpoint?

In general, yes.

I noticed that my middle mouse button (Logitech M560)'s wouldn't go "backward/forward"

In this specific case, I'd invest much more on the diagnosis stage. Do you really think it is hardware not detecting mouse buttons 6 and 7 or is it the much more likely possibility that the client program is no longer responding with the back or forward behaviors?

You can easily test whether the events are detected by using xev.

Roken · 2015-10-18 20:14:04

Agree with Trilby in this instance. However, to make your life easier for the future, update often (I do so once in the morning, and again in the evening on a work day, more frequently when I'm home all day). This will both reduce the update time each time, and limits the number of updates to a manageable number should something go wrong.

You should also check what is being updated each time. Experience is the only teacher in this regard, but you will learn what may cause a problem, and wheat is unlikely to.

matcharles · 2015-10-18 20:31:29

Trilby wrote:

matcharles wrote:
Do I just go through the list and try to pinpoint?
In general, yes.
I noticed that my middle mouse button (Logitech M560)'s wouldn't go "backward/forward"
In this specific case, I'd invest much more on the diagnosis stage. Do you really think it is hardware not detecting mouse buttons 6 and 7 or is it the much more likely possibility that the client program is no longer responding with the back or forward behaviors?
You can easily test whether the events are detected by using xev.

Thanks much for this!

So I tested the mouse with xev and it indeed picks up the mouse button (backward is 6 and forward is 7). Where should I investigate next? Appart from the gpm package I don't see much related to mouse control.

Thanks!!!

matcharles · 2015-10-18 20:34:11

Roken wrote:

Agree with Trilby in this instance. However, to make your life easier for the future, update often (I do so once in the morning, and again in the evening on a work day, more frequently when I'm home all day). This will both reduce the update time each time, and limits the number of updates to a manageable number should something go wrong.
You should also check what is being updated each time. Experience is the only teacher in this regard, but you will learn what may cause a problem, and wheat is unlikely to.

Great points! And I usually do daily, but in this case I was out of the country for 3 weeks so unable to do it. Here is a copy of the log from when something broke: (Maybe ncurses??)

[2015-09-22 13:53] [PACMAN] Running 'pacman -Syu'
[2015-09-22 13:53] [PACMAN] synchronizing package lists
[2015-09-22 13:53] [PACMAN] starting full system upgrade
[2015-09-22 13:56] [ALPM] transaction started
[2015-09-22 13:56] [ALPM] upgraded ncurses (5.9-7 -> 6.0-3)
[2015-09-22 13:56] [ALPM] upgraded readline (6.3.008-1 -> 6.3.008-3)
[2015-09-22 13:56] [ALPM-SCRIPTLET] /usr/bin/bash: error while loading shared libraries: libncursesw.so.5: cannot open shared object file: No such file or directory
[2015-09-22 13:56] [ALPM] upgraded bash (4.3.042-1 -> 4.3.042-3)
[2015-09-22 13:56] [ALPM] upgraded gpm (1.20.7-4 -> 1.20.7-5)
[2015-09-22 13:56] [ALPM] upgraded aalib (1.4rc5-10 -> 1.4rc5-11)
[2015-09-22 13:56] [ALPM] upgraded psmisc (22.21-2 -> 22.21-3)
[2015-09-22 13:56] [ALPM] upgraded alsa-utils (1.0.29-1 -> 1.0.29-2)
[2015-09-22 13:56] [ALPM] upgraded aspell (0.60.6.1-2 -> 0.60.6.1-3)
[2015-09-22 13:56] [ALPM] upgraded libsystemd (225-1 -> 226-1)
[2015-09-22 13:56] [ALPM] upgraded libdbus (1.10.0-2 -> 1.10.0-3)
[2015-09-22 13:56] [ALPM] upgraded dbus (1.10.0-2 -> 1.10.0-3)
[2015-09-22 13:56] [ALPM] upgraded libutil-linux (2.26.2-1 -> 2.27-2)
[2015-09-22 13:56] [ALPM] upgraded util-linux (2.26.2-1 -> 2.27-2)
[2015-09-22 13:56] [ALPM] upgraded less (481-1 -> 481-2)
[2015-09-22 13:56] [ALPM] upgraded texinfo (5.2-3 -> 5.2-4)
[2015-09-22 13:56] [ALPM] upgraded systemd (225-1 -> 226-1)
[2015-09-22 13:56] [ALPM] upgraded gtk-update-icon-cache (3.16.6-1 -> 3.16.7-1)
[2015-09-22 13:56] [ALPM] upgraded freetype2-infinality-ultimate (2.6-3 -> 2.6-4)
[2015-09-22 13:56] [ALPM-SCRIPTLET]   If you have been using freetype2-infinality from the AUR,
[2015-09-22 13:56] [ALPM-SCRIPTLET]   the runtime file that came with it has been saved as
[2015-09-22 13:56] [ALPM-SCRIPTLET]   /etc/X11/xinit/xinitrc.d/infinality-settings.pacsave and the new
[2015-09-22 13:56] [ALPM-SCRIPTLET]   one was installed in its place. You can manually delete
[2015-09-22 13:56] [ALPM-SCRIPTLET]   infinality-settings.sh.pacsave as it is not needed anymore.
[2015-09-22 13:56] [ALPM-SCRIPTLET] 
[2015-09-22 13:56] [ALPM-SCRIPTLET]   If you are using [multilib], please install/upgrade
[2015-09-22 13:56] [ALPM-SCRIPTLET]   lib32-freetype2-infinality-ultimate, too.
[2015-09-22 13:56] [ALPM] upgraded libdrm (2.4.64-1 -> 2.4.65-1)
[2015-09-22 13:56] [ALPM] upgraded libedit (20150325_3.1-1 -> 20150325_3.1-2)
[2015-09-22 13:56] [ALPM] upgraded llvm-libs (3.6.2-3 -> 3.6.2-4)
[2015-09-22 13:56] [ALPM] upgraded libtasn1 (4.6-1 -> 4.7-1)
[2015-09-22 13:56] [ALPM] upgraded gnutls (3.4.4.1-1 -> 3.4.5-1)
[2015-09-22 13:56] [ALPM] upgraded python (3.4.3-2 -> 3.4.3-3)
[2015-09-22 13:56] [ALPM] upgraded chromium (45.0.2454.85-1 -> 45.0.2454.99-1)
[2015-09-22 13:56] [ALPM] upgraded cmake (3.3.1-2 -> 3.3.2-3)
[2015-09-22 13:56] [ALPM] upgraded cpio (2.11-6 -> 2.12-2)
[2015-09-22 13:56] [ALPM] upgraded dhclient (4.3.2-2 -> 4.3.3-2)
[2015-09-22 13:56] [ALPM] upgraded dialog (1:1.2_20150528-1 -> 1:1.2_20150528-2)
[2015-09-22 13:56] [ALPM] upgraded filezilla (3.13.1-1 -> 3.14.0-1)
[2015-09-22 13:56] [ALPM] upgraded flashplugin (11.2.202.508-1 -> 11.2.202.521-1)
[2015-09-22 13:56] [ALPM] upgraded gettext (0.19.5.1-1 -> 0.19.6-1)
[2015-09-22 13:56] [ALPM] upgraded git (2.5.2-1 -> 2.5.3-1)
[2015-09-22 13:56] [ALPM] upgraded gtk3 (3.16.6-1 -> 3.16.7-1)
[2015-09-22 13:56] [ALPM] upgraded guile (2.0.11-2 -> 2.0.11-3)
[2015-09-22 13:56] [ALPM] upgraded htop (1.0.3-2 -> 1.0.3-3)
[2015-09-22 13:56] [ALPM] upgraded hunspell (1.3.3-1 -> 1.3.3-2)
[2015-09-22 13:56] [ALPM] upgraded inetutils (1.9.4-1 -> 1.9.4-2)
[2015-09-22 13:56] [ALPM] upgraded lame (3.99.5-2 -> 3.99.5-3)
[2015-09-22 13:56] [ALPM] upgraded lftp (4.6.4-1 -> 4.6.4-2)
[2015-09-22 13:56] [ALPM] upgraded lib32-freetype2-infinality-ultimate (2.6-3 -> 2.6-4)
[2015-09-22 13:56] [ALPM] upgraded lib32-libdrm (2.4.64-1 -> 2.4.65-1)
[2015-09-22 13:56] [ALPM] upgraded lib32-flashplugin (11.2.202.508-1 -> 11.2.202.521-1)
[2015-09-22 13:56] [ALPM] upgraded libcaca (0.99.beta18-2 -> 0.99.beta18-3)
[2015-09-22 13:56] [ALPM] upgraded libcdio (0.93-1 -> 0.93-2)
[2015-09-22 13:56] [ALPM] upgraded libmariadbclient (10.0.21-2 -> 10.0.21-3)
[2015-09-22 13:56] [ALPM] upgraded libwbclient (4.3.0-1 -> 4.3.0-2)
[2015-09-22 13:56] [ALPM] upgraded python2 (2.7.10-1 -> 2.7.10-2)
[2015-09-22 13:56] [ALPM] upgraded smbclient (4.3.0-1 -> 4.3.0-2)
[2015-09-22 13:56] [ALPM] upgraded mplayer (37379-4 -> 37379-5)
[2015-09-22 13:56] [ALPM] upgraded mtr (0.86-1 -> 0.86-2)
[2015-09-22 13:56] [ALPM] upgraded pinentry (0.9.5-1 -> 0.9.5-2)
[2015-09-22 13:56] [ALPM] upgraded mutt (1.5.24-1 -> 1.5.24-2)
[2015-09-22 13:56] [ALPM] upgraded nano (2.4.2-1 -> 2.4.2-2)
[2015-09-22 13:56] [ALPM] upgraded ncftp (3.2.5-4 -> 3.2.5-6)
[2015-09-22 13:56] [ALPM] upgraded xine-lib (1.2.6-5 -> 1.2.6-6)
[2015-09-22 13:56] [ALPM] upgraded openscenegraph (3.2.2-1 -> 3.2.2-2)
[2015-09-22 13:56] [ALPM] upgraded parted (3.2-2 -> 3.2-3)
[2015-09-22 13:56] [ALPM] upgraded procps-ng (3.3.11-1 -> 3.3.11-2)
[2015-09-22 13:56] [ALPM] upgraded systemd-sysvcompat (225-1 -> 226-1)
[2015-09-22 13:56] [ALPM] upgraded unrar (1:5.2.7-1 -> 1:5.3.4-1)
[2015-09-22 13:56] [ALPM] upgraded vi (1:070224-1 -> 1:070224-2)
[2015-09-22 13:56] [ALPM] upgraded vim-runtime (7.4.854-1 -> 7.4.854-2)
[2015-09-22 13:56] [ALPM] upgraded vim (7.4.854-1 -> 7.4.854-2)
[2015-09-22 13:56] [ALPM] upgraded virtualbox-host-modules (5.0.2-1 -> 5.0.4-1)
[2015-09-22 13:56] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2015-09-22 13:56] [ALPM] upgraded virtualbox (5.0.2-1 -> 5.0.4-1)
[2015-09-22 13:57] [ALPM] upgraded vlc (2.2.1-6 -> 2.2.1-7)
[2015-09-22 13:57] [ALPM] upgraded vte (0.28.2-5 -> 0.28.2-6)
[2015-09-22 13:57] [ALPM] upgraded xorg-xinit (1.3.4-2 -> 1.3.4-3)
[2015-09-22 13:57] [ALPM] upgraded xterm (320-1 -> 320-2)
[2015-09-22 13:57] [ALPM] transaction completed

Trilby · 2015-10-18 21:27:53

matcharles wrote:

Where should I investigate next? Appart from the gpm package I don't see much related to mouse control.

The relevant update wouldn't have anything to do with mouse control. If Xev is seeing the button 6 and 7, your mouse is working fine. There is no universal meaning for those two buttons - any x client program that responds to those events does so in their own way. So whichever program is no longer responding to them is the culprit - and it is most likely just a new configuration that you may need to revise.

matcharles · 2015-10-19 11:48:06

Trilby wrote:

matcharles wrote:
Where should I investigate next? Appart from the gpm package I don't see much related to mouse control.
The relevant update wouldn't have anything to do with mouse control. If Xev is seeing the button 6 and 7, your mouse is working fine. There is no universal meaning for those two buttons - any x client program that responds to those events does so in their own way. So whichever program is no longer responding to them is the culprit - and it is most likely just a new configuration that you may need to revise.

Great! Thanks for poiting me in the right direction, I shall look for new pacsave files and update the thread appropriately. Thanks again!

matcharles · 2015-10-25 18:57:17

Still haven't been able to find the correct settings that might have overwrited over something else. This mouse's backward/forward buttons were working out of the box with arch so I don't know why only these two buttons stopped working.

Anyways, I tried a workaround using xbindkeys but it doesn't seem to be working. What I did was add this in the config file:

# Mapping BACK to mousewheel left on old Logitech
"xdotool key Alt_L+Left"
m:0x0 + b:6

# Mapping FORWARD to mousewheel right on old Logitech
"xdotool key Alt_L+Right"
m:0x0 + b:7

Any idea what is wrong? Thanks!

Arch Linux

#1 2015-10-18 11:18:28

How to know which package broke something after updating?

#2 2015-10-18 11:38:06

Re: How to know which package broke something after updating?

#3 2015-10-18 20:14:04

Re: How to know which package broke something after updating?

#4 2015-10-18 20:31:29

Re: How to know which package broke something after updating?

#5 2015-10-18 20:34:11

Re: How to know which package broke something after updating?

#6 2015-10-18 21:27:53

Re: How to know which package broke something after updating?

#7 2015-10-19 11:48:06

Re: How to know which package broke something after updating?

#8 2015-10-25 18:57:17

Re: How to know which package broke something after updating?

Board footer